Ping: General Failure (vmware on vista)

Gil
10-01-2008, 04:10 PM
Hey guys. I have an odd problem that I'm not sure how to fix. I'm not sure what causes it either.

I've been using Vista on an HP TX1000 tablet/convertible laptop. (amd turion x2, 2gb pc5300, 120gb hd) I have had this system since may 2007 and it has very few problems. Usually I connect to internets with wireless, but I have used the lan connection sometimes, and it has no problem getting an address on either.

About 3 months ago, I wanted to try out virtualization. I installed VMWare Server, and eventually I installed XP on it. I wanted to use this as my work PC and join it to our work domain, having Vista use the wireless connection in my office and have the XP virtual machine use the wired connection. I mapped the nvidia gb-lan nic in VMWare's networking configuration, and assigned the virtual machine to use that connection. It worked fine, and my XP box could join the domain.

Except that this caused my Vista host to lose all networking capability. Connections just...stopped. Pinging automatically failed, and even persistent connections halted.



I messed around with the configuration, but could never resolve the issue. I'm trying out MS Virtual PC 2007 to see if it's better; I've uninstalled VMWare, but the problem persists. I'm planning to move up to vista 64 in the next few months, and basically I want to prevent the problem from happening again.

---

this is IPCONFIG and PING with my computer on the wifi, without a lan cable plugged in:

C:\Windows\system32>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : dhcp4.washington.edu
IPv4 Address. . . . . . . . . . . : 69.91.163.235
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . : 69.91.162.1

Tunnel adapter Local Area Connection* 7:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

C:\Windows\system32>ping www.google.com

Pinging www.l.google.com [209.85.171.147] with 32 bytes of data:
Reply from 209.85.171.147: bytes=32 time=9ms TTL=243
Reply from 209.85.171.147: bytes=32 time=8ms TTL=243
Reply from 209.85.171.147: bytes=32 time=9ms TTL=243
Reply from 209.85.171.147: bytes=32 time=8ms TTL=243

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


And this is the exact same setup, just 1 minute later after I plugged in the lan cable.


C:\Windows\system32>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : ee.washington.edu
IPv4 Address. . . . . . . . . . . : 192.168.141.138
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.141.1

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : dhcp4.washington.edu
IPv4 Address. . . . . . . . . . . : 69.91.163.235
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . : 69.91.162.1

Tunnel adapter Local Area Connection* 7:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

C:\Windows\system32>ping www.google.com
Ping request could not find host www.google.com. Please check the name and try a
gain.

C:\Windows\system32>ping 4.2.2.2

Pinging 4.2.2.2 with 32 bytes of data:
General failure.
General failure.
General failure.
General failure.

Ping statistics for 4.2.2.2:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Windows\system32>ping 192.168.141.100

Pinging 192.168.141.100 with 32 bytes of data:
General failure.
General failure.
General failure.
General failure.

Ping statistics for 192.168.141.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Windows\system32>ping 192.168.141.138

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

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

C:\Windows\system32>ping 127.0.0.1

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

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

C:\Windows\system32>

(192.168.141.100 is the gateway)


So I can ping myself fine, but I can't ping outside. When I had the virtual machine installed, the host couldn't ping it, and it couldn't ping the host, even when on a host-only virtual network, and even when manually set to the same address and subnet.





If you're able to give me any assistance I would thoroughly appreciate it. Like I said, I'm planning to reinstall (upgrade to vista 64) and would like to prevent this from happening again.