2

I've been using remote desktop in the past with no issues, It's been a year since I used it, today I decided to connect using it but it's super slow (minutes) trying to connect. It's fast to ask for the credentials, then hangs for a long time, once connected it's fast again.

The remote allowed any version of remote desktop, I did a test where I could connect without using NLA (Network Level Authentication) and it was fast, no delay and was able to login though the GUI.

This last attempt closing the RDP (connected using NLA) seemed to have the disconnect hanging as well (caused windows explorer to hang (desktop, other apps)). Until I ended the rdp task (and after about 10 seconds things started to respond again).

Win10X64 Pro.

I've tried connecting to different targets on the network, all the same.

Any idea on what could have happened to cause this or how to fix?

Improve this question
5
  • Well in this case rebooting everything seem to have solved whatever was throwing it off.
    – user3161924
    Commented May 31, 2023 at 5:50
  • But it's only temporary, eventually it comes back to 4 minutes to connect or do anything with NLA. Not only that, it can also hang the entire windows UI until it clear, not all the time, but sometimes it ends up where you can't click on start menu, taskbar items, etc.. You can bring up the ctrl-shift-esc list...
    – user3161924
    Commented Jun 3, 2023 at 17:29
  • AHHHH - It turns out the domain was entered as \\machinename instead of machinename that throws off whatever parts of windows to do weird things.
    – user3161924
    Commented Jun 3, 2023 at 18:27
  • Well, that fixed it for a day - it came back. If I remove the hardware token / smart card on the system then it's fast, plug it back in, 4 minute wait. How do I tell NLA to not try and use the smart card. advancedSettings.put_RedirectSmartCards(FALSE); is already set.
    – user3161924
    Commented Jun 6, 2023 at 3:09
  • Having experienced this myself without any resolution, I suspect this is related to the client trying to establish a RDP session under UDP, failing, and then falling back to TCP. In my experience the connection takes 2 minutes to establish, and if I the disconnect and reconnect it connects instantly. But the connection is always TCP, never UDP.
    – Cillié Malan
    Commented May 2 at 8:29

1 Answer 1

Reset to default
1

Maybe old response. I deleted the server RDP log and aparently got faster. How to delete the log space:

  • Open event viewer
  • Go to Applications and Service Logs / Microsot / Windows / terminalServices-xxx - where xxx is all options
  • minimum size is 68kb.
  • Click on each option and right-click and choose Clear Log.

For me, it was delaying 20 seconds do log in. After clean, 2 seconds.

Hope it helps.

Improve this answer

You must log in to answer this question.

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