How to safeguard against IP configuration problems
The problem described below has been resolved. What I am looking for is understanding as to why it happened, what was affected, and how might I safeguard against the problem happening again.
From one day to the next, my ipconfig went from this:
to this:
Notice a few things that are different:
-Connection-specific DNS suffix was wiped-out
-IPv4 address was assigned 169.254.x.x (which I laterlearned was a symptom of the DHCP server assigning a default IP????)
-Subnet mask changed from 255.255.255.0 to 255.255.0.0
Default Gateway was wiped-out / unassigned. Which meant, of course, that I could not see or get to my router.
I tried googling and applying the solutions that made sense (and even some that didn't) including:
-ipconfig release / flush / renew
-netsh commands (various)
-unplugging power to my router(s), both cable and wireless, then powering-them back on (zero help)
-deleting letting Windows reinstall the wireless NIC adapter driver
-tried to hard-code DNS settings (IP and Gateway settings) instead of letting them be automatically assigned. This never helped.
-sacrificed chickens
-vodoo dolls
-What finally worked was resetting Windows. Fortunately I was able to keep my files. But I am having to re-install all of my applications,including Microsoft Office, Visual Studio, Visual Studio Code, SQL Server,and Adobe Web CS4. It's a pain.
I know next to nothing about networking, but after hours of research on this problem it seems to have to do with my DHCP Server failing to assign an IP address to my client (to my laptop)?
Does that sound right?
I am wondering what can be done to prevent this from happening again? Is it the result of corruption that is fixable via RegEdit, or the reinstatement of some obscure file somewhere that I can backup and replace?
Would a deeper knowledge of networking under Windows 10 help me? Recommendations?
It seems to me that if a re-install of Windows 10 fixed this, then it is an operating file issue, which means some sort of file corruption that the re-install FIXED. So - what was corrupted?
Thank you so much. No problems the past few days since I re-installed.
From one day to the next, my ipconfig went from this:
Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . : hsd1.ut.comcast.net
IPv6 Address. . . . . . . . . . . : 2601:681:77f:c059:a1bf:653d:6494:f619
Temporary IPv6 Address. . . . . . : 2601:681:77f:c059:5c7c:a1a4:1235:a8f0
Link-local IPv6 Address . . . . . : fe80::a1bf:653d:6494:f619%5
IPv4 Address. . . . . . . . . . . : 192.168.1.116
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::b675:eff:fe63:f4a4%5
192.168.1.1to this:
Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::89f9:299b:1f80:bb7b%9
Autoconfiguration IPv4 Address. . : 169.254.187.123
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :Notice a few things that are different:
-Connection-specific DNS suffix was wiped-out
-IPv4 address was assigned 169.254.x.x (which I laterlearned was a symptom of the DHCP server assigning a default IP????)
-Subnet mask changed from 255.255.255.0 to 255.255.0.0
Default Gateway was wiped-out / unassigned. Which meant, of course, that I could not see or get to my router.
I tried googling and applying the solutions that made sense (and even some that didn't) including:
-ipconfig release / flush / renew
-netsh commands (various)
-unplugging power to my router(s), both cable and wireless, then powering-them back on (zero help)
-deleting letting Windows reinstall the wireless NIC adapter driver
-tried to hard-code DNS settings (IP and Gateway settings) instead of letting them be automatically assigned. This never helped.
-sacrificed chickens
-vodoo dolls
-What finally worked was resetting Windows. Fortunately I was able to keep my files. But I am having to re-install all of my applications,including Microsoft Office, Visual Studio, Visual Studio Code, SQL Server,and Adobe Web CS4. It's a pain.
I know next to nothing about networking, but after hours of research on this problem it seems to have to do with my DHCP Server failing to assign an IP address to my client (to my laptop)?
Does that sound right?
I am wondering what can be done to prevent this from happening again? Is it the result of corruption that is fixable via RegEdit, or the reinstatement of some obscure file somewhere that I can backup and replace?
Would a deeper knowledge of networking under Windows 10 help me? Recommendations?
It seems to me that if a re-install of Windows 10 fixed this, then it is an operating file issue, which means some sort of file corruption that the re-install FIXED. So - what was corrupted?
Thank you so much. No problems the past few days since I re-installed.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
John:
Note: I updated my question details since you posted, possibly.
Note: I updated my question details since you posted, possibly.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
he tastiest way to sacrifice chickens is to fry them.
: P
in all it leads to the same, the DHCP did not provide an IP when requested....
What is a DHCP server and where does it reside? Can it be monitored? Can I have some sort of warning or indication about WHY it is failing?
To my knowledge, nothing had changed from one day to the next. It just .... STOPPED WORKING ... and then when I ran ipconfig to see what was the matter ... the 169.254.x.x was there and the Default Gateway had disappeared. BTW, there are 2 other computers connecting wirelessly, and they never had any problems during all of this.
I still don't feel like I have a good understanding of why a Windows OS reinstall would fix this? What did the reinstall change?
In addition to the things we listed (TCP/IP Reset and Drivers), Windows 10 applies all driver updates it can, so it may have been driver interference that the reinstall repaired.
ASKER
DHCP wiki
It seems my wireless NIC may have been failing to SEND the request? Or does the 169.245.x.x assignment signify that the wireless NIC requested an IP and the DHCP server did not respond or respond properly?
No problems were indicated with the device / driver for the wireless NIC card before or after I uninstalled and re-installed it. So I wonder what Windows did differently?
I guess it is difficult to prevent this from happening?
I know ONE fix: Reinstall Windows.
I am hoping for a less dramatic fix if this happens again.
The DHCP operates based on the client–server model. When a computer or other device connects to a network, the DHCP client software sends a DHCP broadcast query requesting the necessary information. Any DHCP server on the network may service the request.
It seems my wireless NIC may have been failing to SEND the request? Or does the 169.245.x.x assignment signify that the wireless NIC requested an IP and the DHCP server did not respond or respond properly?
In addition to the things we listed (TCP/IP Reset and Drivers), Windows 10 applies all driver updates it can, so it may have been driver interference that the reinstall repaired.
No problems were indicated with the device / driver for the wireless NIC card before or after I uninstalled and re-installed it. So I wonder what Windows did differently?
I guess it is difficult to prevent this from happening?
I know ONE fix: Reinstall Windows.
I am hoping for a less dramatic fix if this happens again.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Makes sense, and my research seemed to support those 2 potential problems.
If it was a virus, which one?
Would finding and isolating / cleaning the virus fix the corruption?
Is there software BESIDES anti-virus, that specifically guards against attacks that render your wireless NIC cards unusable?
Thanks!