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

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1219
  • Last Modified:

Remote Desktop Gateway - TS Gateway - Speed of logon

Here is the setup. All Windows Server 2008 R2

RDGW01 - Remote Desktop Gateway, RD Connection Broker, RD Dedicated Redirector

RDSH10 - RD Session Host Server
RDSH11 - RD Session Host Server              > RD Farm  - remote.domain.local
RDSH12 - RD Session Host Server

I have a GoDaddy SSL SAN Certificate installed on all servers.  I run a remote desktop connection from outside the network to the gateway.

I am pretty sure everything is setup correctly. My question is - Should it take this long to connect in to the RD Gateway?

Here are my steps:

1. Run Remote Desktop Connection - connect to "remote.domain.local" - my RD Gateway settings are in the Remote Connection.

2. From when I click "connect" it takes 23 seconds to ask me for my password.

3. It then takes 50 seconds to log me into the remote connection.

Is this a normal amount of time?

  • 2
2 Solutions
This type of stuff is often caused by improper DNS settings where machines look at the wrong DNS when they try to authenticate the given credentials.  The DNS scheme needs to be simple, fast, quick, and efficient.

I don't mess with any "farms" and do very little with Certificates, but I have seen this bad behavior with logons/authentication in other products that can suffer from the same problems.
LeviDailyAuthor Commented:
Thanks for the help I called Microsoft, they checked out the environment and said it cant be sped up. Thanks for the help
LeviDailyAuthor Commented:
Worked with Microsoft, no answer.

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now