Not able to ping between VMS in Vmware 9.2

Hi

I have  installed a test lab using VMware workstation 9.2 and I am not able to ping the Windows 2008 server from the XP and windows 7 Client and vice versa.

On the Home -Virtual network editor , I clicked add network and choose the Host only and said connect a host virtual adapter to this network. I did this on both server and the client.
I have not chosen use local DHCP service to distribute IP address to VMs, because I have the window DHCP server configured

and

On the virtual machine settings and on the network   adapter I have  chosen Custom: specific network and selected the right adapter that I created from the drop down list.

I configured static IP on both Windows 2008 server and XP client and when I ping I get request time out.

I created a rule on the windows 2008 FW to allow ICMP and also I disable the FW on both the server and the client and still I am not able to ping.

Please suggest and tutorial will be helpful.

Thanks
lianne143Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JohnBusiness Consultant (Owner)Commented:
Host only isolates machines. Try using NAT and if you want specific NAT networks, set these up in the Network Editor.

I had VMware Workstation 9 and now I have V10. But machines on my computer are all using NAT and they can all ping each other and talk to each other this way.

Host only does not allow inter-machine communication so far as I know.

... Thinkpads_User
0
lianne143Author Commented:
I went to the virtual network editor and choose the VM3 Host-only and under VMnet information I choose the NAT(shared host's IP addresses with VMs) and I get an error Cannot change network to NAT: Only one network can be set to NAT.

There is already a default VMnet8 NAT listed in the Virtual network Editor. do I need to delete the default.

Thanks
0
JohnBusiness Consultant (Owner)Commented:
I think you need to use the default NAT connection because NAT is built into VMware. I think you can adjust the properties.  

I will look further at NAT when I get back to a computer.
... Thinkpads_User
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

JohnBusiness Consultant (Owner)Commented:
Back at my computer, Bridged and NAT networking are the built-in VMware networks. Both will allow inter-machine communication. NAT provides its own built-in DHCP.

Custom networks are Host only. Host only allows a machine to talk to the host computer, but (so far as I know) do not allow inter-machine communications.

I would not remove VMware built-in networks as you risk having to uninstall and reinstall VMware itself.

So for you to connect virtual machines (ping the other machine) you need to use NAT networking for each machine (you could of course use Bridged networking if you are using a desktop computer with external DHCP like a router).

Assuming you use NAT, you want the host firewall to allow the NAT range (which is normally a subnet of 192.168.x.y that is not your host subnet).

Once the machines are running, you should be able to ping back and forth and connect by IP Address (NET USE Z: \\IPofOtherMachine\Foldename).

.... Thinkpads_User
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Nagendra Pratap SinghDesktop Applications SpecialistCommented:
It seems that you have firewalls active on the VMs.
0
JohnBusiness Consultant (Owner)Commented:
@lianne143 - Thanks and I was happy to help. Firewalls will affect NAT as I had suggested above.

... Thinkpads_User
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.