Duplicate IP address in the virtual machine with Windows OS

[Maxime_mtp]

Hello,

I have a problem with VMs that host a windows OS (windows 10 or server)

When I install the windows OS on a proxmox virtual machine, either in static IP address or by DHCP, the configuration appears at startup with a duplicate IP address (an address in 169 ... and the distributed IP address automatic or static).


I also had this case, but for a virtual machine where the network configuration apparently worked correctly on first boot, however, when I reset it from proxmox at boot, it went back to network configuration with IP address in double. This duplicate IP address configuration prevents network communication from the machine.

I think it is a problem of configuration at the level of the network card on Proxmox, but even when changing the network card model (E1000 -> virtIO), the problem persists.

Impossible to do a command ipconfig /release | ipconfig /renew (even in admin mode)

Do you have any leads on where can this problem come from?

 

[Arvyr]

What's your NIC configuration? Checked if all VMs use the same MAC-address?

 

[spirit]

https://fr.wikipedia.org/wiki/Automatic_Private_Internet_Protocol_Addressing

https://wiki.wireshark.org/APIPA

169.254.0.0/24 are autoconfig ip, but only when no static ip is setup or no dhcp ip is receive.
(and you shouldn't have duplicate apipa ip, as it's using arp to find already used ip)


I hope you don't use static ip in this range right ?

 

[Maxime_mtp]

What's your NIC configuration? Checked if all VMs use the same MAC-address?

My configuration of the network interface card is as follows:

1st virtual machine:

IP: 172.16.10.3
mask: 255.255.255.0
gateway: 172.16.10.1
MAC: C6-C8-60-FB-67-18

2nd virtual machine:

IP: 172.16.10.4
mask 255.255.255.0
gateway: 172.16.10.1
MAC: 06-D4-7A-C8-84-E4

Do you need more information about the NIC configuration?

And I just checked the MAC addresses of all my machines and they have a unique MAC address for each of them

 

[Maxime_mtp]

https://fr.wikipedia.org/wiki/Automatic_Private_Internet_Protocol_Addressing

https://wiki.wireshark.org/APIPA

169.254.0.0/24 are autoconfig ip, but only when no static ip is setup or no dhcp ip is receive.
(and you shouldn't have duplicate apipa ip, as it's using arp to find already used ip)


I hope you don't use static ip in this range right ?

I know that addresses starting with 169.X.X.X are APIPA type addresses.

So I tried the following manipulation:

I switched the IP configuration back to DHCP mode.

Since it cannot find a DHCP server, an APIPA address has been assigned to it and the static address that I had assigned to it has disappeared so there is no longer any duplicate addressing. However, what I want is to assign its IP in static (because it is a windows server)

So I switch back to IP addressing in static mode by assigning it an IP, the subnet mask, the gateway and the DNS.

Normally, on any type of system, if I switch a network interface back to a static IP address, the DHCP mode is deactivated and the address assigned to it (APIPA address or address distributed by the DHCP server) disappears. But here, when I make the command "ipconfig / all" the DHCP mode appears as "disabled" but the APIPA address is always assigned to the network card.

Consequently, I perform an ipconfig / release but this command seems to switch the IP addressing back to DHCP mode, which means that the APIPA address is always present. So even if I switch back (in graphic mode or in command mode) to static IP addressing, the APIPA address does not want to be deleted.

 

[spirit]

https://www.itprotoday.com/windows-78/how-can-i-disable-apipa
?

 

[Maxime_mtp]

https://www.itprotoday.com/windows-78/how-can-i-disable-apipa
?

I have already done the manipulation to disable the automatic IPv4 configuration via the registry (at the beginning I did the manipulation only on the network interface concerned, then with the tutorial that you provided me, I did manipulation so that deactivation applies to any network card)

I then restarted the virtual machine. And when I make the command "ipconfig / all" the IP address of type APIPA no longer appears. However, the IPv4 autoconfiguration setting always indicates the status "activated" and the network card always detects that there is a duplicate IP address (the term "double" appears right next to the static IP address that i have assigned).

I also tried to switch off the VM, delete the network card and then recreate it via the VM configuration of proxmox. But nothing changes, the APIPA IP address is no longer visible but it is always detected twice with the parameter (even with the "IPAutoconfigurationEnabled" registry key)

There is not a command line configuration on the proxmox terminal which could make this bug disappear on VMs with a windows host?

Otherwise I will try to perform my test infrastructure on another Hypervisor (VMWare or Hyper-V) because I have never had these problems on these hypervisors ...

 

[Arvyr]

Weird...well can you post a screenshot of your network configuration of proxmox (web page and maybe also the interfaces file)?

 

[spirit]

>> However, the IPv4 autoconfiguration setting always indicates the status "activated" and the network card always detects that there is a duplicate IP >>address (the term "double" appears right next to the static IP address that i have assigned).

Are you sure is not simply that you can setup a static ip on a e1000 interface, then switch to virtio nic interface, and setup the same ip again ?

because windows register ip address by pci slot location, and e1000 vs virtio are not the same slot. (Don't remember exactly how, but you need to display phantom/hiddenn nic, and remove the ip on old interface)

 

[Maxime_mtp]

>> However, the IPv4 autoconfiguration setting always indicates the status "activated" and the network card always detects that there is a duplicate IP >>address (the term "double" appears right next to the static IP address that i have assigned).

Are you sure is not simply that you can setup a static ip on a e1000 interface, then switch to virtio nic interface, and setup the same ip again ?

because windows register ip address by pci slot location, and e1000 vs virtio are not the same slot. (Don't remember exactly how, but you need to display phantom/hiddenn nic, and remove the ip on old interface)

When I change to go from an E1000 network card to a VirtIO network card, when I restart the machine, no network card is detected ...
So I changed the SCSI controller for VirtIO, but it didn't change anything.
I tried to create a new VM with a windows server 2016. I passed the addressing in static IP, and I still have the address in duplicate

I'm desperate ...

The only solution I currently see is to reinstall the hypervisor. But this is not my responsibility.

[EDIT] Ok I will try this solution, I hope it wiil works : https://pve.proxmox.com/wiki/Windows_10_guest_best_practices

I'll keep you informed

 

[Maxime_mtp]

I tried the solution mentioned in the link but it does not work either.

This solution installs PCI and network drivers for VirtIO virtual hardware but does not solve the problem of duplicate IP addressing.

 

[alex.d]

Hi,

Windows probes for a tentative IP address at the same time the switch is probing for device status. This is usually triggered by rebooting which results in a duplicate ip address. To prevent the duplicate ip address on the network the windows system assigns an APIPA address to the adapter. (ie. 169.254. x.x)
They are the following:
1) Modifying the registry:
In my opinion, you may try the following workaround:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Set IPAutoconfigurationEnabled (32-bit DWORD) to 0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Set ArpRetryCount (32-bit DWORD) to 0
2) Vía netsh:
netsh interface ipv4 set interface 11 dadtransmits=0 store=persistent
Hopefully, it can help and looking forward to your feedback.

 

[VDNKH]

Hi team,

The same thing happened to me today after a power failure.
The VM said duplicate IP even though only that VM had it, I searched with ARP through the routers / switches and did not detect anything strange.

I tried deleting and adding interfaces to the VM but the same thing happened on each interface

In the end I deleted all the interfaces in DEVMGMT.MSC that appear in the network section, including the driver (virtio)

Once I did this I turned off the VM and added an E1000 network interface with a handwritten MAC, not the random one generated by proxmox

When I turned it on I set the IP and everything works correctly

I'm not sure what could have caused it but this is how I solved it

Maybe a problem with the VIRTIO driver?