pmitllc
asked on
Windows 10 Static IP Configuration loses DNS Server after a reboot.
Hello,
I have a domain network with a Server 2012R2 Essentials server.
On one of the Windows 10 clients, I have it configured with a static IP on the network card's properties.
Whenever this PC is rebooted it loses the DNS server (it is blank) and it needs to be manually put back into the network card properties in order to get back online.
Before a reboot
After a reboot
I have attempted uninstalling and reinstalling the network card, Resetting the WINSOCK entries, Resetting IPv4 TCP/IP stack, but the problem continues to happen whenever the PC is rebooted or shut down.
I have a domain network with a Server 2012R2 Essentials server.
On one of the Windows 10 clients, I have it configured with a static IP on the network card's properties.
Whenever this PC is rebooted it loses the DNS server (it is blank) and it needs to be manually put back into the network card properties in order to get back online.
Before a reboot
After a reboot
I have attempted uninstalling and reinstalling the network card, Resetting the WINSOCK entries, Resetting IPv4 TCP/IP stack, but the problem continues to happen whenever the PC is rebooted or shut down.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This is a bug that started with vista, continued to exist until win10 as of today.
You can solve it by simply choosing a new ip. Any other IP will do and all settings "will stick".
The true solution would be to do a registry cleaning on the network settings. These are generic keys, you would have to search for them.
You can solve it by simply choosing a new ip. Any other IP will do and all settings "will stick".
The true solution would be to do a registry cleaning on the network settings. These are generic keys, you would have to search for them.
ASKER
Thanks for the responses.
@john I have tried the sfc /scannow but it came back with no errors
I have already uninstalled and reinstalled the network card as well as resetting the TCP/IP stack and winsock entries. I have also run a few virus scans but they all come back clean.
DHCP with reservations is also my preferred method and I'll probably end up implementing it here...this issue just seemed odd.
@McKnife I tried changing to a new IP, but not exactly sure if I did what you meant....I just changed the IP address to .29 as a test and left everything else the same, but it still had the same problem.
@john I have tried the sfc /scannow but it came back with no errors
I have already uninstalled and reinstalled the network card as well as resetting the TCP/IP stack and winsock entries. I have also run a few virus scans but they all come back clean.
DHCP with reservations is also my preferred method and I'll probably end up implementing it here...this issue just seemed odd.
@McKnife I tried changing to a new IP, but not exactly sure if I did what you meant....I just changed the IP address to .29 as a test and left everything else the same, but it still had the same problem.
I suggest you try the DHCP approach as it is problem - free (in my long experience with it).
"I just changed the IP address to .29 as a test and left everything else the same" - that was what I meant and it always worked here, strange!
Please look at google's results for "ip address won't stick", maybe those will help you, the problem is quite common.
Please look at google's results for "ip address won't stick", maybe those will help you, the problem is quite common.
Navigate to HKEY_LOCAL_MACHINE\SYSTEM\ CurrentCon trolSet\Co ntrol\Netw ork and deleted the binary value called Config. Then reboot.
Funny, that's the suggestion of the first hit in he suggested google search :-)
what is the english translation of "Funny, that's the suggestion of the first hit in he suggested google search"
Typo? he=>the
Typo? he=>the
I got ya. Actually I googled the question subject on this one. It was the third hit :) and seemed to work :)
https://www.experts-exchange.com/questions/28953239/Static-IP-not-being-saved.html?anchorAnswerId=41665491#a41665491
https://www.experts-exchange.com/questions/28953239/Static-IP-not-being-saved.html?anchorAnswerId=41665491#a41665491
ASKER
Sorry for abandoning this.
I ended up just setting the reservation for now and setting it to obtain automatically. It still strikes me as odd, but at least it works now when rebooted.
@LockDown Not saying that that wouldn't work, but since I have already switched it to obtain automatically and have it resolved with a reservation, I am not going to make the registry change. Maybe next time I am on site after hours I will give it a shot, but it is a moot point now.
I ended up just setting the reservation for now and setting it to obtain automatically. It still strikes me as odd, but at least it works now when rebooted.
@LockDown Not saying that that wouldn't work, but since I have already switched it to obtain automatically and have it resolved with a reservation, I am not going to make the registry change. Maybe next time I am on site after hours I will give it a shot, but it is a moot point now.
FYI, in the meantime, we had the same problem on one machine and that registry change solved it .
What solved it? Since you tried the selected solution before and did not give positive feedback, I wonder.
Try running sfc /scannow and see if it reports back that there are some corrupt files.