Guest: Windows Server 2016, Windows Server 2012 R2, Windows 7 Pro N.
VirtualBox: 5.1.28, 5.1.30, 5.2, 5.2.1 (R119001, Qt5.6.2)
Hi, just to share information to resolve "Bridged Adapter" issues encountered recently.
1. Firstly, I was using DLINK DIR-850L router at home, VirtualBox Guest can obtains IP from DIR-850L router reserved
but the Host internet connection failed if no internet activity for certain period ( 15-30 minutes ).
2. Later, I installed VirtualBox 5.2, all VirtualBox Guests cannot obtain IP anymore then I switched back to
VirtualBox 5.1.30, things work again but situation still based on statement 1 above.
3. After few days, all VirtualBox Guests failed to obtain IP again then I upgraded to latest firmware of DLINK DIR-850L
but result still the same even I upgraded to VirtualBox 5.2.1 as mentioned on this forum, the Guests subnet mask
reported as 255.255.0.0 instead of 255.255.255.0 in the router DHCP settings that I confirmed.
4. I uninstalled VirtualBox 5.2.1 and re-installed version 5.1.28 back but result still the same as statement 3 above.
5. At this moment, I noticed other devices also hard to connect to the router, and my iPod connected with subnet mask 255.255.0.0 as well.
6. From survey, DLINK DIR-850L does not supports wireless bridge, the same time VirtualBox working fine
with my office TP-LINK-MR3420-3G4G router, all Guest VMs able to obtain IP reserved on "Bridged Adapter" mode.
7. At this point, I suspected DLINK DIR-850L router could be defective and I purchased a new TP-LINK AC1750 router with wireless bridge features.
8. After replaced DLINK DIR-850L with TP-LINK AC1750, all VirtualBox Guest VMs works normally and able to obtain IP reserved again and the issues of statement 1 resolved.
9. The final VirtualBox version used here is 5.2.1 (R119001, Qt5.6.2) with "Bridged Adapter" network mode works well via TP-LINK AC1750 and TP-LINK TP-LINK-MR3420-3G4G router.
10. Done.
Conclusion of my experience is the types of Router used does affects VirtualBox "Bridged Adapter" mode.
Hopes, this solved the mistery of VirtualBox "Bridged Adapter" not working
