My USB wireless network adapter gets a limited connectivity message in the notification tray but no packets are being sent or recieved. It does, however, recognize my network on the available connections list - so it's not totally dead. When I switch to a wired connection I get "no connections available". This is the case even on a new PCI ethernet controller. Details:
Problem happened after installing new memory and clearing the CMOS (to troubleshoot a problem). LAN is working on a fresh Windows install on a different hard drive. Therefore, I've rulled out a hardware failure as the source of the problem.
Device Manager does not list any problems. Everything is recognized. In Network Connections, three Local Area Connections are present and Windows recognizes when the ethernet cable is plugged in. The hardware lights on the wired NIC function properly.
Windows Network Diagnostis reports that "Windows couldn't automatically bind the IP protocol stack to the network adapter" and pings to IP addresses like 192.0.0.1 or 192.168.0.1 get a "transmit failed. General failure" message.
Everything is set to obtain IP addresses and DNS automatically. Also, I haven't knowingly changed any settings from the time it was working until it/they stopped working.
Ipconfig doesn't list any information. It just reads:
Windows IP ConfigurationSolutions Tried So Far:
Host Name..............: Monolith
Primary Dns Suffix...:
Node Type...............: Hybrid
IP Routing Enabled...: No
WINS Proxy Enabled..: No
Where I'm at:
- Uninstalled antivirus software
- Cleared the CMOS and reset defaults
- Ensured that the NIC and USB controller are enabled in the BIOS
- Reset winsock and tcp/ip using netsh commands
- Updated LAN and wLAN drivers
- Ran and ipconfig /release and /renew. Result: "The operation failed as no adapter is in the state permissible for this operation."
- Attempted a System Restore, but it failed. Gave me an "unspecified error".
- Flushed DNS
- Installed a new PCI ethernet controller
I can't figure out why both NICs would be giving me trouble at the same time. It seems like Windows just can't handle anything trying to use TCP/IP no matter what I throw at it. Despite Windows knowing about the hardware and thinking everything is fine, it seems like it can't access it correctly to connect. I know it isn't a hardware issue, despite that being an obvious answer. I just don't know what is wrong.
Please help me.