April 7, 2010 at 8:25 am
Was wondering if someone could help me with the following query.Is it possible to connect to a default instance of SQL Server across a WAN without enabling PORTS 135,139 and 445.I am using XP clients My first reaction is to enable these PORTS
Any help would be appreciated
April 7, 2010 at 9:17 am
depends on your wan
you should be able to connect via TCP/IP - port 1433 (and the UDP port for that is 1434) by default
if these ports are open you should be fine
if you are having trouble in enterprise manager then you can specify the port using the following format in your server registration
myserver,1433
MVDBA
April 7, 2010 at 9:49 am
Hi Mike
thankyou for getting back to me.i have port 1433 enabled and tcpip as well but the when the clients try to connect they fal over and a trace seems to indicate that it is looking to connect to those ports which are disabled at the firewall.I think enabling those ports would resolve it but not sure if I would cause more problems doing that
April 8, 2010 at 1:21 am
what is the client? it it enterprise manager, or an application
can you change the connection string ? can you post it (censored of course - we don't need usernames or passwords, also mask out the IP address or server name) - the reason i ask is it sounds like you are using named pipes, which would mean you had to enable those ports - that can be bad as i beleive 445 is also used for remote file access
if you can change the connectionstring int he application then you could specify the protocol to use
see http://www.connectionstrings.com for details
MVDBA
April 8, 2010 at 3:48 am
The client is an app(Delphi) connecting using a udl.I checked within client network utility and client server utility and saw that along with tcpip ,named pipes was enabled which I disabled and still got the problem.
April 8, 2010 at 4:15 am
could be that named pipes is specified in the connection string
MVDBA
April 8, 2010 at 4:16 am
in client network utility try createing an alias for your server and specify that the alias uses TCP/IP
- that is client network utility on your cleitn machine - not the sql box
make sure sql also is starting up using the TCP protocol (check the server network utility) and alos check the sql server event log for the startup message that shows the ip address and port numbers
MVDBA
April 22, 2010 at 5:35 am
hi Mike
Thanks for your help ,it was all very useful and helpful.i have bounced it back to the firewall adminstrator with some recommendations.
Thanks again
Pat
Viewing 8 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply