I am posting after noticing a few forums are trending a issue with Windows 10 machines locking up with 169 IPs. Most are fixed with a winsock reset but there isn't a conclusion on what is causing it. I am seeing it effect machines on almost every ISP (seemingly random users, not all) across the world so i am wondering if Cox users are also effected. Anyone have idea what is going on?
Just happened to me, Teck. I had to reset the wireless adapter on my laptop due to transfer slowdown to my NAS, did a disable / enable. When it came back, no connectivity and my IP was 169.254.250.65 with a netmask of 255.255.0.0. IPv6 addresses looked normal and the DHCP server pointed to my Nighthawk router. An ipconfig - release followed by a -renew solved it for now. I've read the same thing, reports from all around the world, not local to an ISP or even a country. Haven't kept up with it today, any news on a solution?
No idea of a solution. I am just trying to isolate what's causing it first. I only have a Windows 7 laptop so can't reproduce the issue.
1. Could you still ping IPv6 IPs?
2. Did you have AVG?
3. Do you have MS Updates set to auto? Can you check if there were any recent updates?
4. Did it only happen on Windows 10 machines?
I did a test, disabled then enabled the wireless adapter again, repeat of the same, came back with a 169 address.
Tecknowhelp said:
1. Could you still ping IPv6 IPs?
Tecknowhelp said:
2. Did you have AVG?
Tecknowhelp said:
3. Do you have MS Updates set to auto? Can you check if there were any recent updates?
Tecknowhelp said:
4. Did it only happen on Windows 10 machines?
Yea, it's the weirdest thing. However, I have been seeing a lot of weird things happening since about 12/3. My computer-spider sense is going crazy!
I have only been able to be hands on with one possible effected Windows 10 machine. The OS wasn't recognizing the wireless network as trusted, making it "unrecognized" and locking it with a 169. I disabled the wireless NIC, restarted the wireless service @ services.msc then rebooted. After the reboot, I enabled the wireless NIC, and that is when I got the AVG warning that allowed me to override.
I also remember reading a article about a Windows 10 update that will allow integration of drivers, allowing for better plug and play. Since this "feels" like it's about the network discovery features, I wonder if it's related. However that update was months away.
It happened to my wife's laptop - following seems to have fixed it for now:
Start -> Settings -> Network & Internet -> Status -> "Network Reset" near the bottom, wait for the restart, it resets all network drivers back to virgin settings.
Cox's automated recording now mentions Windows 10 when you call in. It appears this is a widespread issue.
