Securing communications between Web browser and Microsoft Terminal Server |
 |
EXPERT RESPONSE FROM: Stephen Mencik
|
|
|
| > |
QUESTION POSED ON: 09 October 2001
How can I secure the direct communication between a Web browser on the Internet and a Microsoft Terminal Server that is behind a firewall?
After installing the Web based component for the Microsoft Advance Terminal Services on an IIS server that is behind a firewall, I enabled SSL on the server to secure the initial communications from any Web browser on the Internet. However, the subsequent communication from the Web brower is directly to the Terminal Server and is no longer secured by SSL. I would like my users to securely connect to the Terminal Server using any Web browser they can get access to while traveling.
|
|
| > |
|
My guess is that your firewall is blocking port 3389, which is for the
Remote Desktop Protocol. As for encryption, Terminal Services does
not actually use SSL. If you read the documentation available at Microsoft's
Web site,
it describes both the required port and a description of how it does
encryption.
|
|
|
|
|
|
|
|
Search and Browse the Expert Answer Center
Search and browse more than 25,000 question and
answer pairs from more than 250 TechTarget industry experts.
|
|
|
|
|
|
|
|
|
|
|
|
