Can Not Connect to SQL Server Named Instance Remotely?
April 17th, 2009 by Andrew Chen
The other day I was told to install SQL Server 2000 on to a
I verified that the SQL2000 instance was indeed running. The fact that I could connect to this instance by launching Query Analyzer on the server already proofed that. I tried creating and deleting database. No problem I saw the database files created and deleted on the server. But went I tried to connect to this instance from a remote computer using Query Analyzer it failed. I originally suspected there was firewall or something. So I tried pinging the server. I got response and it showed the same IP address as when I ping it on the Server itself. I open up SQL server network utility on the server and found the port number that the SQL2000 instance was listening on and then I tried to telnet to this port on the remote computer. I was able to connect to this port on the remote computer. So it proofed there was no firewall blocking the connection to the SQL2000 instance.
I could not connect to the instance using the name “ServerName\SQL2000″ but I have verified the port was listening so I tried to connect to “Servername,portnumber” and it worked. So what went wrong? If I use the instance name it didn’t work but went I use the port number it worked. It turned out that the SQL Browser Service on the server was not running. What this service does is to tell remote client what SQL server instance is running on the server. It make sense that if this service is not running then no one know what SQL2000 instance is and no one can connect to it. The problem was solved after I turned on the service.
Related Posts:
(6 votes, average: 4.17 out of 5)
Loading ...
I experienced the same problem. The sql browser service has been running. I tried restart the service and did not help. Then I found out the service account that runs the sql browser service needed permission access to the sql 2000 instance. After I granted the access, I could connect to the sql 2000 instance remotely.
Thank you!! I had the same problem. I thought it was a networking/firewall issue.
EVen I am facing the same problem. The instance is SDMSNR\SDMSNR
but how to use the same remotely by giving the IP address.
Regards,
Bhupinder Pathak
Thank u .. I spent so much of time trying to figure out and none of the links were helpful.
using the comma for port# has worked!
I was able to connect to the server with jdbc but needed the sql query analyzer to demonstrate to the user.. thanks for posting this tip!!
You guys are legends, I had this problem that appeared after the accounts used by the SQL Browser service was modified on the two machines. Thanks a lot!
Thanks this fixed my problem.