WINS won't start, socket error

Greetings,

Looking through my logs I discovered that my WINS service
has failed on my Windows Server 2003 box. The problem
appears to have started immediately after a system reboot
a few days ago.

When trying to start the service I get the following error:

Windows could not start the Windows Internet Name Service
(WINS) on Local Computer. For more information, review the
System Event Log. If this is a non-Microsoft service,
contact, the service vendor, and refer to server-specific
error code -536870910.

In the in system log:

Event Type: Error
Event Source: Wins
Event Category: None
Event ID: 4193
Date: 8/17/2004
Time: 1:32:45 PM
User: N/A
Computer: MAYA
Description:
WINS could not create the notification socket. Make sure
the TCP/IP driver is installed and running properly.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: da 01 00 00 fc 2a 00 00 Ú...ü*..
__

Event Type: Error
Event Source: Wins
Event Category: None
Event ID: 4165
Date: 8/17/2004
Time: 1:32:45 PM
User: N/A
Computer: MAYA
Description:
WINS has encountered an error that caused it to shut
down.The exception code is the second DWORD of the data
section. Check previous event log entries to determine a
more specific cause for the error.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: e7 02 00 00 02 00 00 e0 ç......à
__

Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7036
Date: 8/17/2004
Time: 1:32:45 PM
User: N/A
Computer: MAYA
Description:
The Windows Internet Name Service (WINS) service entered
the stopped state.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
__

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 8/17/2004
Time: 1:32:45 PM
User: N/A
Computer: MAYA
Description:
The Windows Internet Name Service (WINS) service
terminated with service-specific error 3758096386
(0xE0000002).

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
__

I have run hardware diagnostics on my NICs (this a
multihomed server with 3 interfaces) and no failures are
flagged.

I have also followed the steps in kb317518, How to reset
TCP/IP in Windows Server 2003.

I have uninstalled and reinstalled WINS.

So far, none of that has fixed the problem.

Anyone with some ideas on what to try next? I am going to
try kb811259, Recover from Winsock2 corruption. I'll post
again.

Thanks!

Donald P. Crawford, MCSE, MCP+I, A+
IS Manager
College of Architecture, Planning + Design
Kansas State University
Manhattan, KS

"Donald P. Crawford" <(E-Mail Removed)> wrote in message
news:09b801c4848f$53e51b90$(E-Mail Removed)...
> I have run hardware diagnostics on my NICs (this a
> multihomed server with 3 interfaces) and no failures are
> flagged.

Huge "red flag" here!! Please explain the purpose and the network
configuration of the three Nics.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

>
>Huge "red flag" here!! Please explain the purpose and the
network
>configuration of the three Nics.
>
>--
>
>Phillip Windell [MCP, MVP, CCNA]
>www.wandtv.com
>
>

What you like to know? I don't see a huge "red flag" here
with the 3 NICS. If I hadn't been able to get WINS
working at all, perhaps. But it has been chuggin right
along until recently. I have been troubleshooting this
problem by going from 3 NICs to 2 to 1 with no results.
If you know something about multihomed boxes and WINS
problems, please share. :^)

DC

>
>Anyone with some ideas on what to try next? I am going
to
>try kb811259, Recover from Winsock2 corruption. I'll
post
>again.
>

Nope, killing Winsock didn't fix the problem. I am back
to square one.

DC

>
>Anyone with some ideas on what to try next? I am going
to
>try kb811259, Recover from Winsock2 corruption. I'll
post
>again.
>

Nope, killing the Winsock reg entries and reinstalling TCP
didn't fix it. Back to square one.

DC