• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows sockets initialization failed - Help.

Kelemvor

Kelemvor

Lifer
Anyone seen this error before? I have a user that did some spyware removing which screwed up his TCP/IP protocol. I found some things online that talked about reinstalling the latest Windows 2000 SP (We are on SP3) which didn't help. Also removed his TCP/IP and then readded it after rebooting which also didn't help.

User is unable to do anything that requires IP at all. No web browsing, no VPN, etc. He doesn't get an IP address at all.

Any suggestions would be great.

Thanks
 
You also might try reinstalling the drivers for the NIC, then adding the TCP back in. If that doesn't work you may have a messed up registry and you might want to download and run a registry repair tool. If that doesn't work, try reinstalling windows.

Mike
 
Well we ended up removing everything associated with the network card. All the protocols and services and stuff and then letting Windows find them all again. Also ran the LSPFix which I think helped as wel because they it started working again.

Oh well.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top