Server 10.3.9 - Three NIC cards - Route between Three subnets

Question

I have a panther server with three nic cards, each one connected to a different network.
xx.xx.1.x = private intranet used for storing video files- Has a DHCP server
xx.xx.2.x = company intranet used for internet access-
xx.xx.3.x = editors intranet
I have a NAT set up to forward network activity from the .3 to the .2
But the editors (.3) also need to access .1.
Is there a way to connect the .3 to the .1 network through the server?
Any help would be greatly appreciated.
Here's a picture to show what I'm trying to say.
http://www.kbdiondemand.org/client_files/routing.png

Answer 1

Here is my newest routing table. I cleared everything out and started over.
I have NAT enabled and it is working, but I removed the private address.
http://www.kbdiondemand.org/client_files/routing3.png
I'm starting to wonder if I need to create a divert rule in the firewall. NAT has a firewall divert rule to send traffic to the NAT service.
So far, I haven't gotten the syntaxt correct for creating the divert rule. The error message is the port is incorrect?
I haven't found the information on any of the panther server books out there. They shy away from using the server as a firewall or a router.
excerpt from Essential Mac OS X Panther Server Administration
Of all the things that a packet filter can do, Apple seems to have some pretty specific things in mind for the Firewall service in Mac OS X Server. Panther Server's Firewall service is targeted at protecting the server on which it is running. Configuring a firewall for this purpose is very different from configuring a firewall designed to sit at the border between a network and the Internet. Mac OS X Server is simply not well-suited for the tasks normally performed by a dedicated firewall.
For example, Mac OS X Server needs to be rebooted for things like software updates, and does a fairly poor job of routing packets during the reboot. Surely you could configure Mac OS X Server as a router and then never touch it so that it wouldn't have to be rebooted, but that means no software updates. Just because Mac OS X Server can act as a router; that does not mean it's the most cost-effective or functional solution. Trying to shoehorn Apple's Firewall service into performing duties that it wasn't intended to provide is generally not a good idea.
Apple also includes a Network Address Translation (NAT) service that works in conjunction with the firewall. This service could be used to provide Internet access to a workgroup by allowing the workstations to share the server's IP address. While the NAT service does work, better results may be found with the average $40 NAT router. The bottom line is that it's a very good idea to use dedicated network hardware, and not a personal computer, to perform critical network functions like routing. This reduces network downtime due to computer maintenance such as software updates.
I will focus on using Apple's Firewall service for protection of services running on our server, and not to do routing or NAT for other computers.