VMware Communities
m0rg4n
Contributor
Contributor
Jump to solution

My guest can't see the host or can't communicate with the network, networking is set to bridged, Host O/S is Windows XP sp3

Hello from Spain,

i'm running vmware workstation 6.0.2 on a windows xp sp3 with two virtual machines, one xp and a windows 2003 enterprise edition. Non of my guests can't see the host computer or other computers in the LAN, and in the host when i click show "Entire Network", "Microsoft Windows Network" i can only see the domain to wich the guests belongs but not the dc when i double click the icon of the domain. Networking is set to Bridged to the NIC connected to the LAN.

Thanks.

0 Kudos
1 Solution

Accepted Solutions
prakashraj
Expert
Expert
Jump to solution

Hi,

No mesage in post

put route print in command prompt for both host and guest and send the report

Prakash

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

View solution in original post

0 Kudos
26 Replies
AWo
Immortal
Immortal
Jump to solution

Disable all firewall and try to ping by IP address.

Post "ipconfig /all" from the host AND the guests.


AWo

VCP / VMware vEXPERT 2009

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
0 Kudos
m0rg4n
Contributor
Contributor
Jump to solution

-


>"ipconfig /all" on host operating system

Windows IP Configuration

Host Name . . . . . . . . . . . . : workstation

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connecti

on

Physical Address. . . . . . . . . : 00-A0-D1-6B-AA-E8

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.1.35

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : 192.168.1.40

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Networ

k Connection

Physical Address. . . . . . . . . : 00-19-D2-70-A1-7B

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.1.70

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.1

DNS Servers . . . . . . . . . . . : 80.58.61.250

80.58.61.254

-


>ipconfig /all on the guest operating system

Windows IP Configuration

Host Name . . . . . . . . . . . . : server1

Primary Dns Suffix . . . . . . . : morgan2.net

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : Yes

WINS Proxy Enabled. . . . . . . . : Yes

DNS Suffix Search List. . . . . . : morgan2.net

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter

Physical Address. . . . . . . . . : 00-0C-29-6E-14-CA

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.1.37

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.1

DNS Servers . . . . . . . . . . . : 127.0.0.1

-


> ping from the guest to the host:

C:\Documents and Settings\Administrator>ping 192.168.1.35

Pinging 192.168.1.35 with 32 bytes of data:

Reply from 192.168.1.35: bytes=32 time=72ms TTL=128

Reply from 192.168.1.35: bytes=32 time<1ms TTL=128

Reply from 192.168.1.35: bytes=32 time<1ms TTL=128

Reply from 192.168.1.35: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.35:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 72ms, Average = 18ms

-


>ping from the host to the guest:

C:\Documents and Settings\newbe>ping 192.168.1.37

Pinging 192.168.1.37 with 32 bytes of data:

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Ping statistics for 192.168.1.37:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Thanks.

0 Kudos
AWo
Immortal
Immortal
Jump to solution

I assume that the ping from the host to the guest doesn't work, because for communication (like ping) only one path can be used. As you have two network cards in one IP net (the physical one and the wireless one) it seems that the wireless is used and thereby it never reaches the guest.

