Hello, I have the following setup:

An ADSL Router (192.168.4.1) which plugs into my server (that has 2 network cards)

Server(eth0-connecting to the ADSL Router) = 192.168.4.2

Server(eth1-connecting to the windows XP PC) = 192.168.4.3

And the windows XP PC = 192.168.4.4

if I delete the entire routing table and add a default route

route add default gw 192.168.4.1 dev eth0 I get an error (I can't remember the error, the PC's
at work) however if I unplug the cable going from the PC to eth1, I can then successfully
add the default route, and I can ping the router, however when I reconnect the cable to the PC and Server... I can still ping the router (from the server) but I cannot ping the PC

if I try and add another route such as:

route add -net 192.168.4.0 netmask 255.255.255.0 gw 192.168.4.4 it wont let me add the rule


I have a feeling i am doing something really stupid here with the addressing scheme, any suggestions how a preffered way to do this? (keep it simple)


cheers,

Ele.

I'd split the lans to make more sense. Use 10.x.x.x for the xp and eth1

Happy to split the routes, silly question though

if I have eth0 on the 192.168.4.0 subnet
and eth1 on the 10.0.0.0 subnet

does linux have its own routing? (how can it route traffic from one subnet to the other)? (silly question I guess considering it lets me put in
static routes" but I was wondering if it also does dynamic routing?

also I tried something similar to your suggestion, I had a 192.168.4.0 subnet and a 192.168.8.0 subnet and it did not fix the issues??? - is there some kind of addressing conflict there? (I will try 10.x.x.x. on Monday)
any other suggestions would be appreciated