Proxmox 8.3.3 - guest windows server 2019 no internet

[roboto]

Hello.
Im using proxmox 8.3.3 and after many tries I registered here to ask if anyone has a solution.

Guest operating system windows 2019 has no internet connection. I tried many things, checked instructions for default bridge settings but that somehow completely breaks my network.

I am renting a dedicated server and my intention is to use windows as a remote desktop.

I use virtIO drivers, everything is installed but I'm getting a yellow triangle over the network icon.

I am not sure how to configure linux bridge (vmbr0) which I created manually.

Every single tutorial I found on youtube has their internet just work out of box after virtIO drivers install.

I'm spinning in circles for days re-installing server and breaking network settings.

 

[Moayad]

Please provide us with the network configuration from the Proxmox VE server `cat /etc/network/interface` and the Windows VM config `qm config <VMID>` as well as the screenshot of the network configuration inside the VM. This can help us identify where is the issue.

 

[roboto]

content of the /etc/network/interfaces

# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

auto enp2s0
iface enp2s0 inet static
address xx.xxx.xxx.46/23
gateway xx.xxx.xxx.1
dns-nameservers 62.141.32.5 62.141.32.4 62.141.32.3
dns-search host
# dns-* options are implemented by the resolvconf package, if installed

auto vmbr0
iface vmbr0 inet manual
bridge-ports none
bridge-stp off
bridge-fd 0
bridge-vlan-aware yes
bridge-vids 2-4094

Please note that I've hid the server IP and host name, i do not want someone tho google this and start pinging or brute force me.

qm config

bios: ovmf
boot: order=scsi0;ide0;ide2;net0
cores: 8
cpu: x86-64-v2-AES
efidisk0: local:101/vm-101-disk-0.qcow2,efitype=4m,pre-enrolled-keys=1,size=528K
ide0: local:iso/virtio-win-0.1.266.iso,media=cdrom,size=707456K
ide2: local:iso/en_windows_server_2019_vl_x64_by_AG_06.2023.iso,media=cdrom,size=5554208K
machine: pc-q35-9.0
memory: 18000
meta: creation-qemu=9.0.2,ctime=1738239105
name: w19
net0: virtio=BC:24:11:CA:136,bridge=vmbr0,tag=1
numa: 0
ostype: win10
scsi0: local:101/vm-101-disk-1.qcow2,iothread=1,size=1600G
scsihw: virtio-scsi-single
smbios1: uuid=9798ba4d-fd5b-4098-b434-954f67a56cbd
sockets: 1
vmgenid: 0eb95a48-90a5-49c9-acf4-4a73b76b1ec3

Virtual machine config in attachments

 

[Moayad]

Thank you!

To understand the situation (correct me if I not understand correct!). The issue is that your main NIC `enp2s0` has the server's IP, but `vmbr0` is set to `manual` with no `bridge-ports` defined. That means the VM's virtual NIC is essentially `bridged` to nothing... so it can't reach the outside network and ends up with that 169.x.x.x address. Typically, you'll want to move the IP address/gateway from the main NIC onto `vmbr0` then include it as the port for `vmbr0` e.g.:

auto lo
iface lo inet loopback

auto enp2s0
iface enp2s0 inet manual

auto vmbr0
iface vmbr0 inet static
    address xx.xxx.xxx.46/23
    gateway xx.xxx.xxx.1
    bridge-ports enp2s0
    bridge-stp off
    bridge-fd 0

And then give the public IP to the Windows VM manually inside the VM.

 

[roboto]

Thanks!
This is the first time that I didn't completely break the network.

However I still can't make the internet work on the VM. Are you referring to a server's IP? Cause that's what I assigned in vm settings.

I'll just delete a vm and make new one, i messed too much with a settings. Will see how it goes.

Ok, still not working but this is the first time ever I was offered an option to allow VM to bee seen on the network and I selecte "yes"

 

[roboto]

Ok... I'm stuck.
This is current settings on the vm.

 

[roboto]

One more update, network says that it's connected now (with the settings above) but internet still does not work.

 

[_gabriel]

is public ip really end /23 ?
I bet on /32, which is 1 public ip, like rented dedicated online, which need SDN (or add iptables rules manually) for PVE act as router / Masquerading, for VM as only host can have the only 1 public ip.