Check if the wireless card is configured to be the primary network connection in Windows or disable it for testing. Verify that whe it is disabled the VMware VMnet0 virtual switch (the bridged connection) uses the physical wired network card. You can do that in the "Virtual Network Editor" of VMware Workstation (Edit > Virtual Network Editor > Host Virtual Network Mapping".


AWo

VCP / VMware vEXPERT 2009

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
0 Kudos
prakashraj
Expert
Expert
Jump to solution

Hi ,

From the IP configuration you have given

the Ping request from Host goes through the wireless network card (192.168.1.70) but that could not be reachable to guest

Actually it should go through 192.168.1.35 Intel(R) PRO/100 VE Network Connection

All you have to do is to change the access order of NICs in

open network connections -> select Advanced -> Advanced settings -> and move 192.168.1.35 Intel(R) PRO/100 VE Network Connection to first and then try ping guest from host

Also disable wireless card and try

Prakash

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!
0 Kudos
m0rg4n
Contributor
Contributor
Jump to solution

Thanks, both of you were right. The order of the NIC's was changed, but correcting this still the same problem. All firewalls are disabled, the order of the nic's is changed and i tryed also disabling the wireless card, but ping only goes from the guest to the host and not from the host to the guest. Also the net view command on the host only shows the workstation not the virtualized computers, net view command on guest shows "there are no entries in the list". On guest Through "entire Network" / "Microsoft Windows Network" i can see the virtual domain but nothing inside it (my domain controller).

I also tried putting the "local area connection" cards in a different range than the wireless card.

Thanks a lot.

0 Kudos
prakashraj
Expert
Expert
Jump to solution

Hi,

So your network has gateway address

check in physiacl NIC it is not present

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connecti

on

Physical Address. . . . . . . . . : 00-A0-D1-6B-AA-E8

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.1.35

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : 192.168.1.40

Also check that Automatic Bridging in virtual network editor tab Intel(R) PRO/100 VE Network Connectiion selected

Prakash

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!
m0rg4n
Contributor
Contributor
Jump to solution

hi prakashraj,

i changed the ranges of the local area connection but it doesn`t work

i `ve two NIC's in the host computer:

Intel(R) PRO/100 VE Network Connection, ip address 10.10.10.10/24 (the local area connection) without a default gateway (with another computer on the same network at ipaddress 10.10.10.12/24)

Intel(R) PRO/Wireless 3945ABG Network Connection ip address 192.168.1.70/24, gateway 192.168.1.1 and dns servers 80.58.61.250 and 80.58.61.254

in the local area connection of the guest os i configured an interface with 10.10.10.11/24 and no gateway, dns server 127.0.0.1

when i want internet access i switch without problems the guest os bridge to the wirelesscard. That works fine. When i want access to the LAN i switch to the wired card with problems: i can ping from the guest to

the host but not viceversa.

Yes, i take a look at "automatic bridging" and is not checked so there are no excluded NIC's.

Thanks.

0 Kudos
AWo
Immortal
Immortal
Jump to solution

I'm getting confused now....

In your first post the Intel adapter had a different IP than you posted now (10.10.10.10/24).

Please make sure:

1. That the vNIC is set to "bridged"

2. That the bridged connection uses the Intel pNIC

3. That host and guest are in the same IP subnet range (either 10.10.10.0/24 ro 192.168.1.0/24)

4. That the wireless is disabled (the order of NIC's doesn't play a role then)

5. That VMnet1 and VMnet8 (if present) do not have the same IP address range as the physical NIC and the BRIDGED vNIC have

6. Ping by IP address, not by name

7. The default gateway doesn't play a role, yet as both machines are (should be) in the same IP subnet

If that doesn't work, post "ipconfig /all" form host and guest (without cutting something), the guect .vmx file and screenshots from the Virtual Network Editor showing your setup.


AWo

VCP / VMware vEXPERT 2009

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
0 Kudos
m0rg4n
Contributor
Contributor
Jump to solution

Hello AWo,

i reply to this address because in the e-mail i received says:

"To reply to this message, either reply to this email (recommended) or visit the message page: http://communities.vmware.com/message/1319314"

the wireless is disabled and there are no firewalls. On the guest i can not run windows firewall because:

"Windows Firewall because another program or service is running that might use the network address translation component (Ipnat.sys)"

Thanks AWo.

2009/7/23 AWo <communities-emailer@vmware.com<mailto:communities-emailer@vmware.com>>

,

A new message was posted in the thread "My guest can't see the host or can't communicate with the network, networking is set to bridged, Host O/S is Windows XP sp3":

http://communities.vmware.com/message/1319314#1319314

Author : AWo

Profile : http://communities.vmware.com/people/AWo

Message:

0 Kudos
AWo
Immortal
Immortal
Jump to solution

Just a test:

Enable VMnet1 and the VMware DHCP server service on the host, set the guest vNIC to be "host-only" and set its IP configuration to DHCP. Try to ping between them by IP again.


AWo

VCP / VMware vEXPERT 2009

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
0 Kudos
m0rg4n
Contributor
Contributor
Jump to solution

Hello AWo,

setting the guest vNIC to host-only, enabling vmnet1 and vmware DHCP server service on host (NAT service also enabled):

pinging through vmnet1

ping from guest to host:

C:\Documents and Settings\Administrator>ping 192.168.180.1

Pinging 192.168.180.1 with 32 bytes of data:

Reply from 192.168.180.1

,

A new message was posted in the thread "My guest can't see the host or can't communicate with the network, networking is set to bridged, Host O/S is Windows XP sp3":

http://communities.vmware.com/message/1319772#1319772

Author : AWo

Profile : http://communities.vmware.com/people/AWo

Message:

0 Kudos
AWo
Immortal
Immortal
Jump to solution

Post "route print" from guest and host in this configuration "host-only", please.


AWo

VCP / VMware vEXPERT 2009

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
0 Kudos
m0rg4n
Contributor
Contributor
Jump to solution

0 Kudos
AWo
Immortal
Immortal
Jump to solution

Your last post contained....nothing Smiley Sad


AWo

VCP / VMware vEXPERT 2009

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
0 Kudos
prakashraj
Expert
Expert
Jump to solution

Hi,

No mesage in post

put route print in command prompt for both host and guest and send the report

Prakash

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!
0 Kudos
m0rg4n
Contributor
Contributor
Jump to solution


&gt; ROUTE PRINT FROM HOST

==============================

=============================================

Interface List

0x1 ........................... MS TCP Loopback interface

0x2 ...00 50 56 c0 00 08 ...... VMware Virtual Ethernet Adapter for VMnet8

0x3 ...00 50 56 c0 00 01 ...... VMware Virtual Ethernet Adapter for VMnet1

0x4 ...00 a0 d1 6b aa e8 ...... Intel(R) PRO/100 VE Network Connection - Pack

Scheduler Miniport

===========================================================================

===========================================================================

Active Routes:

Network Destination Netmask Gateway Interface Metric

10.10.10.0 255.255.255.0 10.10.10.10 10.10.10.10 20

10.10.10.10 255.255.255.255 127.0.0.1 127.0.0.1 20

10.255.255.255 255.255.255.255 10.10.10.10 10.10.10.10 20

127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1

192.168.63.0 255.255.255.0 192.168.63.1 192.168.63.1 20

192.168.63.1 255.255.255.255 127.0.0.1 127.0.0.1 20

192.168.63.255 255.255.255.255 192.168.63.1 192.168.63.1 20

192.168.180.0 255.255.255.0 192.168.180.1 192.168.180.1 20

192.168.180.1 255.255.255.255 127.0.0.1 127.0.0.1 20

192.168.180.255 255.255.255.255 192.168.180.1 192.168.180.1 20

224.0.0.0 240.0.0.0 10.10.10.10 10.10.10.10 20

224.0.0.0 240.0.0.0 192.168.63.1 192.168.63.1 20

224.0.0.0 240.0.0.0 192.168.180.1 192.168.180.1 20

255.255.255.255 255.255.255.255 10.10.10.10 10.10.10.10 1

255.255.255.255 255.255.255.255 192.168.63.1 192.168.63.1 1

255.255.255.255 255.255.255.255 192.168.180.1 192.168.180.1 1

===========================================================================

Persistent Routes:

None

-


&gt; ROUTE PRINT FROM GUEST

IPv4 Route Table

===========================================================================

Interface List

0x1 ........................... MS TCP Loopback interface

0x10003 ...00 0c 29 6e 14 ca ...... VMware Accelerated AMD PCNet Adapter

===========================================================================

===========================================================================

Active Routes:

Network Destination Netmask Gateway Interface Metric

127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1

192.168.180.0 255.255.255.0 192.168.180.138 192.168.180.138 10

192.168.180.138 255.255.255.255 127.0.0.1 127.0.0.1 10

192.168.180.255 255.255.255.255 192.168.180.138 192.168.180.138 10

224.0.0.0 240.0.0.0 192.168.180.138 192.168.180.138 10

255.255.255.255 255.255.255.255 192.168.180.138 192.168.180.138 1

===========================================================================

Persistent Routes:

None</div>

0 Kudos
m0rg4n
Contributor
Contributor
Jump to solution

2009/7/24 eduardo_vila <edu.bit.es<http://edu.bit.es>@gmail.com<http://gmail.com

0 Kudos
m0rg4n
Contributor
Contributor
Jump to solution

0 Kudos
m0rg4n
Contributor
Contributor
Jump to solution

0 Kudos