1 Server, 2 NICs, 2 Networks - How to make this work?

Windows 2003 Server

NIC One:

NIC one is connected to the "internet switch", which is connected to the firewall, which is connected to the router out to the internet.

NIC Two:

NIC Two is connected to the "LAN switch" which connects several different workstations.

As I am sure you are all aware, when setting the two different gateways, I get a nice warning message about redundant networks and how if it's two seperate networks this won't work.

NAT-ing for the servers public IP is not an option.

Keeping one IP public and one IP private, how can i make this work on W2K3?

Crazy thing is, I have 8 W2K servers attached to this same network, with the IP stacks similar as stated above, and seems to work fine and has for 2 years.  The public IP's work and the services provided by them work fine and are accessable by the public, and I can still access shares on the LAN and whatnot.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

I'm curious why you need to have a NIC in your servers for public IP access period?  Why aren't the all just using a LAN IP nic and then routing out through the firewall for their internet access?  And why isn't the firewall "publishing" any web servers, mail servers, etc so that your internal servers aren't actually exposed to the internet at all?
Keith AlabasterEnterprise ArchitectCommented:
Your issue sounds like it is in the question.

NIC2 should not have a gateway; you are confusing the heck out of your server. You should only ever have one default gateway assigned. as the name suggets, it is the default nic to send data out of if it does not have a known route. Giving it two defaults is not a workable option.

Nic1 is fine
Set the dhcp scope on nic2 only (in its settings you tell it to use nic2 only to assign addresses on).
Set the 003 (router option) for the dhcp scope to point all work stations to the NIC2 address of the server.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Keith AlabasterEnterprise ArchitectCommented:
PS, if you have other roues/subnets that the internal network needs to get to, still remove the nic2 gateway then use the route command from the dos cmd prompt

for example,
route - p add mask
Keith AlabasterEnterprise ArchitectCommented:
Thanks :)
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.