I have a brand new Windows 7 system (the host) and I've installed Workstation 9.
I have two Ubuntu guest machines installed.
My system is connected to a local router all on the 192.168.1.x subnet
Here's my problem:
My guest systems can ping each other, the internet and other systems on my local subnet.
The host can reach the internet and other systems on my local subnet BUT NOT the guest systems.
Both quest systems are configured to have a Bridged Network Connection.
I've shutdown the windows firewall and that doesn't seem to help the situation.
Any help or information would greatly be appreciated.
Thanks!
Are you able to ping the guests from other systems on the network, i.e. do the guests have a firewall/block ICMP traffic?
André
Thanks for the reply.
Yes, other systems on my local network can reach the guests.
The only machine that can't reach the guests is the host machine itself...
Thanks.
I have 2 questions:
1) Are you using wireless adapter on host?
2) Are you using nic teaming?
Show us the following info from host pls:
1) Output of
netsh wlan show interfaces
2) Output of
netsh lan show interfaces
3) Output of
ipconfig /all
And ifconfig from guests.
wlnx - thanks so much for the response. here's all of the information you asked for. The only thing i'm not 100% on is nic teaming but I don't believe i have anything like that configured. Thanks!
1.) not using wireless adapter on host - using wired connection
2.) I did not know what nic teaming was. I looked it up and it does not look like anything like that has been configured on my system.
--------------------------------------------
Output of "netsh wlan show interfaces"
There is 1 interface on the system:
Name : Wireless Network Connection
Description : Dell Wireless 1504 802.11b/g/n (2.4GHz)
GUID : 18d4595b-cf42-42b0-a9e1-a3937ffa9653
Physical address : b8:76:3f:0d:8c:21
State : disconnected
Hosted network status : Not available
--------------------------------------------------
Output of "netsh lan show interfaces"
The Wired AutoConfig Service (dot3svc) is not running.
------------------------------------------------------
ipconfig /all (on host system)
Windows IP Configuration
Host Name . . . . . . . . . . . . : ***********
Primary Dns Suffix . . . . . . . : **********
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : *************
Wireless LAN adapter Wireless Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : home
Description . . . . . . . . . . . : Dell Wireless 1504 802.11b/g/n (2.4GHz)
Physical Address. . . . . . . . . : B8-76-3F-0D-8C-21
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82579LM Gigabit Network Connecti
on
Physical Address. . . . . . . . . : B8-CA-3A-D5-C5-6B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.30(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Wednesday, May 08, 2013 3:40:40 PM
Lease Expires . . . . . . . . . . : Friday, May 10, 2013 8:35:23 AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter VMware Network Adapter VMnet1:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet
1
Physical Address. . . . . . . . . : 00-50-56-C0-00-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::514c:a53b:6ada:3bfb%20(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.59.251(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 520114262
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-CD-9E-CC-B8-CA-3A-D5-C5-6B
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter VMware Network Adapter VMnet8:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet
8
Physical Address. . . . . . . . . : 00-50-56-C0-00-08
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::bcf0:47f4:c91f:7133%21(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.239.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 553668694
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-CD-9E-CC-B8-CA-3A-D5-C5-6B
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{BBFAF5FB-0A4A-45F4-9318-560D743F80F4}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 12:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.home:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6ab8:59:839e:e8e6:346e(Prefer
red)
Link-local IPv6 Address . . . . . : fe80::59:839e:e8e6:346e%14(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter isatap.{E8B5B7D8-6069-4342-83EA-51EB67C07A80}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{24046915-A27B-4847-B25B-A42D2CA87B28}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
--------------------------------------------------------------------------------------------------
ifconfig (host 1)
eth0 Link encap:Ethernet HWaddr 00:0c:29:6f:8d:44
inet addr:192.168.1.40 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:866 errors:0 dropped:0 overruns:0 frame:0
TX packets:597 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:95634 (95.6 KB) TX bytes:33459 (33.4 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:159982 errors:0 dropped:0 overruns:0 frame:0
TX packets:159982 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:42752212 (42.7 MB) TX bytes:42752212 (42.7 MB)
------------------------------------------------------------------------------
ifconfig (host 2)
eth0 Link encap:Ethernet HWaddr 00:0c:29:f2:04:6d
inet addr:192.168.1.50 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fef2:46d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:364 errors:0 dropped:0 overruns:0 frame:0
TX packets:242 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:41658 (41.6 KB) TX bytes:30997 (30.9 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4911 errors:0 dropped:0 overruns:0 frame:0
TX packets:4911 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2087848 (2.0 MB) TX bytes:2087848 (2.0 MB)
Wow, I see many letters. =)) Could you ping both guests from host and from other system in your network and show us your arp-table?
BTW, can guests reach the host?
Thanks for getting back to me.
So, my IP Addresses have changed a bit because I have a new guest that I'm currently using but I'm experiencing the same issue. I'm therefore only pinging just one guest at this point.
The guests cannot reach the host and vice-versa.
So, the new guest is Ubuntu as well and its IP Address is 192.168.1.19
192.168.1.19 (guest)
192.168.1.21 (host)
ARP Table from Guest when pinging from host (192.168.1.21) to guest (192.168.1.19)
s2support@s2ncinit:~$ arp -a
? (192.168.1.19) at 00:0c:29:e2:74:77 [ether] on eth0
? (192.168.1.1) at 00:24:b2:6f:66:e8 [ether] on eth0
ARP Table from Guest (192.168.1.19) when pinging from another system (192.168.1.20) on the network
s2support@s2ncinit:~$ arp -a
? (192.168.1.19) at 00:0c:29:e2:74:77 [ether] on eth0
? (192.168.1.20) at 5c:26:0a:31:fd:8a [ether] on eth0
? (192.168.1.1) at 00:24:b2:6f:66:e8 [ether] on eth0
Is it correct that you can reach one (new) guest from host? If it is, try to remove network interfaces from unreachable guests and create new ones. Maybe, it'll help you.
Sorry - no, what I meant to say (but I know I confused things) was that I've added a new guest and that is the one that I'm working with right now
BUT NO the guest cannot see the host or vice-versa.
So, I'm still in the same situation just with a new VM from the time that I first entered this problem.
Thanks!
Well...
I completely confused.
Please, ping both guests from host (yes, pings will fail) and show me host's arp-table after this.
Then ping both guests from another machine in your network and show me arp-table of the machine.
And tell me IP-addresses of the guests, host and another machime, that you used to ping.