I have migrate a couple of VMs from ESX to a Proxmox 8.3. Most work fine but one of them keeps having issues with getting network connectivity.
The network adapter keeps stating "Unidentified network". Tried with E1000 and the virtio driver but both same result.
Created a new VM from scratch (W2022) with the same network settings as working VMs but see the same issue - Unidentified network.
The test VM is a W2012 server, Windows Firewall is turned off, it has the correct VLAN tag (same as others which are working) and the correct static IP info.
NIC in the VMs hardware setup in Proxmox has correct VLAN and firewall is turned off.
Have looked at some of the tips re the network-location service but to no avail.
(delayed start, reg setting)
I'm using Proxmox with 3 NICs, across 2 bridges. 1 bridge for management and 2 (bonded) for VMs running in Proxmox.
Both eno2 and eno3 are going into same switch.
If I remove eno3 from the bond and create a new bridge (vlan aware) for it, the failed VMs start networking. Not sure what is causing the bond not to work.
The network adapter keeps stating "Unidentified network". Tried with E1000 and the virtio driver but both same result.
Created a new VM from scratch (W2022) with the same network settings as working VMs but see the same issue - Unidentified network.
The test VM is a W2012 server, Windows Firewall is turned off, it has the correct VLAN tag (same as others which are working) and the correct static IP info.
NIC in the VMs hardware setup in Proxmox has correct VLAN and firewall is turned off.
Have looked at some of the tips re the network-location service but to no avail.
(delayed start, reg setting)
I'm using Proxmox with 3 NICs, across 2 bridges. 1 bridge for management and 2 (bonded) for VMs running in Proxmox.
auto vmbr0iface vmbr0 inet static address x.x.x.51/26 gateway x.x.x.56 bridge-ports eno1 bridge-stp off bridge-fd 0 bridge-vlan-aware yes bridge-vids 2-4094auto vmbr1iface vmbr1 inet manual hwaddress x:x:x:x:x:x bridge-ports bond0 bridge-stp off bridge-fd 0 bridge-vlan-aware yes bridge-vids 2-4094Both eno2 and eno3 are going into same switch.
If I remove eno3 from the bond and create a new bridge (vlan aware) for it, the failed VMs start networking. Not sure what is causing the bond not to work.
Last edited: