1

When connecting to one of my servers with remote desktop it takes an unusually long time to present me a log in box. After connecting server is very responsive so it doesn't seem like it is running low on resources.

  • It only happens on this one server.
  • Server is running Windows Server 2008r2
  • The server is one of multiple hosted on a hyper-v box.
  • Hyper-V manager shows that disk usage and memory usage is low.

What might be causing this delay?

4
  • Could you be more specific about what happens while you wait and how exactly your connecting to the server ?
    – Stephane
    Apr 29, 2013 at 9:13
  • @Stephane i connect using mstsc as usual. Then i get the connecting to window 'initializing remote connecting' for a long time. Then it asks for username and password like usual
    – t123
    Apr 29, 2013 at 10:09
  • Do you get the username and password promt in a MSTC dialog or do you go to the server remote console and are prompted there ? I'm asking so I can find out if you have an issue with network-level authentication
    – Stephane
    Apr 29, 2013 at 12:26
  • @stephane it asks in a dialog box
    – t123
    Apr 29, 2013 at 15:26

3 Answers 3

2

Turns out it was a DNS issue; trying 3 IPv6 addresses that wouldn't connect before trying a working IPv4 address.

Sorry all!

0

Is the 2008 R2 server isolated from the internet? Most likely it's attempting to update its root certificates and timing out.

Try the following

  1. Launch Computer Configuration
  2. Go to Policies
  3. Open Administrative Templates
  4. Expand System
  5. Explore Internet Communication Settings

Change the setting of "Turn off Automatic Root Certificates Update" to enabled

0

You can enable user logon logging by following the instructions in KB221833.

That will create a log file in %Systemroot%\debug\UserMode which will contains timing information about each step of the logging process.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .