Your LOCAL network should have a netmask of 255.255.255.0 Let me ask you, do you have more than 1 router on the network or just one, period?
getting a headache as i just flashed on my CCNA classes.
The usual mask used is 255.255.255.0, where for the 192.168.0.x address range the 192.168.0 is the network address and the .x (what ever number x represents) is the device address.
A mask of 255.255.0.0 would be a network address of 192.168 with device addresses of y.x.
A mask of 255.255.255.248 would give a very restricted device address range of only a couple of usable addresses.
Clear the arpa cache on the boxes. arp -a
Try adding a default route on the other boxes to reach the router. Check the rote man page for syntax
These would work under unix:
Route add default 192.168.0.1 netmask 255.255.0.0 (default route)
or
Route add host netmask 255.255.0.0 192.168.0.1 1 (static route, one is a hop)
or
Route add netmask 255.255.0.0 net 192.168.0.0
So I’m trying to find the right (if there even is one) ROUTE command that I can enter on Box X that tells him “Listen: if you get a request for 192.168.0.100, the route for it is through 192.168.0.70”
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/route.mspx?mfr=true
http://linux.about.com/od/commands/l/blcmdl8_route.htm
As I understand it: your VM is able to ping its host computer, and vice versa, but the outside world can’t see the VM, and vice-versa.
Sounds like you have host-only networking selected in VMWare (or whatever you’re using). Change to Bridged or NAT, and you should see the rest of your network from within the VM.
(And why not use DHCP? So much more flexible. Devices such as printers which require a static address can still have their static address.)
What virtual-machine package are you using? Not VMWare, apparently. Parallels? VirtualBox? Xen? ...
First, all devices must be on the same subnet to see each other. It sounds like you’re having problems setting the subnet (which determines the address range).
Second, switches and routers must be properly configured.
Third, make sure the physical cabling isn’t screwed up (for example, using or not using a crossover cable).
This may sound like gibberish, so maybe we need to walk you through it.
Perhaps your router is a she and not a he. ;-)
Routing can only be between networks. You can not ROUTE within a network. See my earlier reply. The mask defines the networks.
What is the mask on your main router? If it is 255.255.255.0, you can not route anywhere within that range. In other words you can not route between 192.168.0.70 and 192.168.0.100.
route add -host 192.168.0.100 gw 192.168.0.70
That's for Linux, depending on your OS, YMMV.
Sounds more like a firewall running on the VMWare host machine. also could be that the host needs to bridge the virtual network adapter to the network.
Simple solution, set the netmask to 255.255.0.0 on all hosts in your network.
If I read it, I wouldn't understand it.
When confronted with a problem of this type, I simply call the 1-800 number on the box and let the Philipino walk me through it. It’s their job, so they’re good at it.