RDWeb RDP Access Intermittent Among Workstations/PCs

Posted on 2014-07-14
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
    LVL 34

    Expert Comment

    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

    This is Server 2008 R2

    Author Comment

    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

    Author Comment

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

    Expert Comment

    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 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:
    require pre-authentication:i:1
    This is for publishing VDI through TMG 2010.

    Accepted Solution

    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 60

    Expert Comment

    thank for sharing , hope the posting has assisted.

    Author Closing Comment

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

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Free Trending Threat Insights Every Day

    Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

    At the beginning of the year, the IT world was taken hostage by the shareholders of LogMeIn. Their free product, which had been free for ten years, all of the sudden became a "pay" product. Now, I am the first person who will say that software maker…
    NTFS file system has been developed by Microsoft that is widely used by Windows NT operating system and its advanced versions. It is the mostly used over FAT file system as it provides superior features like reliability, security, storage, efficienc…
    Windows 8 comes with a dramatically different user interface known as Metro. Notably missing from the new interface is a Start button and Start Menu. Many users do not like it, much preferring the interface of earlier versions — Windows 7, Windows X…
    After creating this article (, I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

    760 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

    Need Help in Real-Time?

    Connect with top rated Experts

    7 Experts available now in Live!

    Get 1:1 Help Now