Tuesday, March 27, 2012

Can't get it to listen on TCP port 1433

Been having SQL Server 2000 running for some time now, but recently it stopped listening on TCP port 1433, the log reports its listening on shared memory, Named pipes and Rpc, but no sign of 127.0.0.1 port 1433 or any errors to say why it won't listen.

I've done a netstat -na and nothing else is listening on that port, tried restarting using the enterprise manager, gonna try restarting the entire Server when everyone has gone home, but I'm pretty sure its been restarted recently.

All the other archive logs going back a few days show its not listening.

Yes, I have used the Server network utility to make sure TCP/IP is enabled and set to 1433, even added a comma and 1434 to see if it will listen on multiple ports, no go.

Any help?
What service pack do you have installed?|||Have you told your firewall to allow connections to Microsoft SQL Server?|||SQL Server 2000 - 8.00.194 build 3790 Service pack 1

Mmmm, isn't SP3 out?
Lets hope it doesn't break it even more, as after the restart of the entire server last night, its now not responding to TCP connections locally 127.0.0.1

Not sure about the firewall, I'll have to check, its been fine with it for the past few years.

|||

SP4 has been out for quite some time. Here is a handy web site which lists all of the hot fix and service packs which have been released http://www.sqlsecurity.com/FAQs/SQLServerVersionDatabase/tabid/63/Default.aspx.

Start by upgrading to SQL 2000 SP4. Odds are a Windows 2000 hot fix shuts down SQL from talking over the net if prior to SP3 as there is a major security flaw prior to SP3 which the SQL Slammer worm expliots.

No comments:

Post a Comment