Ethernet doesn't have a valid IP configuration

Hello,

I'm about 4 hours deep into trying to fix this. I've followed several forum posts with similar issues, with no luck.

I've been running windows 10 on my PC with my current hardware (including modem/router) for about a year now with no issues. Yesterday I booted up and had no internet access. The error was something to do with "sockets". I ran the netsh socket reset command, which simply changed the error to my current invalid IP configuration error.

So here's my current state:

I'm typing this from a laptop I dug out of storage. On this laptop I have internet access both through ethernet and the on-board wifi adapter.

On my PC, the ethernet connection is through my motherboard (adapter: Interl Ethernet Connection I218-V), and I have a separate wifi card (adapter: Qualcomm Atheros AR938x). Whether connected with ethernet or wifi, the connection status is:

IPv4 Connectivity: No Network Access
IPv6 Connectivity: No Internet Access

All items in the properties list are checked, including the IPV4/IPv6 items. I've tried uninstalling/reinstalling both the ethernet and wifi adapters. I'm reinstalling from the latest Intel driver installer (PROWinx64).

I've tried the various netconfig commands. If I call "ipconfig /release" I get:

"An error occurred while releasing interface Ethernet 2: An address has not yet been associated with the network endpoint".

Here is my ipconfig /all



I've tried a dozen other things, but I don't want to convolute this post, so just let me know what to do and I'll repeat whatever steps.

Thanks!

I've fiddled with this for a few more hours with no luck. I bought a new ethernet adapter card to try out; the results were no different than with my wifi card or motherboard ethernet adapter.

Is there something to do with the motherboard I could check? What could be causing this that is independent of the adapter used?

Please halp!

You are being given a Windows Auto IP address 169.X.X.X for some reason as if the Desktop can not "see" the Router to get given an IPV4 DHCP assigned (or reserved) IP Address.

IPV6 looks like it is connected though , a good site to test IPV6 connectivity is IPv6 test - IPv6/4 connectivity and speed test

can we assume nobody is playing trick on you and changed setting on your Router ?

It looks like the Wireless Card is disabled ? it says disconnected .... Airplane Mode ? not usually on a Desktop....

If you right click the titlebar on the Command Prompt window and choose defaults , you can set the window size wider , eg 100 x32 deep works and it should use those settings on next use instead.

Kbird said:

You are being given a Windows Auto IP address 169.X.X.X for some reason as if the Desktop can not "see" the Router to get given an IPV4 DHCP assigned (or reserved) IP Address.

IPV6 looks like it is connected though , a good site to test IPV6 connectivity is IPv6 test - IPv6/4 connectivity and speed test

On my laptop, that site says my IPv4 is fine but that IPv6 is not supported, which is strange because I actually ran that test earlier today and I could have sworn it gave me green across the board. Of course, I can't run it on my PC.

Kbird said:

can we assume nobody is playing trick on you and changed setting on your Router ?

Yes, only I have access to the router. Additionally: I factory reset the router/modem and made no changes. When I set it up initially, there were no problems, so I'm hoping the factory defaults are the best way to debug this issue.

Kbird said:

It looks like the Wireless Card is disabled ? it says disconnected .... Airplane Mode ? not usually on a Desktop....

If you're referring to the "media disconnected", that's just because I wasn't connected through wifi when I took that snapshot. Figured the ethernet connection would be easier to debug. However, the information in ipconfig /all is the same for both, whichever one is being used. That, along with the fact that I've also tried a brand new ethernet card leads me to believe this is not an adapter hardware issue.

Kbird said:

If you right click the titlebar on the Command Prompt window and choose defaults , you can set the window size wider , eg 100 x32 deep works and it should use those settings on next use instead.

Thanks for that bit of info. First thing that's worked all day.

glad I got something right :)

and you are sure Your ISP just aint having issues? Or there Router ? are you Bridging with your Own router like me?

KB

Some additional information:

My router does see my PC even though the PC seems not to see the router (i.e., the router is not accessible through the browser). Accessing the router through my laptop, I can see the connected PC, but there is no device name displayed, as if the router cannot entirely see the PC either. The blacked out rectangle is my laptop device name.

Kbird said:

glad I got something right :)

and you are sure Your ISP just aint having issues?

Is it possible it could be on the ISP side even though my laptop is connecting without issue? I've been avoiding actually trying to deal with them as it's Comcast and, well, you know...

that 169 IP address is wrong ...it should be the same as the one below it in the 192 range....

169 means Windows is giving it a IP address of it's own....so DHCP may not be working or you have run out of available IP addresses eg the range set is too small eg 5 addresses and now you have 6 devices.

more info.

If your computer is set to Obtain an IP Address Automatically and it cannot locate a DHCP server, then it will likely produce an IP address similar to this 169.254.x.x IP Address The DHCP server in most home networks will be the router or modem. Some modems are a combination router and modem, so you may only have one device. In either case, the router controls DHCP. Your Windows computer has to get some type of IP address for a DHCP server. When the process fails, it gives up and uses Automatic Private IP Addressing


Any chance you got a virus? and it is messing with things ?

169 means Windows is giving it a IP address of it's own....so DHCP may not be working or you have run out of available IP addresses eg the range set is too small eg 5 addresses and now you have 6 devices.

It could also be that you have an IP # conflict , in which case Windows will just assign an Auto IP address so the network doesn't have errors.

Have you turn off all PC's , turned of your router ,turned off Comcast's Router , waited a While and the restarted Comcast's wait 10 mins, restart your router. wait 5 mins, then started PC's in the desired order of usage ......


more info here:

http://www.windowstechinfo.com/2013/07/solved-windows-8-is-having-16925401-to.html

I've run a couple quick scans throughout the day with no malware found, but I've just started a full scan. Will take a while. At this point I hope it does find something because at least then this whole thing would make sense.

I've reset everything multiple times, and also left everything turned off and disconnected for 3 hours (there were a couple posts with similar problems where this actually worked somehow).

About the incorrect IP address, I tried setting the IP address under my wifi adapter to 192.168.0.100. When I do this I get

IPv4 Connection: No internet access
IPv6 Connection: No internet access

The windows diagnosis can't find any issues and I still am apparently not connected to the network since I can't access it through the browser.

I'm pretty much just shooting in the dark since I don't know much about networking/IT, but I've tried quite a few other things, and have seen a wide variety of errors from the windows troubleshooter.

Thanks for replying. I might be out for the rest of the night but if I don't reply quickly, I'll reply first thing in the morning (I'm feeling the internet withdrawals setting in).

Will have the results of a full virus scan later.