Opened 4 years ago

#19536 new defect

Problems when switching from "NAT" to "Bridge" and vice versa. VM is not assigned an IP address via DHCP when using "Bridge".

Reported by: RonaldMcDonald Owned by:
Component: network/NAT Version: VirtualBox 5.2.40
Keywords: Cc:
Guest type: Windows Host type: Windows


Host is a Windows 10 (Build 1909). If you change in Virtualbox 5.2.40 with a VM (Windows 10 (Build 1909) in the network area from "NAT" to "Bridge" the VM does not get a new IP address via DHCP within the VM. With Virtualbox 5.2.38 it works with the same host and with the same VMs without problems online. You can switch between "NAT" and "Bridge" and the VM gets an IP address internally via its DHCP service. This can also be observed in the DHCP server of the network.

The error is reproducible and occurs immediately after installing Virtualbox 5.2.40 and disappears as soon as Virtualbox 5.2.38 is installed again.

Change History (0)

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use