No reboot required. If the server were a domain controller then I'd do ipconfig /flushdns, ipconfig /registerdns, restart the netlogon service.
--please don't forget to Accept as answer
if the reply is helpful--
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Considering the changing of Network adapter settings and when they are actually applied, expecially considering when to be certain that these settings have applied as a dependency for application testing.
On the windows TCP/IP settings , there are various levels of settings.
I am looking at this in the context of Windows Server 2012 R2 and later.
Do changes to any of these settings require a reboot to be effective ?
If so , which changes in particular require reboot?
If no reboot is required, excuding app restarts which I would do anyway, do we require any OS specific commands to be sure ? (e.g. flushdns e.t.c. )
Kind regards,
Junaid
No reboot required. If the server were a domain controller then I'd do ipconfig /flushdns, ipconfig /registerdns, restart the netlogon service.
--please don't forget to Accept as answer
if the reply is helpful--
Hi,
In my opinion, you do not need reboot.
By resetting your network configuration, run as administrator to start Command Prompt, run the following commands one by one: ipconfig /release> ipconfig /renew> ipconfig /flushdns. After running these commands, your network configuration will reset.
Best Regards,
Mulder Zhang
--------------------------------------------------------------
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.