Terminal Server session hangs
Will Crisp <[email protected]> Thu, 18 Sep 2014 15:25:08 -0500
| Newsgroups | gmane.network.rdesktop.user |
|---|---|
| Message-ID | <CALxAi_-vrSEz4qvjJMZtYUcs3Y8-zf4WU0w+YGnvdb-MZ_v-Ng@mail.gmail.com> |
--===============7840485338120748368== Content-Type: multipart/alternative; boundary=047d7bb0498ee06c6705035cc78f --047d7bb0498ee06c6705035cc78f Content-Type: text/plain; charset=UTF-8 My company uses a "Windows 2008 Server R2" Terminal server to support its Linux users for email access (among other things). For some time now, at least a few times a week, I'll run into a situation when I can't login or resume my existing rdesktop session. The session will remain hung on the "Welcome" screen. I've raised the issue to my company's IT department but they say they can't fix the issue. IT says the issue is caused by users using "non-Microsoft" remote desktop clients that don't properly log-off their session and just close their rdesktop window. These sessions sometimes get in a hung state where noone else can log into the terminal server until the server is rebooted. IT says they don't see this behavior with Microsoft remote desktop clients. Has anyone else seen this behavior? Any advice how to fix this? Thanks, -Will --047d7bb0498ee06c6705035cc78f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div><div><div>My company uses a "Windows 2008 Server= R2" Terminal server to support its Linux users for email access (amon= g other things).=C2=A0 For some time now, at least a few times a week, I= 9;ll run into a situation when I can't login or resume my existing rdes= ktop session.=C2=A0 The session will remain hung on the "Welcome"= screen.=C2=A0 I've raised the issue to my company's IT department = but they say they can't fix the issue.=C2=A0 IT says the issue is cause= d by users using "non-Microsoft" remote desktop clients that don&= #39;t properly log-off their session and just close their rdesktop window.= =C2=A0 These sessions sometimes get in a hung state where noone else can lo= g into the terminal server until the server is rebooted.=C2=A0 IT says they= don't see this behavior with Microsoft remote desktop clients.<br><br>= </div>Has anyone else seen this behavior?=C2=A0 Any advice how to fix this?= <br><br></div>Thanks,<br></div>-Will<br></div> --047d7bb0498ee06c6705035cc78f-- --===============7840485338120748368== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk --===============7840485338120748368== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ rdesktop-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rdesktop-users --===============7840485338120748368==--