Windows 10: Invalid IP address via USB tether or Wi-Fi, IPv4 autoconfiguration

Gday, I've seen a few threads about this but most resolutions I've seen have been tried to no avail.

So laptop has been connecting via USB tether(android phone) without issue until this week, and our other laptop still connects via that phone so no issue there.

Via USB tether the network that appears is called "Ethernet 2" or via Wi-Fi it's "My Hotspot", both, connected separately or together are both constantly "identifying" and both do not get fixed by Windows troubleshoot and return "could not fix, invalid IP address.

Both show an IPv4 Autoconfigured IP address of 169.254.x.x, we've tried Command Prompt ipconfig release and renew, disabling/enabling adapters, setting IPAutoconfigure value to 0 in Registry Edit, setting a static IP to 192.168.x.x, amongst others.

Does anyone have anything to suggest for a solution?

Your advice is appreciated in advance!

Thanks

:)

 

Invalid IP configuration for wired ethernet on Windows 10

The above line says that you are not getting an IP address from your DHCP server. This could happen with a defective router. Switching it off and on again might fix the problem. Alternatively you could set a fixed IP address. What is your router's IP address?

 

Mobile hotspot is not sending internet access

The IPv4 address on the Microsoft Wi-Fi Direct Virtual Adapter # 2 card is not a valid IP address.

Open Command Prompt and type netsh wlan show wirelesscapabilities

Post the result.

 

You normally don't see APIPA addressing unless the node can't reach a DHCP server. Is the local WiFi access point providing DHCP? If not, it needs to be enabled or supplied. If so, you might want to try a wired connection between the device and the laptop just to see if it can get DHCP that way. Then you can start troubleshooting the wireless DHCP access (probably by visiting the WAP mfgr's forums or support site). What I find interesting about this is the failure with static IP assignment, unless you didn't also include the gateway address (usually 192.168.0.1) and addresses for DNS servers in the static configuration page (probably from your ISP).
HTH,
--Ed--

PS: Last week's Current Branch cumulative update KB3201845 is said to cause problems with a network service that ties to DHCP on some Windows 10 PCs. It's supposed to be fixed by Tuesday's KB3206632. If you've applied the former but not the latter to the affected machine, applying the newer update may fix the problem all by itself.

 

Solution:
I found the solution for me. I had 169.254.x.x and also a static IP address simultaneously on the same NIC. That's really not possible or valid. I tried DHCP and then back to static and couldn't fix it. I ended up setting an IP address on that NIC 192.168.1.111 and then going to advanced and adding a second IP address 192.168.1.222 to have two IP addresses on the same NIC. This somehow pushed out the DHCP Autoconfiguration. I then set my NIC back to DHCP and that solved that issue. I then set my NIC back to a static IP address which is what I wanted in the end and it solved the double conundrum of DHCP and static simultaneously on the same NIC issue as well as DHCP not working properly by handing out an autoconfiguration IP address of 169.254.x.x on the same NIC. DHCP works now. Static works now.
-miletx.com

 

Bizarre and unexpected, but very helpful. And a beautiful piece of inspired troubleshooting. Thanks for sharing.
--Ed--

 

Gday Ed and Miletx

Will check both options and respond to assist anyone else with same issues.

Cheers