IPV4 NAT not working under Windows guests after VirtualBox upgrade to 7.1.0

[kabu]

After upgrading VirtualBox to 7.1.0 more users on forum report lost of network connectivity for Windows virtual machines when using NAT: ​https://forums.virtualbox.org/viewtopic.php?t=112323 ​https://forums.virtualbox.org/viewtopic.php?t=112320

Reported are problems on Windows 11, 10, 7, XP guests. In my case Linux OEL8 worked fine. My host system is Windows 11.

For Windows VM machines I have only one adapter configured, Intel PRO/1000 MT Desktop (NAT). ipconfig /all in VM shows IP address 169.254.x.x (Auto Configured), which is probably automatic private ip address, when it can't get one from DHCP server. ipconfig /release and ipconfig /renew did not helped, address stays 169.254.x.x Tried also to disable IPV6 binding for this virtual ethernet adapter in VM, in ipconfig /all output ipv6 adresses disappeared for this network, but ipv4 stays same 169.254.x.x

Guest additions were also upgraded to 7.1.0 version, not helped.

Reinstalled older VirtualBox 7.0.20 and after Windows 11 guest VM startup, network is back working, getting correct address 10.0.2.2. Other user reported that VirtuaBox 7.1.0 Beta 2 also worked fine, so it looks like regression in 7.1.0 GA release.

[tutralex]

Workaround - manually fill in the IPv4 adapter parameters:

IPv4 Address: 10.0.2.15
IPv4 Mask: 255.255.255.0
IPv4 Default Gateway: 10.0.2.2
IPv4 DNS Server: 10.0.2.3

[tutralex]

BTW, there are many other bugs besides this, be it 3D acceleration, etc. I don't understand how you can post such raw software...

[goldsun77]

i have the same problem with kubuntu 24.04 and a Windows 11 guest, interestingly running it in bridge mode gives me networking problems mainly with youtube but under nat mode it works ok, also, in bridge mode but running nordvpn on top of it, things work kind of ok i wonder what is the main problem. Everything works with DHCP ipv4

[maxonthebox]

As an additional workaround, which leaves the guest untouched, it is possible to change the network mode of a failing interface to something else (e.g., internal network) and then back to the intended setting (e.g., NAT) while the affected VM is running.

This seems to restore operation of NAT mode at least, and works on different platforms (Windows, macOS, Linux). Must be carried out for each affected interface of each affected VM every time the VM is started but, in principle, it could at least be scripted using VBoxManage while a fix is being worked on.

Since statically assigning an IP address to the guest as suggested in comment #1 also works, it seems that some internal per-interface DHCP service is failing to start when expected, unless forced to do so by the run-time network mode change. Unfortunately, the VM log does not seem to emit any relevant messages concerning VirtualBox's network driver when the network mode of an interface is changed.

As a side note, guest additions have nothing to do with networking (you may want to check out the related documentation).

[boxer01]

Just tested the new development snapshot (7.1.1-164842). The issue with connection speed on NAT is still here. Now it already starts with slow speed and stays so till the end. It isn't important if I have turned IPv6 on or off. I wrote more in the linked forum post.

[John P.]

Another workaround to the NAT issue is to create and use a NAT Network. It may not work in corporate environments with locked down hosts.

[boxer01]

Looks like fixed on my Windows 10 host and Windows 11 guest combination as of 7.1.1 r164917.

[jfmorin]

In my case — Windows 10 host and Windows 10 guests — version 7.1.1 r164917 didn't fix the issue. I rolled back to version 7.0.20.

[kalomakac]

In my case - Windows 10 host and Ubuntu 22.04 host looks like the problem is fixed as of 7.1.1 r164917.

[quizerti]

I would like to add that I have tried r164917 and the problem is not fixed for my Windows 10 host and it's Windows 10 guest machines.

After approximately 2 hours the guest will lose internet connection. The only solution is to completely shut the guest down and start it again, as restarting does not resolve the internet connection to the host. Just to keep my internet connection out of the equation, when the guest loses internet connection the host's internet connection is working fine.

I have created my own thread with logs here: ​https://forums.virtualbox.org/viewtopic.php?t=112444

If requested, I will create a separate ticket for this.

[hamelg2]

I have this bug. Windows 10 host and archlinux guest. I tried version 7.1.1 r164917 but it didn't solve the problem. no other solution than to revert to version 7.0.20:(

[quizerti]

My problem still persists in v7.1.2 r164945.

Replying to quizerti:

I would like to add that I have tried r164917 and the problem is not fixed for my Windows 10 host and it's Windows 10 guest machines.

After approximately 2 hours the guest will lose internet connection. The only solution is to completely shut the guest down and start it again, as restarting does not resolve the internet connection to the host. Just to keep my internet connection out of the equation, when the guest loses internet connection the host's internet connection is working fine.

I have created my own thread with logs here: ​https://forums.virtualbox.org/viewtopic.php?t=112444

If requested, I will create a separate ticket for this.

[galitsyn]

Hi guys,

VirtualBox 7.1.2 has been released last week. This issue should be fixed in this version. You can download it from here. Than you for reporting the issue.

[boxer01]

The next ticket for this issue is #22189.