I tried turning off the firewall, and that allows the host to ping the Windows
host adapter address 192.168.56.100. That’s expected. But the two network
adapters are still on the 192.168.56.x subnet. The NAT adapter should be on
10.0.x.0/24, and it’s not.
From: Patrice Oliver [mailto:patrice.oliver21...@gmail.com]
Sent: Saturday, August 19, 2017 00:09
To: Community mailing list of VirtualBox users
Subject: [External] Re: [VBox-users] NAT not working for Windows 10 guest on
Windows 7 host
Hello,
Did you Check about the Windows guest firewall ?
Le ven. 18 août 2017 à 16:03, Burkhardt, Glenn B UTAS
<glenn.burkha...@utas.utc.com<mailto:glenn.burkha...@utas.utc.com>> a écrit :
Using VirtualBox-5.1.26-117224, with extension pack installed.
I've turned on both a NAT and host only network adaptor in the guest, but can't
access other machines on the network. This does work with a Linux guest
running on the same host. Oddly, the two network adaptors are given IP
addresses on the same subnet. Ping works to 192.168.56.1 on the guest, but
doesn't on the host to either Win10 guest IP address. Ping on the host works
to the 192.168.56.102 address of the Linux guest.
Ideas?
$ ipconfig
Windows IP Configuration
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::cd49:8fdd:78f8:865d%13
IPv4 Address. . . . . . . . . . . : 192.168.56.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.56.1
Ethernet adapter Ethernet 2:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::6831:a6fc:fe3d:726a%7
IPv4 Address. . . . . . . . . . . : 192.168.56.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
The routing table is:
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.56.1 192.168.56.100 281
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
192.168.56.0 255.255.255.0 On-link 192.168.56.100 281
192.168.56.0 255.255.255.0 On-link 192.168.56.101 281
192.168.56.100 255.255.255.255 On-link 192.168.56.100 281
192.168.56.101 255.255.255.255 On-link 192.168.56.101 281
192.168.56.255 255.255.255.255 On-link 192.168.56.100 281
192.168.56.255 255.255.255.255 On-link 192.168.56.101 281
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 192.168.56.100 281
224.0.0.0 240.0.0.0 On-link 192.168.56.101 281
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 192.168.56.100 281
255.255.255.255 255.255.255.255 On-link 192.168.56.101 281
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
0.0.0.0 0.0.0.0 192.168.56.1 Default
===========================================================================
The host has a suitable routing table entry:
192.168.56.0 255.255.255.0 On-link 192.168.56.1 266
Curiously, the Linux guest has different subnets for the NAT and host adaptor:
glenn.burkhardt@ms110dev:~$<mailto:glenn.burkhardt@ms110dev:~$> ifconfig
enp0s3 Link encap:Ethernet HWaddr 08:00:27:ca:14:08
inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
inet6 addr: fe80::bc0a:568b:31c3:8d96/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:19 errors:0 dropped:0 overruns:0 frame:0
TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2984 (2.9 KB) TX bytes:2712 (2.7 KB)
enp0s8 Link encap:Ethernet HWaddr 08:00:27:e4:56:3c
inet addr:192.168.56.102 Bcast:192.168.56.255 Mask:255.255.255.0
inet6 addr: fe80::18ea:c58a:b5c3:81ab/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1262 (1.2 KB) TX bytes:1308 (1.3 KB)
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
http://sdm.link/slashdot<https://urldefense.proofpoint.com/v2/url?u=http-3A__sdm.link_slashdot&d=DwMFaQ&c=ilBQI1lupc9Y65XwNblLtw&r=aFlNQ5B_1gGdXF59InopHusV5BJ3TVT-NuqbNec_CcQ&m=YZ2wxJ_nAVxaZDX6koB4gD5jzeSwwREZreYX5CKKRT4&s=XvT9CYLAgOaO3_4Xb7xvoD1RNpdImdxzz3EFmwjDFsk&e=>
_______________________________________________
VBox-users-community mailing list
VBox-users-community@lists.sourceforge.net<mailto:VBox-users-community@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/vbox-users-community<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_vbox-2Dusers-2Dcommunity&d=DwMFaQ&c=ilBQI1lupc9Y65XwNblLtw&r=aFlNQ5B_1gGdXF59InopHusV5BJ3TVT-NuqbNec_CcQ&m=YZ2wxJ_nAVxaZDX6koB4gD5jzeSwwREZreYX5CKKRT4&s=UKiamqTM9oATLFMaViqeM6jS-fciIaeY3X1agOnfN_c&e=>
_______________________________________________
Unsubscribe:
mailto:vbox-users-community-requ...@lists.sourceforge.net<mailto:vbox-users-community-requ...@lists.sourceforge.net>?subject=unsubscribe
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
VBox-users-community mailing list
VBox-users-community@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
_______________________________________________
Unsubscribe:
mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe
