Page 1 of 1

Win10 nat no internet

Posted: 26. Nov 2018, 19:51
by Jazze77
Hi. New to this software.
I have a win10 guess on a win10 host. Due to a vpn issue.
My problem is that my guest win10 don't have internet access. Ping works both with ip or sitename like www-goolge-com (after setting the natdnshostresolver to on). But I can't use I browser to access the internet. Despite managing to resolve the ip. The host have its firewall on But I have limited access to it I can add rules but I can not exclude networkcards from it. For the guest I have tested both firewall on and off but no difference. Any tips or trix to resolve this. Is there a firewall in the NAT engine that I can inspect?

Sincerly
Fredrik B

Re: Win10 nat no internet

Posted: 27. Nov 2018, 11:19
by mpack
VPN connections can't be shared. Is that what you were trying to do?

Re: Win10 nat no internet

Posted: 27. Nov 2018, 13:31
by Jazze77
Hi
Maybe it can't, but it works. my issue is that port 80 and 443 seams to be blocked outgoing from the guest.

Re: Win10 nat no internet

Posted: 2. Dec 2018, 15:20
by Jazze77
Hi. a small update here. Regardless of the vpn on the host being on or off. port 80 and 443 is blocked outgoing.
I enabled the network trace option in virtualbox. and after recreating the issue on my guest I analysed the trace file and no trace of me trying to access the internet.
Anyone out there have any tips on how to fix this??

Re: Win10 nat no internet

Posted: 2. Dec 2018, 17:10
by socratis
Jazze77 wrote: Is there a firewall in the NAT engine that I can inspect?
Jazze77 wrote:port 80 and 443 is blocked outgoing
VirtualBox doesn't have a firewall.

Try the following "commands" from a Command Prompt on your guest. I've included a sample output, with only the parameters that you should be focusing on:
> ipconfig /all
   Physical Address. . . . . . . . . : 08-00-27-36-28-0C
   IPv4 Address. . . . . . . . . . . : 10.0.2.15(Preferred)
   Default Gateway . . . . . . . . . : 10.0.2.2
   DNS Servers . . . . . . . . . . . : 1.1.1.1
Then, once you have the key values, try the following commands:
> ping <DefaultGateway>             <-- tests your connectivity
> ping 1.1.1.1                      <-- tests outgoing connectivity
> ping download.virtualbox.org      <-- tests name resolution
If you can "ping <DefaultGateway>", if you can "ping 1.1.1.1", if you can "ping download.virtualbox.org", VirtualBox is working as it should. You should look elsewhere for your networking connectivity. Look in your host for firewalls, proxies, antivirus filters, web-cleaning applications, redirectors, etc.