Big questions on forwarding

[drcrunch]

Situ:
SUSE10 box functioning as a router hooked to a switch on eth1 that boots thin clients via dhcp. Clients are running Damn Small Linux, they boot just fine, run fine. SUSE box is connected to an XP box that runs its own network and this leads to the internet. Cannot reach the net from the thin clients.

congfig:
Thin clients: IP 192.168.0.101 through .126, their router address is 192.169.0.97, this is their gateway setting from what I understand.

SUSE:
Eth1 (inboard NIC) 192.168.0.97
Eth0 (outboard NIC) 192.168.0.5, this is the NIC to the switch that leasds to the XP box
IP forwarding is on, hosts are set to allow the clients. I have added the masquerading files from the tldp.org.

XP inboard NIC is Eth1 192.168.0.1
Status:
I can surf the net easily with the SUSE box.
I can ping the Eth1 and Eth0 on SUSE from the thin clients.
I cannot ping the 192.168.0.1, nor can I reach the net

I need a net, subnet guru.

Help

[drcrunch]

OK, this will update the sitch.
I have been trying to run the tldp.com howto's and was unsuccessful to this point.
On running the rc.firewall.tables start as an executable I was noting errors about files not existing "/usr/local/sbin/iptables: No such file or directory" I traced this to the link between rc.d and init.d and into the bin directory which contains the iptables (cd / (then) /find . -name iptables -print) I then edited the rc.firewall.tables to establish the location of the tables. Started the module again and viola, no errors. I have ping with the clients. My little thin clients can see the web, they can touch it.

I am so proud.