Windows 10: Invalid IP address via USB tether or Wi-Fi, IPv4 autoconfiguration
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!
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).
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:169.254.x.x and a static IP address simultaneously same NIC
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.
Bizarre and unexpected, but very helpful. And a beautiful piece of inspired troubleshooting. Thanks for sharing.
Gday Ed and Miletx
Will check both options and respond to assist anyone else with same issues.
I did a clean install of my Win10 Home about a week ago and it all turned out for the good. However, tonight while nosing around my Network Connections I notice I am connected to the Internet by Ethernet (Realtek PCle GBF Family Controller)...
Any better / faster public DNS servers than Google's 18.104.22.168 and 22.214.171.124 for using with Web browsing on OPENVPN. (IPV4)
Using the Google DNS's is OK but I'm sure they are collecting info all the time !!!! -- mind you Google just has...
I have a two PCs on the same subnet, hardwired into the same router. Every night they timeout and sleep, Every morning my KVM software Microsoft's Mouse without Borders complains (on each PC) that it cannot find the other PC.
Both PCs have fixed...
I am an absolute extreme beginner in trying to install my own website (for my small business) using my home computer as my server for now, etc. Took me days to understand what I was supposed to install where and confusion arose many a time...
Upgraded an old win7 32-bit Dell Dimension 9200 to Win10 Pro on Friday 31st July. I intended to donate it to a school library in Kenya but shipping / customs costs high so now hoping to sell it to raise funds for the same charity.
On Friday 7th...