This is actually a Windows question, but this forum has some of the most capable routing ppl on the web. I'm trying to set up my computer at work to communicate with my Linux box at home.

We have a NT Domain set up at work with a proxy connection to the internet. This connection doesn't allow FTP upload, nonstandard HTTP ports, or SSH. This effectively blocks my access to my home network, which has a lot of my tools hosted on it.

Solution came to mind in that we have a DSL connection. There are drops for it in my office building, so I just patched an unused Ethernet port into that switch, and bam, I can get to my home machine. But only when I disable the Domain connection.

So, as of right now, I have to disable the domain connection and change my browser connection settings every time I want to switch to the DSL connection. If I enable both, I can't get traffic to pass over the DSL NIC.

Normally, I would just rip the gateway out of the Domain NIC's network stack (I have static IPs for everything), and set the metric to the low setting for that connection. The problem with that is that the Domain network has several subnets attached to it (10.0.5.0 - 10.0.200.0). The DSL connection is going through a residential router, with a Nortel switch in my office. That IP range is 192.168.100.0 for our example.

What I want to do is have any traffic destined to any 10.xxx address to go out through the domain NIC (10.20.28.205) and through that gateway (10.20.28.254), and any other traffic to go out through the DSL connection (192.168.100.95/192.168.100.1). I'll set DNS up on this machine so that it uses the internal DNS on both adapters to prevent conflict.

PLEASE, any suggestions would be appreciated.

Have you tried setting:
default route to DSL connection
and 10.x.x.x to 10.20.28.205 ?

No. . . and I'm not sure how to do that in WinXP, any suggestions?

I could do it under Linux all day long, lol, but no idea where to start in Winblows. I'll check it out, but if anyone has any timesaving suggestions, it would be much appreciated.

Eureka! Magic is in the Route command, apparently. Guess this isn't too different than doing it in Linux, you just don't manually edit the routing table config file.

Ran again after testing with the -p flag set, and she works! Thanks Pronoy for getting me moving in the right direction.