I hope you can help me with an incredibly strange issue I'm facing. I have a server that randomly seems to have decided that it wants a new static IP and no matter what I do it is forcing that IP into the NIC settings. It should have the .169 address assigned to it but no matter how many times i remove the .22 or reboot it just keeps coming back.
It's causing, as you can imagine to have inconsistent network connectivity and the server is failing to do its job. Luckily so far the the Hyper V host that has the .22 address doesn't seem to have thrown up any errors but I suspect this is more through luck than anything else and it will start to cause issues sooner rather than later.
anyone ever experienced this or got any ideas as I am fresh out!
Best Answer +PeterUK , 07 October 2013 - 14:16
Remove the gateway IP and the two IP's check in
and delete the any PersistentRoutes (do not delete the key) then re-add your IP and gateway settings.Go to the full post