Server 2003 Routing Issue...

[death2all]

ok i have new (3) new Server 2003 web servers (and numerous 2000 servers)at my offsite hostinbg facility. each one is configured w/ 2 NICs; 1st NIC is to the outside/Internet. 2nd NIC is to our internal network. when i first installed them it appeared everything went smoothly and they were connected to both networks. though when i tried to test the websites, they would not come up. if i disconnected the internal NIC the sites would come up, but not when both were connected. after much troubleshooting it turned out to be that 2003 (and XP) automatically set the metric values on the default gateways and the faster 1GBps internal network was being assigned a lower metric than the slower 100Mbps external network and not allowing me to view the sites. i then manually set the value to 10 on both NICs and gateways (my 2000 servers have theirs set to 1) and everything seemed to work. fast forward 2 weeks the problem came up again and it appeared windows when back to automatically setting the metric value. changed it to 10 and problem solved. problem comes back next day, so I set to 1 and its solved again. the problem is now intermittent and what worked for 2 weeks is now unreliable. i've looked up a bunch of articles on server 2003, automatic metric, order of adapters, dead gateway detection, why u shouldnt have more than 1 default gateway and most of them make sense, but what gets me is why it worked for 2 weeks and why our 2000 servers never had a problem w/ 2 default gateways. i'm basically looking for a definitive explanation and solution; should i NOT have 2 default gateways? and if so do i remove the default gateway on the internal network and add static routes in the routing table? i think ive included everything (except a route print), but if i havent let me know. thanx in advance

[death2all]

bump

was really hoping to get some help on this