I have a Win2k Server PC with 5 nics.

For my situation, the idea is to share a DSL connection in my building between several companies using Win2k Server's excellent NAT service.
For security reasons, you don't want to be on one huge LAN with unknown users while using windows file sharing.
So, the nics are each a separate ip range, (192.268.1.0/24, 192.168.2.0/24, etc) and aren't allowed to browse each other. IP Forwarding is off, and no DNS service is provided.
Any company on a nic by itself is hidden from the other nics. There are a couple of nics that have 2 or 3 companies sharing, so they use personal firewalls. There are at least 20 computers attached to this server, which is only a 450MHz k6-2.
This isn’t exactly what you're doing - but the experience of building this system gives me some insight.
Ideally, you need DHCP to listen on all internal nics and hand out ip addresses appropriate for the nic you're attached to. Plus, DHCP should hand out the IP address of the gateway, DNS Server, domain name, and other critical info that’s correct for each nic. The DHCP config file is easily edited to add the separate ranges.
Users of the 192.168.0.1 nic, would use192.168.0.1 as the gateway, DNS service, etc
Users of the 192.168.1.1 nic, would use192.168.1.1 as the gateway, DNS service, etc
Users of the 192.168.2.1 nic, would use192.168.2.1 as the gateway, DNS service, etc
You could enter all this by hand into the clients and forget DHCP, but that becomes a pain after while - even with only a few machines.
For your setup, you'd want a local DNS service running. That should provide browsing between the LANs. Shouldn’t need to enter routes by hand.
Looks like all the LANs listed in Local Networks are the ones that are allowed access for services like Squid, DNS, etc., so you'd have to add them all there.
I just got my first SME Server up yesterday, so I haven’t had time try to go beyond 2 nics. That’s why I read your post, in fact - looking for ready made answers to save time.
I've been looking for an alternative to Win2k Server because of its hefty cost. But after learning and setting up several distribs of Linux and BSD as firewalls, I never felt comfortable that they were actually secure. There is just too much I don’t know about setting up ipchains and all the rest. And I know a lot more about linux and firewalls than the average person.
That’s what drew me to try SME Server - a secure firewall, (seems to be so far) that’s low cost and configures itself. And it runs on a Pentium 1.
Anyway, hopes some of this helps...