All that the VirtualBox NDIS6 Bridged Networking Adapter does is allow the virtual machine to share the host's physical NIC. If the guest gets an IP from your router and can connect to the router it is hard to see how the problem has anything much to do with VirtualBox. Both VMWare and VBox works OK in NAT mode.VBox sometimes doesn't get an IP but can work to get to the router with fixed IP in that case (but doesn't work any further than the router's IP).VBox sometimes gets IP and I can log in the router and it resolves DNS with the browser, but can't reach anywhere (ping, browser.).VMWare can't netowrk (browse, ping.) even with fixed IP. VMWare can't get an IP from Gargoyle's DHCP. VMWare's Bridged mode can't even get an IP from the router! I've looked at the forum and there were reports on strange behaviors regarding Bridged networking (supposedly related to late Windows 10's build) so I thought to give VMWare a try because all problems seemed to be VBox problems.Īnd that was the most strange thing: VMWare has problems too. well, there were some other problems, like sometimes I started the VM and the virtual NIC 1 and 2 were swapped, I can't ping outside, DHCP sometimes assigns IP to the NIC, sometimes not. It all started with an old VBox version using a WinXP host, but because I was using the VMs in a conventional way (for example to do some TeamViewer work), didn't actually need Bridged mode, so I turn to NAT to solve the problem.īut recently I need to do some research on MikroTik CHR and need badly Bridged mode to use Winbox, so I installed CHR on VBox, set up 2 NIC and. It's a clean machine! I've installed a clean XP to retest in both VMWare and VBox (Vbox was installed on my PC, but following suggestions, did a clean uninstall-install vmware wasn't on my system, so I did a clean install)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |