[SOLVED] ESXi to Proxmox migration, DHCP server not working anymore

[karnalta]

Hi all,

Small business here, I am currently migrating from ESXi to Proxmox.

The last but not least VM to migrate is our Windows Server 2019 with the roles of AD / DNS / DHCP.

The problem is that after having set back IP address on the new virtio network adapter (the esxi one has disappeared as I changed to virtio) the DHCP role does not work anymore. From the server side, DHCP seem OK but no computer can obtain a IP from it. I am really lost, I don't really understand what can cause that.

Firewall is disabled on the VM network virtual adapter. IP / Gateway / Subnet / DNS are correctly set in the VM.

Maybe I am missing some specifics network adapter settings that Windows added when installing these roles ?

I hope someone could help me with that ? I have had to abandon for tonight and start back the EXSi VM for tomorow morning.

Thank for your help.

 

[Magnus-mercer]

Is DHCP bound to the new Virtio NIC? Or use tcpdump to capture the traffic?

 

[karnalta]

Is DHCP bound to the new Virtio NIC? Or use tcpdump to capture the traffic?

Sorry for the late update of the post but the answer was yes and no

DHCP was automatically bound to the new interface but it seem like it was bugged. I have juste unbound and rebound it and DHCP was working. Probably that the various vNIC changement has cause a bug.

So problem was not related to Proxmox but clearly to a Windows issue.