2 isp access to Windows 2003 terminal server

I have a network with a Win 2003 server running Terminal Services Lan
IP 192.168.50.5).

Access to Internet is through two routers, one (Lan IP
192.168.50.100)
from T1 access and the other (Lan IP 192.168.50.98) by cable modem.


Both routers have NAT and forward port 3389 to the Win Terminal
Server
(192.168.50.5)


Access only works from the T1 router ( because the default gateway on
the server points to 192.168.50.100). I there any way to achieve
access to the Terminal Server from both internet gateways?


I suspect I will need to forward traffic from 192.168.50.98 to
192.168.50.100 on the LAN but my router won't forward specific ports
from LAN to LAN.


Any suggestions or help?


thanks


Elliott

Elliott <(E-Mail Removed)> wrote:
> I have a network with a Win 2003 server running Terminal Services Lan
> IP 192.168.50.5).
>
> Access to Internet is through two routers, one (Lan IP
> 192.168.50.100)
> from T1 access and the other (Lan IP 192.168.50.98) by cable modem.
>
>
> Both routers have NAT and forward port 3389 to the Win Terminal
> Server
> (192.168.50.5)
>
>
> Access only works from the T1 router ( because the default gateway on
> the server points to 192.168.50.100). I there any way to achieve
> access to the Terminal Server from both internet gateways?
>
>
> I suspect I will need to forward traffic from 192.168.50.98 to
> 192.168.50.100 on the LAN but my router won't forward specific ports
> from LAN to LAN.
>
>
> Any suggestions or help?
>
>
> thanks
>
>
> Elliott

Hi - I replied elsewhere. Please don't multipost - if you need to post to
multiple groups, it's best to crosspost instead, by posting a single message
to a handful of relevant groups (separate the NG names with commas) so that
everyone can follow the thread. Thanks :-)

See http://www.blakjak.demon.co.uk/mul_crss.htm

"Lanwench [MVP - Exchange]"
<(E-Mail Removed) ahoo.com> wrote in
news:(E-Mail Removed):

> http://www.blakjak.demon.co.uk/mul_crss.htm

Couldn't agree more, because I would really like to know the solution... as
I have the same problem. I DO however have both routers and NIC on their
own submasks.

Route 1 - WAN, router (10.10.10.1), NIC (10.10.10.4/255.255.255.0)
Route 2 - WAN, router (10.10.99.1), NIC (10.10.99.4/255.255.255.0)

Hugh O'Donnell