We just started experiencing an issue during testing with four terminal servers that have started disconnecting users from the desktop after 3-5 seconds of logging on via RDP. A change was made with a com port mapping last night which was the last change was made before the issue presented. Disabling it did not resolve the problem. There is a licensing policy for idle disconnect set at 2 hours. Administrator accounts aren’t affected but user accounts are. This just started happening today. Any suggestions would be appreciated. Thank you very much.
-Scott
Windows 2008 Terminal Server logoff issue
-
- 4StarLounger
- Posts: 402
- Joined: 14 Apr 2010, 15:59
-
- Administrator
- Posts: 78596
- Joined: 16 Jan 2010, 00:14
- Status: Microsoft MVP
- Location: Wageningen, The Netherlands
Re: Windows 2008 Terminal Server logoff issue
Sorry about the lack of replies -apparently we don't have experts on this subject.
Try one of these articles, depending on the version of Windows Server 2008 you're using:
Remote Desktop disconnected or can’t connect to remote computer or Remote Desktop server (Terminal Server) that is running Windows Server 2008
Remote Desktop disconnected or can’t connect to remote computer or to Remote Desktop server (Terminal Server) that is running Windows Server 2008 R2
Try one of these articles, depending on the version of Windows Server 2008 you're using:
Remote Desktop disconnected or can’t connect to remote computer or Remote Desktop server (Terminal Server) that is running Windows Server 2008
Remote Desktop disconnected or can’t connect to remote computer or to Remote Desktop server (Terminal Server) that is running Windows Server 2008 R2
Best wishes,
Hans
Hans
-
- 4StarLounger
- Posts: 402
- Joined: 14 Apr 2010, 15:59
Re: Windows 2008 Terminal Server logoff issue
Hans,
Sorry for the slow response. This helped. The first article mentioned a com port redirect conflict which turned out to be the issue on one of the clustered Citrix servers that in turn was causing issues on the terminal servers.
Thanks for your help!
Sorry for the slow response. This helped. The first article mentioned a com port redirect conflict which turned out to be the issue on one of the clustered Citrix servers that in turn was causing issues on the terminal servers.
Thanks for your help!