Dual WAN on XP Peer-To-Peer

[Mark Flynn]

I have a Peer-to-Peer XP pro network. The router is also the DHCP server,
and all Workgroup PC's are set to DHCP. This network connects to the WAN
via a T-1 line that only has 128 kb of bandwidth.
QUESTION: how can I include a DSL connection on this network? The idea is
that the T-1 would service the Workgroup's Company "server farm" on the
WAN. And the DSL would service the Internet (www) for the Workgroup.
Any ideas?
Thanks, Mark Flynn

 

[Doug Sherman [MVP]]

Clients should have a default gateway pointing to the DSL router/interface
and a static route(s) to the IP network for the server farm. If possible,
you should configure the static routes on the DSL router. If this is not
possible, you can do it on the client machines.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

 

[Mark Flynn]

Hi Doug, thanks for our reply.
I believe the Company's T-1 router requires a specific IP address. Let's
say that the T-1 router's address ends in .1 Can I address the DSL
router's IP address ending with .2, and use the DSL's router address as the
Default gateway on each client PC?
So, if I understand correctly:
A) I can disable DHCP on the router.
B) Then assign static IP addresses to the clients
C) Let the client PC's know that the Default gateway is the DSL router's IP
address.

And, hopefully, Company T-1 traffic will look to the T-1 router, and
Internet traffic will look to the DSL router?
Thanks, Mark Flynn

 

[Doug Sherman [MVP]]

OK, this is probably best explained with an example. Let's say:

1. The internal interface for the T1 router is 192.168.0.1; and the
internal DSL router interface is 192.168.0.2; and the external IP for the
server farm is 123.123.123.123; and you have an internal workstation IP
address 192.168.0.3.

2. On the workstation:

a. set the default gateway to 192.168.0.2 - this means that any traffic
destined for an IP which is not on the 192.168.0.0 network will go to the
DSL router UNLESS there is a static route to the destination IP.

b. Configure a static route to 123.123.123.123. On the workstation, open a
command prompt and enter this command:

route add 123.123.123.123 mask 255.255.255.255 192.168.0.1

if instead of a specific IP, you wanted to route to a whole
network you would use the 'real' subnet mask, eg:

route add 123.123.123.0 mask 255.255.255.0 192.168.0.1

c. The result is that all non-local IP traffic will use the DSL gateway
EXCEPT for traffic destined for the 123 address (or network) which will
instead be sent to the T1 router.

You can configure multiple static routes if there are multiple incompatable
addresses or networks you want to reach through the T1.

To make a static route permanent, use "route -p add"

If the DSL router supports static routes, you need only configure the static
route on the DSL router (you will have to consult the router documentation
to determine how to do this) - then all clients using the DSL router as a
default gateway will also use the static route. If the DSL router does not
support static route entries, you will have to configure the static route on
each client machine per the above.

Doug Sherman
MCSE Win2k,NT4.0, MCSA, MCP+I, MVP

 

[Mark Flynn]

Hi Doug:
Thank you for clearly showing me what to do. I greatly appreciate your time
and expertise.
Best regards, Mark Flynn