if I understand correctly, the clients don't need to make any changes. You can add another NIC on the DC but that may cause some issues (it is not recommended to run DC on a multihomed computer). I think the DC with one NIC should work but you need to point default gateway to the T1 line and all internet traffics go to T1 line while still be able to access the LAN.
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"robert.waters" <(E-Mail Removed)> wrote in message news:(E-Mail Removed) ups.com...
Hello,
I have a windows 2003 domain containing a terminal server that is used
by both internal and external users to access an important application.
Our WAN link is currently a slow-ish adsl modem. I have been asked to
get a dedicated link (T1) so that external users will have a better
experience accessing the terminal server, while keeping the existing
adsl connection for internal users' internet and email access.
How would I set this up? Our network is simple, basically a NAT router
is upstream of a Dell managed switch, to which all of our servers and
wired internal clients connect to; the NAT router also does wireless,
which allows our wireless internal clients to connect to local
resources as well as the internet. The NAT router is connected to the
adsl modem.
Can I just connect the T1 to the second NIC of my terminal server, and
set it up so that it routes internal traffic to one NIC and external to
the other?
I truly don't know where to look first (on the 'net); even some
recommended links would be great.
Thank you,
Robert