Windows Server 2012 R2 (TS) connection lost (idle time) after exactly 8 Hours
Posted on 2016-10-19
After a lot of googling i am here to ask the experts for this anoying problem regarding session time outs on a specific terminal server.
I have several terminal servers, a connection broker and a remote desktop gateway and offcourse a Domain controller with defined group policy. At first i thought this defined policy was causing the issue.
Set time limit for active but idle Remote Desktop Services sessions = 8 Hours
Which is also configured on the other terminal servers. and dont cause any problem.
I removed this policy, did a gpupdate /force and restarted the terminal server because its a computer policy obviously. :).
Still weird because the user in question is not idle at the time the event takes place.
The event : User gets logged off after exactly 8 hours. With the notification "session timed out, idle time exceeded"
I have checked the folowing options
- NPS settings on the Remote Desktop Gateway (where no idle time is defined)
- Remote Desktop Gateway Manager, where no policy is defined nor policy folder is visible.
- Local GPedit.msc where the policy is not configured.
I have no idea where to start.
The event viewer shows the following error when the event takes place (exactly 8 hours from start of login)
"Cached User logon fails when LSASRV event 45058 indicates FIFO deletion of cached credential"
Which is quite normal for a terminal server event viewer.
I also created a policy "Configure keep-alive connection interval" keep alive interval = 10
Still i get the disconnects after exact 8 hours...
Any suggestions where to start looking further?