"Aquila Deus" <aquila_deus@yahoo.co.uk> wrote in message
news:1107174971.116391.61060@z14g2000cwz.googlegroups.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.
>

Simon Hayes wrote:
> "Aquila Deus" <aquila_deus@yahoo.co.uk> wrote in message
> news:1107174971.116391.61060@z14g2000cwz.googlegroups.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