Migrate VMs via vMotion cross vCenter on VMware vSphere 6.7

7. Reconfigure the virtual machine network (if the IP addressing is different)

Previously, we explained to you that it was recommended to use the same IP addressing on the source site as on the destination site using an L2 or L3 bridge.
However, in our test environment we did not do this for technical reasons.
Which means that the network connection of this virtual machine has been problematic since it was migrated to our remote site (in Paris).
You can easily see it thanks to the Windows network icon at the bottom right of the screen.

If you check the network status of your virtual machine from Windows settings, you will see that a "No Internet Access" error appears.
Note that this error may vary from one operating system to another.

As you can see, our virtual machine always has the IP address "10.0.1.22" (in our case) which corresponds to the IP addressing used on the source site (Brussels in our case) and not that of the remote site .
Additionally, the virtual machine is currently trying to contact gateway "10.0.1.10" which is on the source site and not the destination site.
Hence also the fact that Windows tells us that this virtual machine does not have access to the Internet.

To resolve the problem, you have 2 options:

• virtually disconnect and reconnect the network cable of this virtual machine by going to its settings.
• use the commands specific to the guest OS from it so that the virtual machine obtains a new IP address from the DHCP server which is on the remote server's network.

To begin, we will show you how to fix the problem via the "VMware Remote Console" (VMRC) program.
From your virtual machine console, go to: VMRC -> Removable Devices -> Network adapter 1 -> Settings.

Currently, the virtual network adapter is still connected to the virtual network shown just below (the one that was selected in the migration wizard for this VM).

Uncheck the "Connected" box and click OK.

Now that the network cable for this virtual card is virtually unplugged, go back to: VMRC -> Removable Devices -> Network adapter 1 -> Settings.

Check the "Connected" box and click OK.

Virtually unplugging and reconnecting the network cable will allow the guest operating system to detect the new network in use.
Hence the appearance of the blue banner in the case of Windows 10.

As you can see, the virtual machine has been assigned a new IP address "10.0.2.24" and gateway IP address "10.0.2.10" which now correspond to the network used at the remote physical site.

Note that in Windows, you could also use these commands to respectively reset the IP configuration of the guest operating system network card, then obtain a new IP address from the DHCP server located on the new network to which it is connected.

Batch

ipconfig /release
ipconfig /renew