NAT internet connection not working on Windows 10 Host (Windows 10 Guest)

[NeitroyintB]

Hi!

I have a testing VM running Windows 10 Pro N x64 on a Windows 10 Enterprise Host.
When I start the machine it don't get internet connection.

It is configured as NAT. (not NAT Network, only NAT)

Below you can see VM logs

[socratis]

00:00:04.791937 NAT: Guest address guess set to 10.0.2.15 by initialization

Your guest gets an IP. Can you check that this is the same IP inside the guest? 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            <-- VBox NICs start with 08-00-27
   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 <DNSserver>                  <-- tests your DNS server
> ping 1.1.1.1                      <-- tests outgoing connectivity
> ping download.virtualbox.org      <-- tests name resolution

Report any misconfiguration, or any errors from the "ping" commands.

If you can "ping <DefaultGateway>", if you can "ping <DNSserver>", 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.

[NeitroyintB]

The connection falls on the name resolution.

Code: Select all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : DESKTOP
   Primary Dns Suffix  . . . . . . . : 
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : company.com

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : company.com
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Desktop Adapter
   Physical Address. . . . . . . . . : 08-00-27-A4-1F-5D
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::c1b2:4c81:9e02:b2b9%9(Preferred) 
   IPv4 Address. . . . . . . . . . . : 10.0.2.15(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : February 5, 2019 3:06:27 PM
   Lease Expires . . . . . . . . . . : February 6, 2019 3:06:27 PM
   Default Gateway . . . . . . . . . : 10.0.2.2
   DHCP Server . . . . . . . . . . . : 10.0.2.2
   DHCPv6 IAID . . . . . . . . . . . : 101187623
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-23-DB-8A-87-08-00-27-A4-1F-5D
   DNS Servers . . . . . . . . . . . : 9.0.130.50
                                       9.0.128.50
                                       208.67.222.123
                                       208.67.220.123
   NetBIOS over Tcpip. . . . . . . . : Enabled

Pinging 10.0.2.2 with 32 bytes of data:
Reply from 10.0.2.2: bytes=32 time<1ms TTL=128
Reply from 10.0.2.2: bytes=32 time<1ms TTL=128
Reply from 10.0.2.2: bytes=32 time<1ms TTL=128
Reply from 10.0.2.2: bytes=32 time<1ms TTL=128

Ping statistics for 10.0.2.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 9.0.130.50 with 32 bytes of data:
Reply from 9.0.130.50: bytes=32 time=153ms TTL=250
Reply from 9.0.130.50: bytes=32 time=159ms TTL=250
Reply from 9.0.130.50: bytes=32 time=173ms TTL=250
Reply from 9.0.130.50: bytes=32 time=181ms TTL=250

Ping statistics for 9.0.130.50:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 153ms, Maximum = 181ms, Average = 166ms

Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=249ms TTL=50
Reply from 1.1.1.1: bytes=32 time=463ms TTL=50
Reply from 1.1.1.1: bytes=32 time=165ms TTL=50
Reply from 1.1.1.1: bytes=32 time=173ms TTL=50

Ping statistics for 1.1.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 165ms, Maximum = 463ms, Average = 262ms
Ping request could not find host download.virtualbox.org. Please check the name and try again.

[socratis]

Why so many DNS servers? Try setting the DNS in the guest statically to 1.1.1.1

[NeitroyintB]

I set it and nothing changed. I might say that this configuration is not the one given by the DHCP, this configuration is the one given by Virtual Box NAT.
I used to have a machine on a RHEL host and worked fine. The issues started when I begin using Windows 10 as Host.

Code: Select all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : DESKTOP-HC5GBSK
   Primary Dns Suffix  . . . . . . . : 
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : company.com

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : company.com
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Desktop Adapter
   Physical Address. . . . . . . . . : 08-00-27-A4-1F-5D
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::c1b2:4c81:9e02:b2b9%9(Preferred) 
   IPv4 Address. . . . . . . . . . . : 10.0.2.15(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : February 7, 2019 11:30:25 AM
   Lease Expires . . . . . . . . . . : February 8, 2019 11:30:24 AM
   Default Gateway . . . . . . . . . : 10.0.2.2
   DHCP Server . . . . . . . . . . . : 10.0.2.2
   DHCPv6 IAID . . . . . . . . . . . : 101187623
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-23-DB-8A-87-08-00-27-A4-1F-5D
   DNS Servers . . . . . . . . . . . : 1.1.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

[socratis]

The issues started when I begin using Windows 10 as Host.

The problem is with your host then. Any proxies, re-directors, antivirus, other?