Hello Microsoft Professionals,
I am having an issue with external access to my RDP service server. I have set this up to be configured to work internally and externally. Internally is working fine, I have set up the requirements for external access as well and am able to navigate to the public FQDN via an internet browser. I am even able to get as as far as logging in with private credentials, however when I click on the remote desktop tab and specify a computer that I have added to the necessary policies I then get prompted for credentials. Not only do I get prompted for credentials but the logon screen is looking for credentials related to the RDgateway server instead of the remote computer. So I oblige by providing admin credentials and every time I get the error: "RDgateway server is temporarily unavailable." please see picture: http://i2.photobucket.com/albums/y25/BooBoniK/RDgatewayErrors_zps1a77c7b4.png
I was under the impression that once I complete this connection using port 443 all of the services also traverse port 443. I have ran the best practices analyzer with all compliant results except a warning regarding the self signed cert (which I am not to concerned about). I am in need of some assistance, I have been navigating forums and looking for answers for this problem now for over two weeks. I have tried every suggestion there is out there with no success. I have even flattened and rebuilt this server twice now. I am able to provide more screenshots and details if needed.
I thank you in advanced for any insight.
- Edited by Eddie.Brown1986 Friday, July 26, 2013 11:06 PM
How many servers / vm's do you use for your deployment? If you have done the quick start deployment and spent way too much time with .pfx headaches - then I am willing to share my experience with regard to 2012 RDS / RemoteAPP deployment. (perhaps you can email me)
Firstly, please refer to this article to verify the configurations.
Deploying Remote Desktop Gateway Step-by-Step Guide
I followed this document and every other regarding RDP Services. That document highlights what needs to be done for internal access and assumes that you have a perfect environment with unlimited resources. Which unfortunately I do not. it says nothing about adding an external DNS entry to your ISP or forwarding port 443 on your router.
If you believe that I would come to the TechNet forums without reading every one of Microsoft's "Step-by-Step Guides" referencing the set up of RDP services, then you are poorly mistaken sir.
Still looking for an answer. I have had a colleague suggest I need a trusted certificate in order for the remote desktop to work from within the portal. I am currently waiting for approval on a 30day free trial.
I will update once the approval comes through.