Do you have multiple NICs? If so, I don't think you even need to add a static route if your default gateway is 10.0.0.1 on the correct NIC. The route to 128.125.0.0/16 should be created automatically when you set up the 2nd NIC. (No default gateway needed on that NIC.)
Your name resolution could get wacky, however, if the DNS servers in one subnet don't know anything about the other, or don't have a route out to get public information. You'll have to play with it a bit, I would guess. -----Original Message----- From: Salvador Manzo [mailto:[email protected]] Sent: Tuesday, June 02, 2009 1:01 PM To: NT System Admin Issues Subject: Question re: ROUTE options All, Quick question showcasing why being self-taught isn't always the best possible option. I have a situation where I will need to have multiple IPs on a server, with most traffic going through a private VPN EXCEPT for a single publicly addressable subnet. 10.0.0.1 Private Gateway 10.0.x.x Range Public 128.125.n.y Normal Public Gateway 128.125.x.x Range In this situation, would ROUTE -p ADD 128.125.0.0 MASK 255.255.0.0 128.125.n.y METRIC 2 IF 2 put me in a place where all traffic NOT destined for the 128.125 IP range would go through the private gateway, but all traffic on the 128.125 range goes through the public gateway? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
