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.
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...
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...
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...
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...
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...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.