sql server connect: SQL Server 2000 not listening on TCP port -- sql server connect

SQL Server 2000 not listening on TCP port

Aram
10/12/2005 1:29:01 PM

sql server connect:
Hello,

I have a brand new install (with latest MDAC and SP) installed. In the SQL
Server Network Utility both Names Pipes and TCP/IP are "enabled" I chose
1433 as the port for the TCP connection. However the SQL Server Log only
shows Named Pipe:

SQL Server is ready for client connections
SQL server listening on Shared Memory, Named Pipes, Rpc.
Clearning tempdb database.

Re: SQL Server 2000 not listening on TCP port

Brad Sarsfield
10/12/2005 1:44:25 PM

Hi Adam,

You must restart the SQL server service for it to pick up any changes made
in the Server Network Utility. If you restart SQL and it still is not
listening on the port you may have another application listening on 1433.
You can find out if this is the case with the following command.

netstat -an | findstr 1433

--
Brad Sarsfield [MSFT] bradsa(at)microsoft.com

This posting is provided "AS IS", with no warranties, and confers no rights.

[quoted text, click to view]