January 14, 2005 at 5:44 am
Hi. I'm a SQL Server novice, so apologies if any of this sounds simple.
I am running Windows XP SP2, and have just installed SQLServer 2000. I need another application to connect to SQLServer, and am specifying it to do so via localhost:1433, but keep getting an error whenever I try doing so saying it cannot connect to the database. A colleague of mine has the exact same set up on his machine, and he can connect to SQL Server fine. Running 'netstat -a' at the command line on his machine reveals that the system is listening to port 1433/ms-sql-s. Running netstat on my machine shows that the system is not listening to 1433/ms-sql-ms. I have checked in Network Config in SQLServer Enterprise Manager, and TCP/IP is set to be using 1433.
To confirm this, my application can connect over the network to my colleague's SQL Server. but he cannot connect over the network to mine.
So I'm pretty sure the issue is related to this 1433/ms-sql-s problem.
Does anyone know how to resolve this? Many thanks.
January 14, 2005 at 6:59 am
Are you running the Windows Firewall? If so, check out this KB article:
http://support.microsoft.com/default.aspx?kbid=841251
By default, ports used by SQL Server are blocked.
January 14, 2005 at 7:21 am
Thanks. I just read the article, but I am not running Windows firewall, it is switched (however, I am running ZoneAlarm). I put the exception into Windows firewall anyway - no joy.
I'm running Service Pack 2 on SQLServer, am just downloading Service pack 3 now.
January 14, 2005 at 8:28 am
I just installed Service Pack 3 and that appears to have resolved the issue. perhaps it was related to the slammer worm.
Thanks.
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply