Opened 8 years ago
Last modified 8 years ago
#15266 new defect
VirtualBox 5.0.16 - Windows 10 Host- Bridged Network
Reported by: | svalcken | Owned by: | |
---|---|---|---|
Component: | network | Version: | VirtualBox 5.0.16 |
Keywords: | Bridged Network Linux Guest Windows 10 Host | Cc: | |
Guest type: | Linux | Host type: | Windows |
Description (last modified by )
Hello,
I have on Windows 10 Host the VirtualBox 5.0.16 installed and try a Linux Guest with bridged Network. On Network tab, i can select the bridged network as interface and then the physical network device from windows. I am try to install a fresh Linux Ubuntu 14.04 LTS Server. This works fine, but the DHCP Service will not found from Linux. After setting up manual IP-addresses it will not be better. The Interface appears in the Linux system but no ping or other communication will work.
The IP-range is correct, the addresses also. Any idea what is the problem and what can i do?
Thanks Sascha
Change History (4)
comment:1 by , 8 years ago
comment:2 by , 8 years ago
The Connection is wired. Marvel Yukon 1GB Adapter. The Lan has a dhcp Server also. The Linux guest does not detect the dhcp Server. Then i have tryed with manuell IP Adresse Settings. A Ping from lan to vm resch Timeouts. The Same from guest.
The host only Adapter Works. I have this tried with Host only Interface. This Works Fine. The nat has the Same Problems.
comment:3 by , 8 years ago
Please, attach the VBox.log
file.
Please, attach packet captures done both on the host, on the interface the VM is bridged to, and on the guest. When capture is started, start DHCP client on the guest. When the client fails, stop the captures.
Thanks.
comment:4 by , 8 years ago
Description: | modified (diff) |
---|
Are you bridging to wired or wireless host interface?