Virtual Machines are not able to fine a way to connect each other however PING is working fine

[amrinderbajwa]

Hi,

      I am using VMWare Workstation 8 and I have configured 3 VM as follows:

CentOS Server     192.168.30.129     (IP configured manually, working as DNS, DHCP, FTP server)

Windows XP         192.168.30.130     (IP assigned by CentOS via DHCP service but when performing DNS query, its not working)

CenOS Client       192.168.30.131     (IP configured manually)

All the machines are able to PING each other without any issue. The network type is "HostOnly". CentOS Server (192.168.30.129) is configured as main server with domain "bajwa.com", when I am performing DNS query from client VM, they are showing error like "No route to host" however all machines are able to ping each other.

Windows XP received an IP from CentOS server but when I perform DNS lookup using 'nslookup'  it showed me an error like can't find the default server:

Same thing is happening from CentOS client machine:

[root@bajwa3 /]# telnet 192.168.30.129 21

Trying 192.168.30.129...

telnet: connect to address 192.168.30.129: No route to host

[root@bajwa3 /]# telnet 192.168.30.129 53

Trying 192.168.30.129...

telnet: connect to address 192.168.30.129: No route to host

[root@bajwa3 /]# ping 192.168.30.129

PING 192.168.30.129 (192.168.30.129) 56(84) bytes of data.

64 bytes from 192.168.30.129: icmp_seq=1 ttl=64 time=1.37 ms

64 bytes from 192.168.30.129: icmp_seq=2 ttl=64 time=0.509 ms

^C

--- 192.168.30.129 ping statistics ---

2 packets transmitted, 2 received, 0% packet loss, time 1880ms

rtt min/avg/max/mdev = 0.509/0.940/1.372/0.432 ms

[root@bajwa3 /]# ftp 192.168.30.129

ftp: connect: No route to host

ftp> ls

Not connected.

ftp> bye

Could you please help me with this issue so that each machine will be able to connect each other without any issue?

All the Ports are open on CentOS Server and it is listening for above mentioned services like FTP, DNS, DHCP

[Scorpion99]

Hi,

why r u using "Host Only"??

Try to choose a VMnet and put the 3 machines in it.

You can find the VMnet options in Virtual network Editor in your start menu within the VMware Folder.

[amrinderbajwa]

HI,

      I am using "HostOnly' network because I can't use NAT. I want that when Windows XP will boot every time, it will get its IP from CentOS Server (192.168.30.129) and it is getting. I have changed the network to VMNet as per your advise but still showing the same errors. Here is my VMNet configuration:

I have disabled "Local DHCP Service" on VMNet2 so that Windows XP will gets its IP from CentOS not from VMWare DHCP Service

[Scorpion99]

Ok , make sure that all firewall are turned off , and try to create a shared folder on every machine so you can try to access between them.