2 isp's Terminal Services access

[Elliott]

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

 

[Lanwench [MVP - Exchange]]

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, Elliott - this is a group for Windows XP networking issues (not the best
group for your question....)

That said, your ability to get *into* a TS box from the Internet has nothing
to do with a default gateway set on the server (or any host machine) itself.
The default gateway controls that server's *outbound* connectivity to the
Internet. So, something else is clearly wrong.
Your two routers don't have to know anything about each other. If you have
router1 and router2, and each is set up to forward TCP 3389 fromWAN to
192.168.50.5, you shouldn't have any problems getting to that box from the
Internet on either connection's public IP (or FQDN established for same).
You might try posting in m.p.windows.server.networking for more specific
help, and provide the exact setup & errors you get....I don't think this
really has anything to do with Terminal Services itself.

Also (veering a bit off topic), I'm not sure what your specific reason is
for having two Internet connections/circuits, but you would probably be
better off getting a router or firewall with two WAN interfaces, that can do
load balancing/failover automatically....check out Sonicwalls running the
EnhancedOS or some Cisco kit.