Elite: Dangerous PvE - Mobius

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.

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

Thanks, TheBS, I've tried those and no joy. I don't even have a wireless facility in this machine, but I suppose the software doesn't necessarily know that.

Walter wrote:Thanks, TheBS, I've tried those and no joy. I don't even have a wireless facility in this machine, but I suppose the software doesn't necessarily know that.

Okay, figured I'd check to make sure. At this point, if you have a free PCIe x1 (or x4/8/16), I'd get a cheap NIC card. Sometimes the PHY just gets fried.

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

thebs wrote:Okay, figured I'd check to make sure. At this point, if you have a free PCIe x1 (or x4/8/16), I'd get a cheap NIC card. Sometimes the PHY just gets fried.

That's my thought - I can pick one up tomorrow for about £7. That should at least narrow things down to a hardware or software problem. Thanks again.

Bet that cures it......

Walter wrote:

thebs wrote:Okay, figured I'd check to make sure. At this point, if you have a free PCIe x1 (or x4/8/16), I'd get a cheap NIC card. Sometimes the PHY just gets fried.

That's my thought - I can pick one up tomorrow for about £7. That should at least narrow things down to a hardware or software problem. Thanks again.

Well, there can still be a software driver issue, especially if the add-on card uses a different driver and works. But I didn't want to get into tracking down the INF file, looking up the files in it, and then deleting them plus the INF file.

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

I had something similar happen to bluetooth on my PC. Bluetooth happens to be on the same intel card as my wifi, which never had trouble, making it doubly weird. After trying every software solution I could, I finally opened up the case, pulled the card out, and put it right back in.

As soon as I rebooted, it worked again. If your network isn't soldered directly to the motherboard, you might want to try reseating it, as dumb as that is. (I have a mini-itx motherboard, and I think the card my network and bluetooth are on is PCIe? It's some ridiculously small card and slot.)

I am quote hungover, so forgive me if this has not been suggested.

Modern PC's never fully power off unless you physically disconnect them from the mains. If the nic is in a hung state and will not respond, I suggest pulling the power cord for a minute or two and let the capacitors in the system drain.

And if that doesn't solve it, by all means pop for a new nic card.

The error messages I'm getting must be very generic as there are so many people reporting similar problems and so many finding different solutions - if they find one at all; there's a lot of frustration out there.

Being really old school (remember having to open up the case every month or so to push the processor and memory chips back into their sockets?) the first recourse is to unplug everything and restart. With everything soldered to the board these days, that's a limited option. An even older school habit: everything gets switched off at the mains at the end of every day.

Many thanks for all the suggestions - all gratefully appreciated - at least I know I've done all the right things. Off to buy a NIC as soon as PCWorld opens.