Walter wrote:I could really do with some expert advice here. After accidentally resetting my desktop machine by flicking the mains power switch I can no longer access the Internet - no more ED.
The Ethernet connection says: Unidentified network and the diagnosis is: Ethernet doesn't have a valid IP address.
This seems to be a common problem with as many solutions as problem reporters. I haven't found my solution. Every other device on the network - wired and unwired - can connect, but my main Win 8.1 wired desktop machine has struck out for independence. I've:
- replaced the cable
- tried a defined IP address
- reinstalled the network drivers
- netsh reset
- turned everything on and off again
I don't have McAfee and everything was working this morning - it's now 10.20pm. I suppose I could have fried the mobo lan circuits but don't have a card to test for this.
All suggestions gratefully received. BGS player with three factions and a serious ED addiction to support.
I've run into this before with Windows 8.
Windows literally maintains state on the NIC hardware/driver for PHY (physical interface) enable/disable, even if it's not a wireless NIC (aka RFkill), and the device is in the wrong state now. It's a really unnecessary and over-complicating concept, that the OS itself has to maintain the PHY state, instead of registers in the MAC (media access controller - the embedded processor in the NIC) that are accessed via WMI (Windows Management Instrumentation) to read it's actual state. I've lambasted both Microsoft and PC OEMs for this stupidity, as have some Linux developers and even a few at Intel.
Steps to try to resolve:
- Try #1: Pull up networking and right click on the device and disable. Now right-click again and enable. This usually does not work, as it doesn't toggle the PHY state, but it's worth a try.
- Try #2:. Pull up Device Manager, go to the NIC device, right-click and tell it to remove/uninstall. Now it should not longer be there. Reboot and Windows will redetected the device, load the driver and, lo'n behold, the PHY will also have its state reset.
This may not be your issue, but I've run into it multiple times. It's really only something you should see I'm a notebook for a wireless NIC. Why they do this with a wired interface on a desktop too, I have no idea.
Disclaimer: Please excuse any grammar, pathetic typos, or satanic versus known as "auto-correct" as this was posted via Tapatalk from my budget Honor 5X