Network Server Utility Fails

The SQL Network Server Utility fails to update the installed protocols.

SQL MSDE2000 SP4 installed on Windows 2003 R2 Standard DC server.

When MSDE2000 installs by default it only installs Shared Memory, I need
TCP/IP and Named Pipes to work.

So I ran svrnetcn from the server and added Named Pipes and TCP/IP
protocols. Applied changes clicked OK twice and then stopped my SQL instance
and restarted. I even shutdown the windows server and restarted still no
luck here is the log file which will show that only Shared Memory is
listening.

2008-12-15 21:38:39.45 server Microsoft SQL Server 2000 - 8.00.2050
(Intel X86)
Mar 7 2008 21:29:56
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine (Windows) on Windows NT 5.2 (Build 3790: Service Pack 2)

2008-12-15 21:38:39.45 server Copyright (C) 1988-2002 Microsoft
Corporation.
2008-12-15 21:38:39.45 server All rights reserved.
2008-12-15 21:38:39.45 server Server Process ID is 1588.
2008-12-15 21:38:39.45 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\LOG\ERRORLOG'.
2008-12-15 21:38:39.54 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2008-12-15 21:38:39.75 server SQL Server configured for thread mode
processing.
2008-12-15 21:38:39.75 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2008-12-15 21:38:39.92 spid3 Starting up database 'master'.
2008-12-15 21:38:41.57 spid3 Server name is 'TGCS001\SHAREPOINT'.
2008-12-15 21:38:41.57 spid3 Skipping startup of clean database id 4
2008-12-15 21:38:41.57 spid3 Skipping startup of clean database id 5
2008-12-15 21:38:41.57 spid3 Skipping startup of clean database id 7
2008-12-15 21:38:41.57 spid3 Starting up database 'STS_tgcs001_1'.
2008-12-15 21:38:41.64 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2008-12-15 21:38:41.64 server SQL server listening on Shared Memory.
2008-12-15 21:38:41.64 server SQL Server is ready for client connections
2008-12-15 21:38:41.64 spid5 Starting up database 'model'.
2008-12-15 21:38:43.85 spid5 Clearing tempdb database.
2008-12-15 21:38:51.50 spid5 Starting up database 'tempdb'.
2008-12-15 21:38:53.92 spid3 Recovery complete.
2008-12-15 21:39:05.42 spid51 Starting up database 'STS_Config'.
2008-12-15 21:40:00.07 spid3 SQL global counter collection task is
created.

I have asked several questions about this topic on the NGs but now I am
being more specific.

I have run the utility several times no changes to the log.

My other sql server log shows all three protocols listening.

Is it a registry entry that may not being set properly?
I have compared the SuperSocketNetLib NP Tcp on both computers and they
match

It is something that I am missing here.

Thanks again for all the guys who have been answering all my questions

I hope we can figure this one out

Thanks again

Tom