Windows Server 2008 R2 SP1 RDS hang and stop responding new rdp session. Already connected session also hang as well

Question

We have a Windows Server 2008 R2 SP1 RDS supporting many ThinClients, mostly using a mandatory profile on a Windows 2003 R2 AD environment
at the moment of the hang what we experienced was:
New RDP sessions got stucked in the legend "Iniciando" (we have the spanish MUI).
Systems Events shows a lot of Warnings:
The Group Policy Client Side Extension Group Policy Shortcuts may have caused the Group Policy Service to terminate unexpectedly. To prevent further failures in the Group Policy
Service, this extension has been temporarily disabled until after the next system restart. Group Policy settings managed by this extension may no longer be enforced until the system is restarted. The vendor of this extension should be contacted if this issue
recurs.
and after that a lot of this errors:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the CryptSvc service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the NlaSvc service.
The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client.
timeout (30000 milliseconds) was reached while waiting for a transaction response from the Schedule service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the gpsvc service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the BITS service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SessionEnv service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ShellHWDetection service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the CertPropSvc service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the IKEEXT service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the iphlpsvc service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SessionEnv service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the iphlpsvc service.
During the problem we ping DC and Network Share where Profile and Document Redirection resides and they were working OK (we also did a
\\server\HomeUsers and we reached it without problem)
Only reseting the server worked, Any Ideas of what could be causing this ?? Best Regards
Federico Giampietri Latamsupport IT Infrastructure Services

Answer 1

Hi Clarence,
Today we experienced the problem again,
Users can’t login to RDS, but now they got stucked at “"Please wait for the Group Policy client”;
System log events recorded the following errors again:
timeout (30000 milliseconds) was reached while waiting for a transaction response from the Schedule service.
timeout (30000 milliseconds) was reached while waiting for a transaction response from the sessionenv service.
timeout (30000 milliseconds) was reached while waiting for a transaction response from the ShellHWDetection service.
timeout (30000 milliseconds) was reached while waiting for a transaction response from the Wuauserv service.
timeout (30000 milliseconds) was reached while waiting for a transaction response from the BITS service.
timeout (30000 milliseconds) was reached while waiting for a transaction response from the CertPropSvc service.
What path do you suggest to investigate further?
Thanks a lot!
Federico Giampietri Latamsupport IT Infrastructure Services