Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

vmware 1.0.4 server host cannot ping guest?

Status
Not open for further replies.

zaccaz

MIS
Aug 10, 2005
270
HK
Hi there,

Host server w2k3 std sp2, running with vmware 1.0.4, 1 active nic, the rest of the nic disabled on w2k3 server.

In the vmware 1.0.4 server, already got 5 other vm guest systems running without problem.

Now I added the 6th vm guest system, just a wxp pro sp3, from this vm guest I can ping the host server, I can ping the rest of the internal servers, I can ping & browse internet without any issues.

Here come the strange problem - from the host server itself, or from the rest of the computers, all cannot ping this 6th vm guest system.

Checked that ipaddr config on host & 6th guest system should be all right.
No windows own firewall, or any other 3rd party firewall running on both host & 6th guest system.
On the host, arp -a resolved the correct mac addr of 6th guest system.

I've no idea what else went wrong, any comments? Many thx!
 
oh boy, that's a really old version.

Don't remember if that supported NAT or not. But if your NATing, switch to bridged for your implementation. I would also suggest moving to the free 5.1 hypervisor when you can, it will work a lot better for you in the long run.

If there are no firewalls in play, the symptoms sound like an IP address conflict. The host can ping the VM, but the VM can't ping the host? It usually is both work or both do not with that kind of test. When only one way works, and a firewall is not in the mix, then I think you have another device on your network with the same IP address as the new guest. So try shutting down the new guest and ping the IP address. If it replies, you need to hunt down the device that has the IP address or come up with a new one for the new guest. If it does not reply, then a conflict isn't the issue.

=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Brent Schmidt Senior Network Engineer
Keep IT Simple[/color red] Novell Platinum Partner Microsoft Gold Partner
VMWare Enterprise Partner Citrix Gold Partner
 
Thx Brent, after further checking it's not related to ipaddr conflict, tested that after shutdown that vm instance, still cannot ping that ipaddr.

Also tested that assign another ipaddr to that vm, still cannot ping that ipaddr from the host itself, & other machines, however that vm can ping the rest of the machines, & can browse internet without any issues.

very very strange....

X-(
 
i've done the following tests:

1. on the vmware 1.0 host server, "arp -a" command can resolve the correct mac address of that problem vm guest

2. added a new lan card to the vm guest with a new, non-conflict ipaddr, host server still cannot ping this new assigned ipaddr of vm guest

3. removed old lan card to the vm guest, host server still cannot ping the new assigned ipaddr of vm guest on newly added lan card; again the vm guest can ping host server, can ping the rest of the network computers, can browse internet without problem

what else could be wrong? many thx!
 
just newly build one wxp guest system on the vmware 1.0.4 server, however this new build wxp also got the similar problem - it can ping machines in same subnet, it can ping & access internets, but just machines from same subnet also the vmware 1.0.4 server itself cannot ping this newly created wxp.

existing vm guest systems didn't have this issue at all, i've compared the network settings should be all right, any idea where did it go wrong?

many thx!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top