RE: Access to Terminal Servers
Cnances are your Terminal Servers are behind a NAT Firewall, and you have
port 3389 open to the first terminal server. To do this the way I would not
recommend, you'd need a second Public IP Address that you can have directed
to port 3389 on the second server. Alternatively you could change the
listening port for the second server to 3390, or some other port, and
continue to use one IP address.
That was what I would not recommend. What I would recommend is that you
access the terminal servers via SSL VPN or a SSL Reverse Proxy. This is
typically done by putting the server/appliance in the DMZ, which
intermediates the traffic from the users on the public Internet, so you only
have to open port 443 from the public Internet to the device in the DMZ, then
open port 3389 from the DMZ to the Terminal Servers.
Products that offer this functionality are Provision Networks Virtual Access
Suite Enterprise Edition, Citrix Presentation Server Advanced or Enterprise
Edition, 2X LoadBalancer, HobSoft JWT Enterprise and Ericom PowerTerm
Webconnect.
To wrap you head around what I'm describing, here is a Visio Diagram of our
solution that offers this functionality:
http://www.sessioncomputing.com/pdf/VAS_Architecture.pdf
There are plenty of SSL VPN Devices from which you can choose, one of which
is AEP Networks NSP.
--
Patrick C. Rouse
Microsoft MVP - Terminal Server
SE, West Coast USA & Canada
Quest Software, Provision Networks Division
Virtual Client Solutions
http://www.provisionnetworks.com
"Candace Sparks" wrote:
> Just added an additional terminal server on the network. Do not have
> experience with terminal server. Now, users are connecting remotely to the
> 1st terminal server. How can they connect to the 2nd terminal server? I
> have tried to connect remotely; I only know to type the Public IP address,
> and I connect to the 1st terminal server. I do not see an option to connect
> to a different server?
>
> Thank you for your help in advance!
>
> Candace Sparks
>
>
>