Combination of things.

Firstly, 192.10.200.0/24 is, AFAIK, a registered Internet address. You should change that subnet to 192.168.200.0/24.

Secondly, the box on both LANs should automatically route between the two LANs. There should be no need to add extra routing to any box except those that need to connect to something on LAN2. The printer might be an exception there, but I'm not sure.

Thirdly, for NBT to route, you need a WINS server. Samba can do this automatically for you, you just have to flip the switch, so to speak. You also have to tell the PCs on LAN2 that the gateway machine is also the WINS server.

Finally, if you still need to fiddle with the routing in Windows 2000, type route on a command line for some assistance. Windows' routing is not quite as simple as routing in Linux, but it's not impossible. It basically does daft things like route through the loopback or some strange thing, so ignore that and it makes sense.

Wade.

We used to use that id back at IBM for internal lans back in the 1980s. Thought it was still a no public addr.

Re win2k, reason I posted here was after bashing my head on a wall trying to get route to make sense on the win2k machines.

Perhaps Greg's advice re using the Linux box to route is the best. Linux routing is easier to get working.

The Buffalo AirStation wi-fi lan is a nice little box to use - is made by MELCO (Mitsubishi Electric Coy) an guessing ti runs Linux (if not then it must be bsd Unix). Is configured thru web pages. Comes out of the box with a preset ip but one can change just about ecery aspect of its routing & filtering & dhcp allocations etc:. It will support up to 254 devices so the model I have that also has 4 utp ports can be cascaded to quite a size.

Anyway, thanks both of you for the pointers

Cheers

Doug

Welcome to IWETHEY!