[Webinar] Learn how to a build a cloud-first strategyRegister Now


RDWeb RDP Access Intermittent Among Workstations/PCs

Posted on 2014-07-14
Medium Priority
Last Modified: 2015-02-08
RDWeb RDP Access Intermittent Among Workstations/PCs

I am seeing this issue currently with a domain:
RDWeb and IIS is setup properly and working.
Everything is configured correctly - certs are in place, matching, etc.
Recently access to Workstations via RDP is failing inside RDWeb.
This is also happening with RemoteApps

This happens on only some workstations, and it does not seem to be IE version or OS version dependent. Has anyone seen this, and know the update(s) that may be causing the issue?
Question by:bizco
  • 5
  • 2
LVL 38

Expert Comment

ID: 40195597
Is this 2012 \ 2012 R2 RD Web access ?

In that case if you are using Win 7 clients, you need to update RDP clients on win7 to RDP 8 \ 8.1


Author Comment

ID: 40195639
This is Server 2008 R2

Author Comment

ID: 40195644
What error do you see when the connection fails?
The remote access gateway is unavailable

Does access fail to all workstations and RemoteApps at once, or is it inconsistent?
The remote access is consistent on failure per workstations, either the workstation can or cannot.

What does the issues follow (the workstation the resources are accessed from, the resource accessed, an Internet carrier, time of day, etc.)?
Nothing in common
When the issue occurs, can you ping the resource?
You can ping the resource
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.


Author Comment

ID: 40235294
Points Increased, also looking into mstsc.exe version, most are not working with different versions, so that eliminates that.
LVL 65

Expert Comment

ID: 40267844
the forum seems to share similar issue

I would suggest the following action plan.

1. Minimize the complexities. The error you are seeing states that RDGateway is not available. Do not test by connecting through the RDWeb page. Use only MSTSC and connect using these settings (where server.domain.com is you will replace with the FQDN that is on the subject line of the certificate that is bound to the Gateway service.  Based on configuration, you may have to use “hosts” files to resolve the name if needed). It is very important to uncheck the “Bypass RD Gateway server for local addresses” in the Remote Desktop Client. Otherwise it will still utilize 3389 which would work internally.

2. Test internally first. Preferably on the Gateway server itself. Does it work?  If so move to another server\client on the internal environment and try to connect to another device utilizing the RD Gateway settings in the MSTSC.  Did that work?

3. Test externally only utilizing MSTSC trying to RDP through the Gateway service to an internal device.  Don’t utilize Websso or RDWeb as they are completely different services and we don’t want to confuse the troubleshooting steps any more than they may be.

4. Once we have proven we can get the RDGateway to work internally using MSTSC then try utilizing the RDWeb page. Does it work internally? (Keep in mind that you must also uncheck the Bypass option in the RemoteApp\RD Gateway configuration otherwise it will utilize 3389 to connect).

*Note: We need to keep in mind that RemoteApp, RDWeb, WebSSO, and RDGateway are different services that provide different functionality.  RDGateway is nothing more the a proxy service that converts incoming SSL data (actually RPC over HTTPS) to RDP 3389 data and passes it to the backend resource you are trying to contact.  Get that working first without all the other services.
** If everything works good internally, then you know that the issue is somewhere within the Firewall or outside getting in.
Eventually, the author went through


I added this line in remote desktop connection manager > go to the personal vertual desktops properties > Custom RDP setting    >
pre-authentication server address: s: https://TsGateway.company.com/rdweb
require pre-authentication:i:1
This is for publishing VDI through TMG 2010.

Accepted Solution

bizco earned 0 total points
ID: 40387153
Found the issue was due to configuration. RDWeb was sharing a OWA certificate to cut cost. Migrated RDWeb to another server and all is working fine now.
LVL 65

Expert Comment

ID: 40387717
thank for sharing , hope the posting has assisted.

Author Closing Comment

ID: 40596666
It wasnt configured in best practice so I moved the RD Server

Featured Post

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Question has a verified solution.

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

Know the reasons and solutions to move/import EDB to New Exchange Server. Also, find out how to recover an Exchange .edb file and to restore the file back.
Most folks would know the basics of how Dropbox works, so that’s not the purpose of this article. Security is what it’s all about, so here I’ll share how I choose to secure my Dropbox Account and the Data it contains.
Internet Business Fax to Email Made Easy - With  eFax Corporate (http://www.enterprise.efax.com), you'll receive a dedicated online fax number, which is used the same way as a typical analog fax number. You'll receive secure faxes in your email, f…
Finding and deleting duplicate (picture) files can be a time consuming task. My wife and I, our three kids and their families all share one dilemma: Managing our pictures. Between desktops, laptops, phones, tablets, and cameras; over the last decade…

865 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