By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,767 Members | 1,302 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,767 IT Pros & Developers. It's quick & easy.

SQL Server 2000 cannot listen on TCP/IP!

P: n/a
Hi all!

I just tried to enable TCP/IP on SQL Server 2000 (trial, SP3a). The
Server Network Utility shows it's already turned on, but after
restarting the server doesn't listen to any TCP port, and in the
eventlog it reports "SuperSocket info: gethostbyname(MSAFD Tcpip
[TCP/IP]) : Error 11004." and "SuperSocket info: (SpnRegister) : Error
2102.". I googled but found nothing helpful. Does anyone know what's
wrong??

The OS is Windows 2003 Server Enterprise Edition.

Jul 23 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a

"Aquila Deus" <aq*********@yahoo.co.uk> wrote in message
news:11*********************@z14g2000cwz.googlegro ups.com...
Hi all!

I just tried to enable TCP/IP on SQL Server 2000 (trial, SP3a). The
Server Network Utility shows it's already turned on, but after
restarting the server doesn't listen to any TCP port, and in the
eventlog it reports "SuperSocket info: gethostbyname(MSAFD Tcpip
[TCP/IP]) : Error 11004." and "SuperSocket info: (SpnRegister) : Error
2102.". I googled but found nothing helpful. Does anyone know what's
wrong??

The OS is Windows 2003 Server Enterprise Edition.


This KB article lists a few possibilities:

http://support.microsoft.com/kb/q307197/

If that doesn't help, could you post the relevant messages from the SQL
Server log, which should show which protocols are in use? And how have you
verified that the server isn't listening? Does netstat show the MSSQL port?

Simon
Jul 23 '05 #2

P: n/a

Simon Hayes wrote:
"Aquila Deus" <aq*********@yahoo.co.uk> wrote in message
news:11*********************@z14g2000cwz.googlegro ups.com...
Hi all!

I just tried to enable TCP/IP on SQL Server 2000 (trial, SP3a). The
Server Network Utility shows it's already turned on, but after
restarting the server doesn't listen to any TCP port, and in the
eventlog it reports "SuperSocket info: gethostbyname(MSAFD Tcpip
[TCP/IP]) : Error 11004." and "SuperSocket info: (SpnRegister) : Error 2102.". I googled but found nothing helpful. Does anyone know what's wrong??

The OS is Windows 2003 Server Enterprise Edition.

This KB article lists a few possibilities:

http://support.microsoft.com/kb/q307197/

If that doesn't help, could you post the relevant messages from the

SQL Server log, which should show which protocols are in use?
Shared Memory (and Named Pipe if I enable it).

It doesn't show anything like "bind failed", the gethostbyname is the
only relevant event logged.
And how have you
verified that the server isn't listening? Does netstat show the MSSQL

port?

Both tcpview and netstat show that MSSQL doesnt listen on any TCP port.
I didn't use dynamic port and force encryption.
However, I just successfully connected to it via named pipe (thanks to
a jTDS dev :).

Jul 23 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.