not able to ping two Linux systems installed on VM
Hi,
In my office I have two systems and I installed VM on both the systems and then installed Linux 5.0 on them. I'm doing ifconfig to obtain IP address of both the Linux machines installed on VM, but when I try to ping each one of them they are not responding. How do I fix this? Thanks |
Quote:
You say "Linux 5.0"...WHAT linux? RedHat? SUSE? Debian? What kind of network configuration? Post the output of both of the ifconfig statements for ONLY the interfaces you're talking about, and the routing table (output of the "route" command). You may have interfaces down, no default route, different networks, etc. Are the linux boxes on two different VM hosts, or on the same one? Running what kind of VM software? |
What type of network interface did you setup? NAT? Bridged? etc. What are the IP addresses of the machines?
|
not able to ping two Linux systems installed on VM Reply to Thread
TB0ne,
This is what I have setup.System1 and System2 are two separate desktops on the same network System1: Windows XP IP:172.21.45.77 VM 6.5.1 On this VM I have installed RHEL 5.0 and named it station1. Below is the output of ifconfig and route: [root@station1 ~]#ifconfig eth0 Link encap:Ethernet HWaddr 00:0C:29:D2:B5:B0 inet addr:192.168.223.129 Bcast:192.168.223.255 Mask:255.255.255.0 inet6 addr:fe80::20c:29ff:fed2:b5b0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packtes:169 errors:0 dropped:0 overruns:0 frame:0 TX packets:148 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:20358 (19.8 KiB) TX bytes:26999 (18.6 KiB) Interrupt:67 Base address:0x2000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING NTU:16436 Metric:1 RX packets:3888 errors:0 dropped:0 overruns:0 frame:0 TX packets:3888 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:8070948 (7.6 MiB) TX bytes:8070948 (7.6 MiB) [root@station1 ~]#route kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.223.0 * 255.255.255.0 U 0 0 0 eth0 169.254.0.0 * 255.255.0.0 U 0 0 0 eth0 default 192.168.223.2 0.0.0.0 UG 0 0 0 eth0 System2: Windows XP IP:172.21.45.15 VM 6.5.1 On this VM I have installed RHEL 5.0 and named it Server1. Below is the output of ifconfig and route: [root@Server1 ~]#ifconfig eth0 Link encap:Ethernet HWaddr 00:0C:29:D2:B5:B0 inet addr:192.168.107.128 Bcast:192.168.107.255 Mask:255.255.255.0 inet6 addr:fe80::20c:29ff:fed2:b5b0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packtes:267 errors:0 dropped:0 overruns:0 frame:0 TX packets:259 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:27892 (27.2 KiB) TX bytes:26999 (26.3 KiB) Interrupt:67 Base address:0x2000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING NTU:16436 Metric:1 RX packets:12795 errors:0 dropped:0 overruns:0 frame:0 TX packets:12795 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:5442880 (5.1 MiB) TX bytes:26999 (5.1 MiB) [root@Server1 ~]#route kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.107.0 * 255.255.255.0 U 0 0 0 eth0 169.254.0.0 * 255.255.0.0 U 0 0 0 eth0 default 192.168.107.2 0.0.0.0 UG 0 0 0 eth0 |
Sounds like a routing issue. Assuming your guests are on a NAT-ed network, not host only, the hosts act as routers. You need to tell each host how to get to the VM networks on the other host. On System 1, try "route add 192.168.107.0 mask 255.255.255.0 172.21.45.15". And on System 2 try "route add 192.168.223.0 mask 255.255.255.0 172.21.45.77"
|
That or change your VM from NAT to Bridged and let them pull and IP from your router and be on the same network.
|
Also in VMware when you set up a NAT network connection, your Virtual Machine will get a 192.x.x.x network address. The host also gets a virtual address of 192.x.x.x. This allows the VM to communicate to the Host and other VM's on that host but I do not think it can communicate with other host or VMs on other host unless you set specific routes. I prefer to do Bridged connections to avoid having to do routes and such.
|
NAT networking shares the host IP. Ping doesn't work in this case.
|
All times are GMT -5. The time now is 05:02 AM. |