RemoteApp not accessible from outside of my local system
RemoteApp is becoming the "bane of my existence". My setup has been working great since my last problem (SonicWall issue) but that's only been for a little over 2 months! I can't think of anything I've changed or anything that's happened to my network, so, as usual, I don't have a clue as to why this, all of a sudden (and, of course, at an extremely crucial time since I'm using it to convince a potential new customer to purchase my software system) has stopped working, but it has. Internally, it works just fine, which rules out some possibilities but does nothing to help my current situation. I'm running RemoteApp (RDS) on a Windows 2008 R2 Server and I'm going to embed as much information as I can think of regarding my current setup (which has NOT changed) and hope that someone can help me. Let me start with the error message received by anyone attempting to access from outside my network:
Being a programmer with a "passing knowledge" of server setups, I have NO idea what a forward proxy configuration means. The following screens will display my basic setup which uses a Gateway Server AND a Remote Host Session server (SSL certificates exist for both. The RemoteApp Manger screen:
The Remote Desktop Connection Manager:
The RemoteApp Deployment Settings for the RD Gateway:
The RemoteApp Deployment Settings for the RD Host Session Server:
I have more screen shots if anyone with the RemoteApp expertise that I don't have can help and needs further information about my setup. One last thing is that I am (and always have been) substituting port 4011 for the standard 3389. Any help would be greatly appreciated.
RemoteApp-Error-External--2..jpg
Being a programmer with a "passing knowledge" of server setups, I have NO idea what a forward proxy configuration means. The following screens will display my basic setup which uses a Gateway Server AND a Remote Host Session server (SSL certificates exist for both. The RemoteApp Manger screen:
The Remote Desktop Connection Manager:
The RemoteApp Deployment Settings for the RD Gateway:The RemoteApp Deployment Settings for the RD Host Session Server:I have more screen shots if anyone with the RemoteApp expertise that I don't have can help and needs further information about my setup. One last thing is that I am (and always have been) substituting port 4011 for the standard 3389. Any help would be greatly appreciated.
RemoteApp-Error-External--2..jpg
Jackie Man
Your digital cert for SSL has been expired?
ASKER
One of the first things I checked:
I have 2 SSL Certificates (one for the Gateway Server and one for the Remote Host Session Server) and I even "re-keyed" them both just to be sure there were no issues there, so that's not the problem.
I have 2 SSL Certificates (one for the Gateway Server and one for the Remote Host Session Server) and I even "re-keyed" them both just to be sure there were no issues there, so that's not the problem.
Hi,
Since it's Windows server, I suspect iis could be the cause. Look at IIS and see the forward proxy configured for Remote apps?
The exact configuration can be found here
https://docs.microsoft.com/en-us/iis/extensions/configuring-application-request-routing-arr/creating-a-forward-proxy-using-application-request
Thanks
Since it's Windows server, I suspect iis could be the cause. Look at IIS and see the forward proxy configured for Remote apps?
The exact configuration can be found here
https://docs.microsoft.com/en-us/iis/extensions/configuring-application-request-routing-arr/creating-a-forward-proxy-using-application-request
Thanks
ASKER
I read the information on the URL you sent, but that was only for HTTP connections. This is an SSL, or HTTPS, connection so nothing in that explanation applied to my situation. Thanks, anyway!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I spent $ 200.00 back in April when I had a similar issue which, at the time, I knew was firewall related since I had messed up a firewall firmware update and couldn't remember my original settings because, again, I'm not a firewall expert either (and don't want to be...). At any rate, this time the issue is NOT with my firewall. My SonicWall is set up correctly (thanks to the $200 back in April), my cable modem firewall is disabled, and my Windows Firewall on the RDS server is set to allow the ports I'm using both inbound and outbound.
ASKER
Thanks for pointing me in the right direction!