During the day, my internet connection died, actually, my NIC did... sort of.. got error 10.
I tried to uninstall and re-install it, and it seems to go back but then I get the error code 10.
I installed a new Belkin USB NIC and it installed fine but also returns error code 10. I installed a Hawking USB NIC and it installed Ok, but returns error 10. I installed an old 802.11b SohoWare PCI card, and it installs fine, but returns error 10. I installed a Marvell Yukon 88E8052 PCI-E ASF Gigabit Ethernet Controller and it installed fine, just still get the error 10. I un-installed each NIC that didn't work and re-booted before installing the next.
This all sounds like a virus that can attack any network device, as any form of network device fails on error 10.
If I didn't have a few computers laying around, I couldn't make this post. I also checked all services between the computers, networking settings, group policies, BIOS settings, etc. to look for something different on the bum machine, but nothing is obvious that caused the one machine to allow a NIC to be installed, but then cannot be used. (I'm running XP-Pro, SP2)
I ran "WinsockFix" to no avail, I tried the repair I found elsewhere (below), but it did nothing to help. How about You? Can You help?
"TCP/IP stack repair options for use with Windows XP with SP2.
Start, Run, CMD to open a command prompt:
Reset TCP/IP stack to installation defaults. netsh int ip reset reset.log
Reset WINSOCK entries to installation defaults: netsh winsock reset catalog
Reboot the machine."
Tried, no luck... (sigh...)
I tried to uninstall and re-install it, and it seems to go back but then I get the error code 10.
I installed a new Belkin USB NIC and it installed fine but also returns error code 10. I installed a Hawking USB NIC and it installed Ok, but returns error 10. I installed an old 802.11b SohoWare PCI card, and it installs fine, but returns error 10. I installed a Marvell Yukon 88E8052 PCI-E ASF Gigabit Ethernet Controller and it installed fine, just still get the error 10. I un-installed each NIC that didn't work and re-booted before installing the next.
This all sounds like a virus that can attack any network device, as any form of network device fails on error 10.
If I didn't have a few computers laying around, I couldn't make this post. I also checked all services between the computers, networking settings, group policies, BIOS settings, etc. to look for something different on the bum machine, but nothing is obvious that caused the one machine to allow a NIC to be installed, but then cannot be used. (I'm running XP-Pro, SP2)
I ran "WinsockFix" to no avail, I tried the repair I found elsewhere (below), but it did nothing to help. How about You? Can You help?
"TCP/IP stack repair options for use with Windows XP with SP2.
Start, Run, CMD to open a command prompt:
Reset TCP/IP stack to installation defaults. netsh int ip reset reset.log
Reset WINSOCK entries to installation defaults: netsh winsock reset catalog
Reboot the machine."
Tried, no luck... (sigh...)