Answered by:
RemoteApp external access not using correct port

Question
-
Hi,
We have a situation where we are setting up RDS for externally outsourced staff and as such they are only connecting to selected apps which will allow through RDS Web.
Currently 443 is the port used for our mail server web access and cant be used for RDS. As a result I went through to the Transport Settings configuration in the RD Gateway Properties and updated the HTTPS Port from 443 to 4321.
I then proceeded to open and forward to correct ports on all the firewalls. Internally this works perfectly (also tested via VPN), but when trying to access externally it didn't want to work. I kept getting an error saying the Remote Desktop Gateway was unavailable.
So using the trusty fiddler tool I checked it out to see what connections where going on. Turns out that when remote app session was still trying to establish a connection using 443 and not the port specified.
I was under the impression that for external connections the gateway is used as a middle-man to connect to the internal network and connects over the HTTPS port specified and the UDP port.
Is there anything I'm missing here? Please help.
Thanks
Phill
Friday, December 27, 2013 2:15 AM
Answers
-
Hi Phill,
Based on my understanding you are facing accessing issue with RemoteApp from external network. Here want some information from your side.
Did you find any Event ID during this issue?
Does this issue occurs with all users? Have you define RD RAP and RD CAP?
Did you check all certificate are properly placed?
Which version of RDP client you are using on your user system? The changing port will only listen gateway connection with new RDP client version so suggest you to upgrade to RDP client v 8.0 or 8.1. You can go through “Running RD Gateway on a different port then 443 (Windows Server 8)” for details.
When you create the RD RAP, add the user groups that you defined in the RD CAP. Also, create a new RD Gateway-managed computer group that contains both the NetBIOS names and the fully qualified domain names (FQDNs) of the RD Session Host servers or the RD Session Host server farm that hosts the RemoteApp programs. In addition, you can try to uncheck the “Bypass RD Gateway server for local addresses” option under RD Gateway Setting. Please refer below article for detail information.
Checklist: Make RemoteApp Programs Available from the Internet
http://technet.microsoft.com/en-us/library/cc772415.aspx
Hope it helps!
Regards.- Marked as answer by Dharmesh SMicrosoft employee Monday, January 6, 2014 3:43 AM
Friday, December 27, 2013 8:00 AM
All replies
-
Hi Phill,
Based on my understanding you are facing accessing issue with RemoteApp from external network. Here want some information from your side.
Did you find any Event ID during this issue?
Does this issue occurs with all users? Have you define RD RAP and RD CAP?
Did you check all certificate are properly placed?
Which version of RDP client you are using on your user system? The changing port will only listen gateway connection with new RDP client version so suggest you to upgrade to RDP client v 8.0 or 8.1. You can go through “Running RD Gateway on a different port then 443 (Windows Server 8)” for details.
When you create the RD RAP, add the user groups that you defined in the RD CAP. Also, create a new RD Gateway-managed computer group that contains both the NetBIOS names and the fully qualified domain names (FQDNs) of the RD Session Host servers or the RD Session Host server farm that hosts the RemoteApp programs. In addition, you can try to uncheck the “Bypass RD Gateway server for local addresses” option under RD Gateway Setting. Please refer below article for detail information.
Checklist: Make RemoteApp Programs Available from the Internet
http://technet.microsoft.com/en-us/library/cc772415.aspx
Hope it helps!
Regards.- Marked as answer by Dharmesh SMicrosoft employee Monday, January 6, 2014 3:43 AM
Friday, December 27, 2013 8:00 AM -
Hi,
How is everything going? Could you please tell us the present situation? If you need any further assistance, please let us know.
Thanks.Monday, December 30, 2013 2:31 AM -
Hi,
Here just writing to ensure that the problem has been completely resolved. If there is anything I can do to help on this issue, please feel free to let me know.
Regards.Friday, January 3, 2014 3:33 AM