VirtualBox cannot connect to Internet after moving to new PC

Discussions related to using VirtualBox on Windows hosts.
Post Reply
tng
Posts: 3
Joined: 5. Apr 2020, 20:17

VirtualBox cannot connect to Internet after moving to new PC

Post by tng »

After 1 full day of trying, i already tested all kind of possibilities that i can think of,
but i still can't make the VM connect to internet using the bridge adapter mode.

I moved one of my VM from 1 host machine to another one,
i tried with only moving the VM folder and i also tried the export/import appliance.
In both case, my VM in the new host cannot connect to internet.
I tried to reconfig the network adapter config, but still doesn't help.

I am using Bridge Adapter, it is the same setting as what i was using before.
I also try to test with the NAT mode, it works.
However, i want to use Bridge Adapter mode not the NAT mode.

Is there something that i can use to diagnose the reason of this?
Thanks a lot.
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: VirtualBox cannot connect to Internet after moving to new PC

Post by mpack »

tng wrote: Is there something that i can use to diagnose the reason of this?
Why don't we start with a precise error message?
tng
Posts: 3
Joined: 5. Apr 2020, 20:17

Re: VirtualBox cannot connect to Internet after moving to new PC

Post by tng »

I thought about if that could be due to different version of VirtualBox, so i try to fall back to the original version, still doesn't work.
I checked in the Show Log..., there is error message.
I simply got no error message.
This make me really stuck, i only got an exclamation mark, in the Lan connection icon inside the VM.
When i try to do ipconfig /renew, it said can't connect to the DHCP server, i guess that is the reason. But not sure what to do.
tng
Posts: 3
Joined: 5. Apr 2020, 20:17

Re: VirtualBox cannot connect to Internet after moving to new PC

Post by tng »

It is my problem
I am idiot
I just find out that is due to the Router has whitelist control, want to dump myself into the rubbish bin.
Post Reply