Sure. You may have to play with the "route" command to make it work. What
you want is to route only the traffic that _has_ to go over dialup that
way, and make the DSL connection your default route.

Take a look at "TCP/IP settings" on the "Server" tab. There's a checkbox
that says "Use default gateway on remote network". You'll want to uncheck
this, but not just yet -- first, you need to find out what routes you
actually need.

Dial-up, and then go to the command line and do "route print". The output
will look something like this:

C:\>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 50 56 b6 01 0c ...... AMD PCNET Family Ethernet Adapter
0x3 ...00 01 d0 4b 52 80 ...... NdisWan Adapter
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0   152.125.216.69  152.125.216.69       1
          0.0.0.0          0.0.0.0      192.168.1.1    192.168.1.14       2
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
      152.125.0.0      255.255.0.0   152.125.216.69  152.125.216.69       1
   152.125.216.69  255.255.255.255        127.0.0.1       127.0.0.1       1
      192.168.1.0    255.255.255.0     192.168.1.14    192.168.1.14       2
     192.168.1.14  255.255.255.255        127.0.0.1       127.0.0.1       1
    192.168.1.255  255.255.255.255     192.168.1.14    192.168.1.14       1
        224.0.0.0        224.0.0.0   152.125.216.69  152.125.216.69       1
        224.0.0.0        224.0.0.0     192.168.1.14    192.168.1.14       1
  255.255.255.255  255.255.255.255     192.168.1.14    192.168.1.14       1
===========================================================================

Here, "0.0.0.0" means the default route. 192.168.1.1 is the gateway for DSL,
and 192.168.1.14 is the machine's IP. (These are actually addresses on my
LAN, but it works the same way if you have a direct connection to DSL from
the NT computer.) The other default route line was put in by the dialup
adapter; it effectively displaces the old default route.

If we remove both default routes:

 route delete 0.0.0.0

and then restore the DSL default route:

 route add 0.0.0.0 mask 0.0.0.0 192.168.1.1

normal DSL traffic is restored, while traffic destined for the 152.125.xx.xx
net continues to be routed over dialup. Unchecking the "Use remote gateway"
box before dialing up has the same effect.

But, is this enough? In my case, no -- as I can see by this excerpt from the
output of "ipconfig /all" (winipcfg will work as well):

 Primary WINS Server . . . . : 152.124.64.18
 Secondary WINS Server . . . : 152.124.173.19

Seeing this, I know that I at least have to route 152.124.xx.xx, as well.
Following the model of the existing route for 152.125.xx.xx:

 route add 152.124.0.0 mask 255.255.0.0 152.125.216.69

This seems to be enough for my case, but it's a bit of trial and error. You
should find out the IP's of any of the machines on the dialup LAN that you
know you have to use, and figure out which nets they're in. If you're lucky,
no additional route statements will be needed.

HOWEVER, the fact that you're unable to access your Exchange server after
dialup is cause for concern. Since the dialup has set the default route, it
shouldn't be a routing issue. You may have another problem to work on there.

It seems that it does, in NT 4. It doesn't happen in Win 98, oddly enough.
This happens whether or not you uncheck "Use default gateway", but you could
try overriding it with the "Specify name server addresses" option from the
same page.

--
William McBrine <wmcbr...@telocity.com>