Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ASG-RemoteDesktop 2018 RDP Login slow after passwort
#1
hi there,

i recently installed W10 1803 and all the security patches.
since then (i think) i have bad issues with authenticating into RDP Servers.


the problem it takes about 3-5 min until the authentication window disappears and i can see the rdp session.
(the Windows Security Windows goes to not responding) see Attachement

When i rdp onto the servers via MS native mstsc.exe it works fast as intended.


i tryed many things so far:

uninstalled ASG, clean Registry deletet folder and local profile.
I used a different user to test it.
I changed may gpedit and regedit settings regarding some websearches
i had RemoteDesktop 2012 before and i updated to 2018 because i thought it was a 2012 bug
we moved the database from SQL 2008 R2 to 2014

all of this made no improvement.
all my colleagues have no issues with the similar constellation - so it hase to be local client issue
I dont want to reinstall my client because this takes me 2 days ...


does anyone have an clue about the sollution?



Regards.

Felix


Attached Files Thumbnail(s)
   
Reply
#2
Never seen or heard that before - but if you colleagues do not have the same problem in the same environment it must be something regarding your RDP client - can you go to to the Components Check and see what rdp client is detected (version) - same as your colleagues? We use also the native rdp client (same as mstsc) but of course it possible that MS set parameters that we do not know?!? But it sounds really strange...
Regards/Gruss
Oliver
Reply
#3
(22-10-2018, 02:32 PM)DevOma Wrote: Never seen or heard that before - but if you colleagues do not have the same problem in the same environment it must be something regarding your RDP client - can you go to to the Components Check and see what rdp client is detected (version) - same as your colleagues? We use also the native rdp client (same as mstsc) but of course it possible that MS set parameters that we do not know?!? But it sounds really strange...

RDP:
The installed RDP client is fully supported.
Installed version: 10.0.17134 (NLA supported)      <- My colleague has the same version

HTTP/S (IE):
Internet Explorer control was found but compatibility mode is active.
Installed version: 9.11.17134.0

HTTP/S (GeckoFX):
GeckoFX could be initialized successfully.konnte erfolgreich initialisiert werden.

VNC:
The internal VNC component is installed and working correctly.

ICA:
The installed Citrix-Receiver is fully supported.
Installed version: 14.9.2000.21

SSH, Telnet:
PuTTY was found and the installed version is the one that is supported.
Installed version: 0.70

VMware:
VMware vSphere Client installed. Connect to console can be used within the application.
Installed version(s): VMware vSphere Client 5.5; VMware vSphere Client 6.0

HyperV:
PowerShell 2.0 or higher is installed. Communication with HyperV is possible.

General:
Local operating system version: Microsoft Windows NT 10.0.17134.0
Program version: 11.0.6104.1
Installation path: C:\Program Files (x86)\ASG-Remote Desktop18
....
...
Graphics Card(s): NVIDIA GeForce GTX 1050; 
DPI: 96
Windows Theme: Aero style
Symmetric Monitor Setup: Yes
Your Monitor Setup: ###
Reply
#4
So it should the newest version of RDP client on your system… Did you try to setup a new environment just for testing - a local file with one connection and one credential object - same result?
Regards/Gruss
Oliver
Reply
#5
(22-10-2018, 03:07 PM)DevOma Wrote: So it should the newest version of RDP client on your system… Did you try to setup a new environment just for testing - a local file with one connection and one credential object - same result?

i made a  new local file, created a new connection - same result - takes 5 min to connect.

i got someting:

when i choose "connect as" -> "Custom" and type in the credentials it connects in 1 sec ...

can you tell me why?
Reply
#6
Wow - no currently I have no idea what it is - but I will try to find out...

With mstsc.exe can you provide credentials to auto login and it still takes < 1 sec? Or takes that also some minutes...
Regards/Gruss
Oliver
Reply
#7
As I see in other posts (on other web sites) this problem also occurs with mstsc.exe - and there are a lot of steps like check system files, set some reg values, and so on that might help - but it is something wrong with your local system I guess
Regards/Gruss
Oliver
Reply
#8
(23-10-2018, 12:42 PM)DevOma Wrote: As I see in other posts (on other web sites) this problem also occurs with mstsc.exe - and there are a lot of steps like check system files, set some reg values, and so on that might help - but it is something wrong with your local system I guess

when i use mstsc.exe with save creds - it takes 1-2 sek ... ;-)
Reply
#9
I'm having this problem as well.  No slow login's when I use MSTSC.  On Windows 10 1809 (Build 18282).  Custom works with no delay, but the delay is at least two minutes and if you try and cancel out after, the same delay happens.  I've seen this earlier and it went away and now it's back.
Reply
#10
We have currently no clue what is causing this...
Regards/Gruss
Oliver
Reply




Users browsing this thread: 1 Guest(s)