Search results

Every other IP in that subnet works fine, same router, same switch.

Proxmox VE 8.2, fresh install, worked fine for about an hour then this. I have disabled firewall on the node and datacenter. The VMs are all accessible via their IPs, no issue there. But, the nodes (I have 5 nodes in a cluster), none of them are accessible 5 minutes after reboot via their IPs...

That seems to of fixed it! Thanks @_gabriel

Thanks! I'm trying the ALB right now, to see if there is a difference, turning bonding off worked. So I'm trying a different mode to see if there is a chance. Thanks!

Intel didn't even last 30 min, it just dropped. This is kind of crazy, won't stay online.

Realtek kept dying after about 20 to 30 min, switched to intel card now, it works, full gigabit speed. I guess we'll see if it lasts. The Windows 10 VM hasn't gone offline once

After using it for a half hour, installing software, all of a sudden nic went dead, no internet. Nothing changed in config. I rebooted, nothing, didn't come back. Went into device manager, disabled nic then re-enabled, came back online. At this point I don't trust this thing to take into production.

It's definitely not bond, seems to be the Virtio nic card bug found on many threads online. But I've used both the most recent version of the drivers disk and version 221, same deal. Switching to Realtek driver everything works fine.

That's the point, I need bond to work.

Just tried re-installing from scratch from the ISO, same deal. Windows server 2022 Standard

Left them both turned on overnight, this morning the Windows 10 VM has network, the Server still does not. No changes on either since yesterday morning when I installed them both.

Links have been edited and fixed.

I have a fresh clean install of Proxmox Community Edition v7.4-3. Everything worked great for setup, same as always. I did something a tad different this time, bonded the two NICs: https://i.imgur.com/2aRqwSb.jpg But it works fine on the node, as well, the Windows 10 VM worked fine for about...