I just worked through a similar issue. I VM server was moved to a different IP, and somewhere in the process the NIC settings had gotten lost. After logging in Locally and entering the new settings, it would appear to take them, but then immediately
assign a different IP.
I came across the following info from a colleague:
When removing a network driver using a vendor-provided uninstallation program or through Device Manager, previously entered static IP
address information may not be removed correctly from the registry. After reinstalling the network driver and reentering the same static IP address, the presence of previous registry information prevents the newly entered address information from being saved
correctly.
Resolution
Once the machine is experiencing this problem, the static IP address, Subnet mask, and Default gateway must be reentered TWICE in order
for the values to be saved correctly.
- Open the Local Area Connection / Internet Protocol Version 4 (TCP/IPv4) Properties dialog, and select "Obtain an IP address automatically",
and choose OK. From the Local Area Connection Properties dialog, choose OK
- Reenter the Local Area Connection / Internet Protocol Version 4 (TCP/IPv4) Properties dialog, and select "Use the following IP address"
- Perform the first two steps AGAIN, even though the IP address appears to be displaying properly.
*or*
- Open a command prompt under the administrator context
and run the following command TWICE, using the desired static address information. For example:
netsh interface ipv4 set address "Local Area Connection" static 10.0.0.55 255.0.0.0 10.0.0.1
Note: This first command may return an error "Object already exists"
netsh interface ipv4 set address "Local Area Connection" static 10.0.0.55 255.0.0.0 10.0.0.1
Note: This command should succeed with no errors
Sure enough I did it the simple way using the GUI method, reset it to DHCP, then re-entered the IP info and VOILA! It suddenly worked fine.
