February 12, 2007 at 2:05 pm
I am having trouble remotely connecting to sql server 2005 instances which are on a 2-node cluster. I can connect to the default instance locally and remotlely and aslo can connect to the named instances locally. But I am not able to remotely connect to the named instances using SQL Server Manamement Studio. Has anyone had this problem before? Thanks!
February 12, 2007 at 4:11 pm
Yes, we did have this problem. For the instances to be accessed, SQL Browser servie has to be running and UDP port 1434 has to be open. Since we have port 1434 closed between sites my workaround is to create a client alias in Client Network Utility or in 2005 in SQL Server Configuration manager that uses TCP/IP and explicitly specifies port without "Dynamically Determine Port" - this should be unhecked. To start Client Network Utility, go to Start ->Run and type cliconfg (exactly as spelled without i between f and g) and go to Aliases tab to add a new alias.
Regards,Yelena Varsha
February 12, 2007 at 11:41 pm
If you configure the instance to listen on a specific port and you code your connections to that port you won't need to run the SQL Browser service.
February 13, 2007 at 9:49 am
Yes, that is correct. But if port 1434 is closed, even if Browser service is running, it would not do much.
Regards,Yelena Varsha
February 16, 2007 at 12:23 pm
Thanks a lot for all your information. It is very helpful!
February 18, 2007 at 12:13 am
Did you resolve your issue? what is the solution?
MohammedU
Microsoft SQL Server MVP
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply