IP Address Not Sticking

[FN-GM]

Hello,

 

I have needed to change the IP address of our exchange server. We are running Exchange 2013 on Server 2012, this is on Vmware 5.5. I removed the old E1000 nic and added a new VMXnet3 nic. I booted a server and assigned an IP all was ok. When i reboot the server normally it seems to go a little bit weird. On the console the server "looses" its IP. It runs dead slow and won't respond to my commands, after about 40 mins something seems to un-jam and i can use it normally. I do an IP config its show a 169 address but the NIC is sill configured with the correct static IP address. If i set the NIC to DHCP then change it back to static again all is ok and it goes back to normal, no issues. I reboot and we have issues again.

 

Anyone any ideas please?

 

Thanks

[FN-GM]

Any ideas anyone please? This one is being a swine!

[twin--turbo]

I would remove all nic hardware including hidden/disabled ones in windows.

 

Reboot and let it detect the hardware again.

 

Set the IP and see if that helps.

 

Had a similar issue on Citrix.

[FN-GM]

I think I have sorted it by resetting the IP stack. The annoying things is, when I am testing it with a reboot it was taking ages to get cracking with things.

[KLashbrook]

Look into or create an ARPRetryCount registry setting: SYSTEM\CurrentControlSet\services\Tcpip\Parameters\ArpRetryCount

 

It's a DWord. Set it to 0.

The 169.x.x.x addresses following a reboot should stop.

[ITGURU]

Not sure why you would need to remove and re-add network adapter just to change the IP address,

 

I've recently done an exchange 2010 to 2013 migration and just changed the IP address on the old exchange server so could re-use on the new one. Rebooted and as long as it's updated the IP address in DNS it had no other effects on any services.

[FN-GM]

This was from 2013 so bit behind. I didn't add and remove the interface to change the IP. I did it so I can use 10GB network connection.