Question : Problem: Securing Remote Desktop Web Connection

Hello,

I am in the process of configuring Remote Desktop Web Connection for my company's network so to give our company and a software developer access to our server by other means then LogMeIn. So I have spent several hours reading how to configure it right, but I still have a few questions about some things I just couldn't find.

First, I'll tell you where I am. Our company hosts two website on a web server running Server 2003. So I installed remote desktop web connection for IIS on the web server, then made a virtual directory under the two websites for remote desktop web connection so the result would be an address from our website to access the RDP. Something along these lines:

http://www.companyname.com/rdp

I tested its functionality on the internal network and it worked perfectly. Next I wanted to test it from an external network and I then found out that I needed to open up port 3389. So I did.

Now my next goal is to make this secure. My first thought was to simply turn on SSL, but that did not work. It simply would not display the page when you go over to https. I have port 443 open since OWA is running, so forwarding should not be the problem. I was wondering if you could secure remote desktop web connect with SSL or other encryption? Also, if you can use SSL, how do I make it so it automatically redirects to https when you go to the link from http?

Step by step instructions would be a god send.

Thank you

Answer : Problem: Securing Remote Desktop Web Connection

Random Solutions  
 
programming4us programming4us