Running the "netsh winsock reset" command fixed the problem for me. It seems like it has something to do with a broken Winsock LSP. We do not use Microsoft AntiSpyware, so this is not the program that caused this.
This event can occur after you install Aventail Connect version 3.01S on a computer that runs Windows 2000 Professional or Windows 2000 Server. See ME297524
for details on this issue.
See "JSI Tip 3996" for additional information about this event.
I have encounter this exact problem tied with event 7024. The events were caused by the improper removal of NewDotNet spyware by Microsoft Windows AntiSpyware. After searching groups for hours, I have found the links “NewDotNet” and “LSP-Fix”, which helped me to resolve the issue.
Backup your registry prior to use in case you need to revert, but for me it fixed the Winsock LSP broken chain.
From a newsgroup post: "I recently restarted one of our Windows 2003 servers (not a DC, just a member server) after some software updates. When it came back up, I was able to log in as normal, but the Netlogon service failed to start and this event was logged in the event log. It seems that for some reason, the IPSec service had entered block mode, so I disabled the service and rebooted the server. It came up like a charm".
See the link to "Winnetmag Article ID 38380" for additional information.
I got this error in after uninstalling AVM Fritz Card. Along with this error I also received event 1006 from source Dhcp. The following steps worked for me:
1. Uninstall TCP/IP protocol (do not restart after uninstalling)
2. Delete the following registry keys:
4. Install TCP/IP protocol again.
This event is usually followed by an Event 7024 ("The Net Logon service terminated with service-specific error 5737"). The problem is discussed in ME303330