W2008 R2 RemoteApp Gateway Server Unavailable Error Externally

I have had this working internally/externally for some time now, with all services on one W2008 R2 box,using a 3rd party SSL certificate.  Today I tried adding a separate site bound to a dedicated addtional IP on this box for a completely different site to redirect.
This somehow broke RemoteApp for external users. on LAN or VPN users can still access RemoteApp, but all others still get the message "This computer can't connect to the remote computer because the Terminal Services Gateway server is temporarily unavailable. Try reconnecting or contact..."
I have since removed the new site and IP from this box.. it looked like my redirect also hit the "default web site" (which is where RDWeb is installed by default). So I removed the redirect and all the Applications (RDWeb, RPC,RPCwithCert) still seem to look ok.
I have everything setup to connect to the external FQDN which is the same as the SSL cert name. etc. I have checked all known online solutions for this and nothing seems to really apply to this specific issue.  This server is now in production so any help would be GREATLY appreciated. Thanks in advance.
pacman_dAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
pacman_dConnect With a Mentor Author Commented:
Well...hopefully this helps someone else.  After exhausting all methods I could think of, I brought up another server and configured it basically the same (only the RDS roles though). I figure I could compare configurations and see the differential.
After getting a verbose error by trying to browse the /RPC VDir on the server, I started looking at the possibilty of corrupted web.config or application.host file as the error suggested. Duh, as it turned out- when I created this custom site and pointed it to inetput\wwwroot, it caused some conflicts with "Default Web Site" which shared this same directory. It created a web.config file which I noticed didn't exist on my new RemoteApp test server. Anyhoo, simply removing this file fixed the issue.
0
 
pacman_dAuthor Commented:
I have solved the issue...
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.