Custom Query (16363 matches)
Results (1345 - 1347 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #8155 | wontfix | Bridged Network: VM uses MAC of Host instead of MAC entered in setting for the VM | ||
| Description |
Szenario:
Because of that, IP/MAC binding isn't working because i have 2 different IP's with the same MAC. That behavior first occured in 4.0. Before the update everything worked perfectly. Because it worked i never looked up wich MAC the VM uses in the previor versions. |
|||
| #5455 | fixed | Bridged Networking Driver breaks host networking | ||
| Description |
After installing VirtualBox 3.0.10 on my workstation, my computer would have network connectivity after installation. However, after a reboot, my computer was unable to retrieve a DHCP address. Whenever I'd try to repair the connection, it gave me the error, "Failed to query TCP/IP settings of the connection. Cannot proceed." After uninstalling VirtualBox, my computer immediately retrieved a DHCP address and started to behave normally, which led me to dig a bit further. After a while, I discovered that, if the VirtualBox Bridged Networking Driver was checked on the host NIC when it booted, I wouldn't have network access. However, if I unchecked it, waited for a DHCP address on the host interface, and rechecked it, everything worked normally. I'm using an HP Compaq dc5750 with a Broadcom NetXtreme Gigabit Ethernet adapter running Windows XP Professional SP3. Let me know if you need anything else. I (hopefully) attached a screen shot of the error I received. |
|||
| #8856 | obsolete | Bridged Networking Problems with 4.0.6 | ||
| Description |
After updating from 4.0.4 to 4.0.6 network connections from outside the host (Win7_64) to the guest (Win7_32/bridged networking/fixed ip-address) break down periodically (after a few seconds and for a few seconds) and come back again. Ping requests from outside the host result in roughly 20 percent loss. Ping requests inside the host (guest to guest) work just fine. Problem appears without any firewall or other networking restrictions on host or guest. Bridged networking worked fine in 4.0.4 |
|||

