Re-IP issues: Win2008R2 with VMXNET 3 Adapter

When you perform failover for a Win2008R2 server with a VMXNET 3 Adapter, configured Re-IP settings are not applied to the target replica. Instead, the Guest OS of the replica shows a NIC whose network settings have been set to DHCP.

This is a known issue with the VMXNET 3 Adapter. When Veeam Backup & Replication creates a VM replica, the replica’s PCI Express virtual network acquires a MAC address that differs from the MAC address of the source VM. This MAC address is ultimately added as a new device, so Re-IP does not function properly.

Information regarding solutions and workarounds are discussed in the following VMware article.

Deploying Windows 2008 R2 and Windows 7 templates with vmxnet3 renames the NIC as #2 (1020078)

Excerpt from that article:

During template deployment or cloning, new virtual hardware is created for the destination virtual machine. Network interfaces are assigned new MAC addresses. PCI Express devices, including the VMXNET3 virtual ethernet adapter, a new serial number is generated as well.

Windows 2008 R2, Windows 2012, and Windows 7 track PCI devices by which slot the device is connected to. Moving a PCI network interface between slots will allocate a new set of settings for the NIC as it is considered a new device. Replacing a PCI network interface with the same make and model will retain use of the previous settings. However, PCI Express devices are tracked by their serial number, which is derived from the MAC address.

When a virtual machine is created by cloning or template deployment, the new virtual machine's PCI Express virtual network interfaces have different MAC addresses and serial numbers, and are detected as new devices.

The same behavior can be observed by deploying clones of Windows 2008 R2, Windows 2012, or Windows 7 on new physical hardware with PCI Express network interfaces in the same slots.

 

---

Update February 2025: Broadcom has decommissioned the above article that documented the cause and solution for the underlying VMXNET3 issue. Based on a review of Veeam Support cases from 2015, it appears the solution previously listed in that article was to install the Microsoft Hotfix KB2344941 or KB2550978. However, Microsoft has delisted the hotfix download links, likely because Server 2008 R2 and Windows 7 reached End-of-Life on January 14th, 2020.

Customers facing this issue are now advised that the only alternative solution is to replace the VMXNET3 adapter with another compatible NIC type for VMs running Server 2008 R2 or Windows 7 VM, then perform the following steps to update the replica.

1. Delete the current VM replica.

2. Verify Re-IP settings in the properties of a replication job.

3. Re-run the replication job.

4. When a new replica is created, test failover to ensure Re-IP settings are correctly applied.