wlandymore
asked on
can't ping VM machine from another network...
I have a 2003 machine setup with an adapter (192.168.2.153)
Then it's running Linux on it which is using the bridged network and an address of (192.168.2.111)
At first I couldn't ping anything on the 2.0 network, but when I opened the network settings in the VM and put in a route for:
192.168.2.0
255.255.255.0
192.168.2.2 (gateway for that network)
I can now reach it from everything on the 2.0 network. However, I can't get things on the 1.0 network to talk to it. I tried making another route for this:
192.168.1.0
255.255.255.0
192.168.1.245 (router which spans 1.0 and 2.0 network)
but it still doesn't work. I've never had to setup routes to get things talking to the VM before so I'm not sure why it's requiring this now. Does anyone know if something is out of line with my setup?
Then it's running Linux on it which is using the bridged network and an address of (192.168.2.111)
At first I couldn't ping anything on the 2.0 network, but when I opened the network settings in the VM and put in a route for:
192.168.2.0
255.255.255.0
192.168.2.2 (gateway for that network)
I can now reach it from everything on the 2.0 network. However, I can't get things on the 1.0 network to talk to it. I tried making another route for this:
192.168.1.0
255.255.255.0
192.168.1.245 (router which spans 1.0 and 2.0 network)
but it still doesn't work. I've never had to setup routes to get things talking to the VM before so I'm not sure why it's requiring this now. Does anyone know if something is out of line with my setup?
RDAdams
Your netmask will not allow it. 255.255.255.0 means all first three quads need to be exact.
What does your routing table look like?
ASKER
If that's the case about the subnet mask, why did I have to add a route to the 2.0 network just to make other devices visable?
When I had the VM running on the 1.0 network there was no need for a route to be entered. It just had a different address from the host computer and both addresses (host or VM) were pingable.
When I had the VM running on the 1.0 network there was no need for a route to be entered. It just had a different address from the host computer and both addresses (host or VM) were pingable.
ASKER
plus, you can use something like 'route add' to setup a route to another address on another network (both using masks of 255.255.255.0) and you will be able to reach them and ping them. Why should that not work for a VM?
Are you able to ping your router at 192.168.1.245 ?
From the 1.x network of course.
ASKER
yes, that's coming through
So the route from your router to the 2.0 is not working. What type of router is it?
ASKER
when I do a ping of any device from the VM linux I get 'destination network unreachable' right away. However, I have a route on the host computer pointing to the 1.x network which is also present inside the VM, and I can ping anything on the 1.x network from the host machine, it's just from the VM or to the VM that's unaccessable from the 1.x network.
Is this VM ware that you are running?
ASKER
yes
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.