Question : Multiple default gateways

My company has a DHCP server that assigns a class C address like this

10.32.2.x
subnet 255.255.255.0
gateway 10.32.2.1

The gateway (a router) is used to connect to some other subnets for extranet purpouses (not public ones, just private subnet like 111.222.1.0/24 or 111.222.2.0/24 and so on)

Now, I have connected a router/firewall in order to gain internet access from any pc of my LAN.

So the internet router (SERVER01) has 2 NICs:
Internet <--> ISP router <--> SERVER01 <--> LAN <--> Corporate Router <--> Corporate Subnets

Nic1   192.168.0.170   -> WAN interface (NAT)
Nic2   10.32.2.200     -> LAN interface

I configured some clients setting a fixed IP and changing their "default gateway" and DNS to the new one (10.32.2.200) and they can succesfully connect to any internet site.

Unfortunely they no more access to the other corporate subnets (e.g. 111.222.1.x) because the packets are routed through the ISP router.

My question is:
How can I configure my router/firewall SERVER01 in order to route the client IP packets to two different gateways?
Is it possibile? Do I have to set routing tables for every client in my LAN?

My router/firewall is Win2K pro with WinRoute firewall, the WAN interface is NATTED.
I configured 8 permanent ROUTES on this server to help choosing the correct router and locally it works perfectly, I can reach any ip (internet or corporate subnet).

Example:
ROUTE ADD 111.222.1.0 MASK 255.255.255.0 10.32.2.1 METRIC 1

Trying from the clients, it seems that SERVER01 routes their packet always to the ISP default gateway.


Thank you
Massimo

Answer : Multiple default gateways

I would probably write a logon script that performs the route add commands for the clients then.  Actually, if they are NT or above, you just have to add the routes once with the /p switch to make them persistent (stays after reboot).  However, if they are 98 or below, you have to add them everytime the box boots up.  I know in the past I've went as far as to make a batch file that sits locally on each computer that is run at startup to insert the routes.  The logon script just ensured that the batch file was there - if it wasn't it would copy it and insert the registry key to run it at startup.