I have traced several of these problems to improperly configured winsock LSPs. Run "winmsd" and go to Components/Network/Protocol. Look at the names in the list, anything with "MSAFD" in it or the "RSVP xxx Service Provider" should be fine. Anything else is suspect, and uninstalling the owning program might help.
If that fails or your provider list is empty, you may need to rebuild the catalog from scratch. The following instructions will rebuild your catalog for TCP/IP. If you are using any other transports (If you don't know, then you probably aren't) then you will have to reinstall them as well.
NOTE: You may want to print out these instructions or save them to your hard disk before starting.
3. Go to the network connections folder, right click the icon for your network connection, and select properties.
4. Click install, choose "protocol", and click "add..."
5. Click "Have Disk...", enter "\windows\inf", click OK
6. Select "Internet Protocol (TCP/IP), click OK
7. When the process in complete, reboot
Ken Wickes [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
"Lost and Confused" <michael....@navy.mil> wrote in message news:firstname.lastname@example.org... > Okay. Computer lost connectivity randomly, as far as i > now nothing happened to it. Now, it pulls an Automatic > ip, the widnows 169.254 b.s. If you do the renew > command, it says > "Error on Interface bla bla: An operation was attempted > on something that is not a socket." > I tried replacing Winsock and Winsock2 in Registry to no > effect, and reinstalling networking, to no effect. > Also, IPSec service and the netlogon service willnot > start. They give error message: " Error 10106: The > requested service provider could not be loaded or > initialized." > Am out of ideas.. please help!