I had a similar setup(ish) and found I was getting
warnings when I had two networks using 192.168.1.x IPs
on one and 192.168.2.x on the other. This happened even
with the subnet mask for each as 255.255.255.0. It
shouldn't make the slightest bit of difference, but you
might want to change one of the networks to the
172.16.x.x (or the other private address range) range of
IPs and see if it makes any difference.
Also, I wouldn't set up a default route on the NT server
at all. Instead I'd just set the default route of each
client machine to be the relevant nic on the server.
That should be sufficient info for the two networks to
talk to eachother, I think... At least that's the way
I've got mine set up and it seems happy enough.
> > From: Fergal Moran
> > runs NT4 WKS and RH6.1 with the IP address
192.168.0.2. This is
> > via a crossover cable to a NT4 Server to a NIC with
the IP 192.168.0.1.
> > Another NIC on the NT Server box with the IP
192.168.1.1 is connected to
> > box running RH6 with the IP 192.168.1.2. The 0.1
NIC on the NT server is
> > set to use the 1.1 NIC as default gateway and vice
versa. IP forwarding
> > set up on both. 192.168.0.2 is set to use
192.168.0.1 as its gateway and
> > 192.168.1.2 is set to use 192.168.1.1.
> > Here's the problem.
> > from 192.168.0.2 I can ping 192.168.0.1
> > from 192.168.0.1 I can ping 192.168.0.2
> > from 192.168.0.1 I can ping 192.168.1.1
> > from 192.168.0.1 I can ping 192.168.1.2
> > but
> > from 192.168.0.2 I cannot ping 192.168.1.2 or vice
versa running either
> > or NT Wks
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!