all groups > sql server connect > december 2004 >
You're in the

sql server connect

group:

Port 1433 doesn't listen


Port 1433 doesn't listen Morten Snedker
12/3/2004 2:31:44 PM
sql server connect:
I've Googlet alot, but can't find my solution.

1. I cannot telnet on port 1433
2. SQL Server Network Utility shows 1433 on the TCP/IP.
3. netstat -an doesn't show anything using port 1433
4.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSocketNetLib\Tcp\DefaultPort
has the value of 1433 (decimal).


I'm running version:
Microsoft SQL Server 2000 - 8.00.194 on Windows NT 5.1 (Build 2600:
Service Pack 2) (XP Pro sp2).

I'm close to re-installing MS-SQL...any last resort?


Re: Port 1433 doesn't listen Ashok K Kumar
12/3/2004 9:02:34 PM
It may not be configured to work on TCP/IP!! It may be working on Named pipe
only! check the server properties (See pt 4)

[quoted text, click to view]

May be firewalled

[quoted text, click to view]

Is that "Client Network utility" that you are talking about?

[quoted text, click to view]

If I were you, I would do a simple thing. netstat -an while the server is
running and do it again while the server is shutdown and compare what
listening port is missing.

[quoted text, click to view]
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSocketNetLib\T
cp\DefaultPort
[quoted text, click to view]

I am not sure if that points to the port that should be used for listening
by the SQL instance. Check out the SQL Enterprise manager > right click on
the server > properties > General tab > Network Configuration > TCP/IP >
Properties.


--
------------------------------
Ashok K Kumar
------------------------------

AddThis Social Bookmark Button