Solved

W2008 R2 RemoteApp Gateway Server Unavailable Error Externally

Posted on 2010-11-24
2
1,283 Views
Last Modified: 2012-05-10
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.
0
Comment
Question by:pacman_d
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
2 Comments
 

Accepted Solution

by:
pacman_d earned 0 total points
ID: 34223836
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
 

Author Closing Comment

by:pacman_d
ID: 34223837
I have solved the issue...
0

Featured Post

Back Up Your Microsoft Windows Server®

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I was supporting a handful of Windows 2008 (non-R2) 2 node clusters with shared quorum disks. Some had SQL 2008 installed and some were just a vendor application that we supported. For the purposes of this article it doesn’t really matter which so w…
A safe way to clean winsxs folder from your windows server 2008 R2 editions
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…
How to install and configure Citrix XenApp 6.5 - Part 1. In this video tutorial we have explained step by step installation of Citrix XenApp 6.5 Server on Windows Server 2008 R2 is explained in this video. We have explained the difference between…

696 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question