Multi gateway terminal server

Ok,

I have a Terminal Server (2k3 SP1) in our head office that people connect
from multiple branch offices via the internet.

(There is no VPN or any other connectivity and never can be)

The capacity of the line that they use is almost full and I ordered another
connection. My problem is that I cant specify more than one gateway even
though each gateway is on a different subnet and different NIC.



WAN1: SN 255.255.255.0 GW 192.168.10.250 IP 192.168.10.5

WAN2: SN 255.255.255.248 GW 192.168.11.1 IP 192.168.11.2



I have configured Routing and Remote Access (I think) to route between two
private networks and it appears to work most of the time but occasionally
locks up on WAN2.

I have changed the metric for both NICs to manual and '1' but when I remove
the 2nd gateway from WAN2's NIC WAN2 doesn't work. (WAN1 must still work as
I have not been abused yet!) At this stage both NICs have a default gateway
set, which is incorrect from what I can read.



Does this indicate I have done something wrong or is there a better way to
do this type of connection?

Any ideas welcome!





Regards,

Murray

What type of connection did you order? I would have recommended a
bonded t1.

http://www.microsoft.com/technet/com...uy/cg0903.mspx

see "Configuring Multiple Gateways"

psg

Due to our overregulated government controlled ISP, the fastest upload link
I
can get is 512kb ($100 month) unless I want to pay >$1000 month for a 2mb
connection.

What I was hoping to do was to use another 512 link to connect to the same
server from the WAN (via port fwding). Trouble is I want everything that
comes in on X.X.11.1 to go straight back out the same path.

I understand how
"chrispsg" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> What type of connection did you order? I would have recommended a
> bonded t1.
>