![]() Once I closed lid and tried again and it worked. Once in awhile it will time out after a long time, like 5 or 10 minutes, then give me the legal notice screen. Same problem for years when I bring laptop back to work from home. I found reports of GPClient randomly stalling the logon process for several minutes back in 2014.Īpparently that's undefined behavior that has never been fixed.Īccording to, GPClient presumably tries to fix an allegedly corrupted WBEM repositoryīut that doesn't make sense because why is TeamViewer still able to open a login screen within a second and allow me to login without delay? If the WBEM repository was corrupted at that point, it still would require repair - right? The problem arises when I put it to hibernation at home and wake it up at work. my Intel-NUC) back home.Īt work, the NUC is directly attached via LAN cable at home it is connected via WiFi and OpenVPN. On some weekends, I literally take "work" (i.e. I forgot to mention one specific circumstance that triggers the misbehavior: So your recommendation - check RDP log, then user profile log - was helpful. The application log shows the folloging warnings and errors:Įvent 17: Security Center failed to validate caller with error DC040780.Įvent 0: The description for Event ID 0 from source openvpnserv cannot be found.Įvent 6005: The winlogon notification subscriber is taking long time to handle the notification event (CreateSession).Įvent 6006: The winlogon notification subscriber took 64 second(s) to handle the notification event (CreateSession).Įvent 6006: The winlogon notification subscriber took 491 second(s) to handle the notification event (CreateSession). The RDP log lists the following events so everything is fine according to RDPĮvent 261: Listener RDP-Tcp received a connectionĮvent 1149: Remote Desktop Services: User authentication succeeded. Only return from hibernation is affected. I don't recall that the problem occurs if I power down the system. Is there any RDP diagnostic logging that can be enabled (on either side of the communication Kong Just like the verbose boot flag that tells what windows is doing right now while booting. What I'd like to know is whether there is any way to make the 1-Bit feedback of RDP ("works", "doesn't work") somewhat more verbose? ) I've already read on the internet a thousand times. Please spare me with all the "advice" (scan disk, hack some registry, reinstall windows. ![]() ![]() TeamViewer ALWAYS works if RDP has any problems whatsoever.Īfter opening and closing a TeamViewer session, another attempt to use RDP ususally works within a few seconds. TeamViewer is also installed and in this situation I can open a TeamViewer session within seconds. However, sometimes the RDP session gets stuck at the "connecting" wait screen for at least several minutes, after which I lose patience. I can access it via RDP (from the same Windows version), which works most of the time. In the evening, I put it to hibernation and the next morning I wake it up by pressing the power button. I'm running Windows 10 Enterprise LTSC 1809 on an Intel NUC.
0 Comments
Leave a Reply. |