[unixfox]

I don't think you have a NETMASK problem, I think you have a routing problem.

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?

[1rudeboy]

For God's sake, man! Grab hold of yourself! Here's a photo of Olivia de Havilland.

[Drango]

getting a headache as i just flashed on my CCNA classes.

[sd-joe]

The mask allows an ip address to be broken up between a network address and a range of local addresses.

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.

[y6162]

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

[2 Kool 2 Be 4-Gotten]

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”

---

In windows or linux that command is called “route”.

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

[RightOnTheLeftCoast]

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? ...

[qwertyz]

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.

[verity]

"He's configed to be 192.168.0.1 locally."

Perhaps your router is a she and not a he. ;-)

[sd-joe]

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.

[B Knotts]

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"

route add -host 192.168.0.100 gw 192.168.0.70

That's for Linux, depending on your OS, YMMV.

[j_guru]

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.

[j_guru]

"sorta like VMWARE"
is this sorta like application VirtualBox?

[central_va]

Simple solution, set the netmask to 255.255.0.0 on all hosts in your network.

[USS Alaska]

I'm using my router, number 222.222.225.xyz to avoid this thread.

If I read it, I wouldn't understand it.

[Klutz Dohanger]

It appears your network is configured correctly, the problem lies between the Host Software (XP, correct?) and the virtual program.

A couple of things to try.

1. Assign the 192.168.0.100 address to the XP network adapter as a secondary IP address. You will have to set the adapter up with a static IP address first, using it's current address of 192.168.0.70. Make sure you put in the correct netmask 255.255.255.0 and gateway 192.168.0.1

Then under advanced, assign the secondary IP. Since it's in the same network, you won't have to add another netmask and gateway.

2. Some Virtual programs aren't real good at detecting host system hardware. They may put a virtual adapter in your hardware manager, but don't recognize the adapter. Check hardware manager to see if one is added, and is ok. (Not Red X'd or Yellow Exclamated). Also check your network connections to make sure if a virtual adapter is added there, it's enabled and has the proper address information.

3. Still other Virtual programs run a networking component under Windows services to handle the TCP/IP transfer from the host adapter to the virtual adapter. Check windows services to see if something has been added, and is not disabled, or has a problem running.

[Wingy]

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.