Unable to reset connection
- I have a thin client that was connected to one of my TS2008 servers, showing in Terminal Services Manager as State as Active, with a long Idle Time. The client says it is trying to connect, but never does. If I reset the connection, the Session on the server shows blank (no longer RDP-Tcp), but still shows as Active. Nothing I do can reset that connection, and the client can no longer connect to the server. So far, the only way I have found to remedy this situation is to reboot the server.
Can someone suggest a better solution? I have about 100 thin clients with four TS2008 servers, and see this nearly every week.
All Replies
- Is it possible to get a memory dump when this happens? We can debug it and see if we can identify the root cause. Else, at least provide the event log.
Thanks! - What is the procedure for taking the memory dump?
I don't see anything in the event log that relates to the problem. - Hi,
It should be possible to reconnect sessions if all the components have been configured properly. (TS session broker, DNS with round robin)
If reconnection works properly then you no longer have to reset/remove idle connections that cannot be reconnected.
The following technet articles explain all the settings for confiiguring session reconnection:
http://technet.microsoft.com/en-us/library/cc772418.aspx
http://technet.microsoft.com/en-us/library/cc731045.aspx
Danny.
Now you can follow al the hot TS forum threads on twitter! http://www.twitter.com/mstermserv Founder of www.citrix-guru.com and www.rds-support.eu Linkedin: www.linkedin.com/in/dnyvandam- Proposed As Answer byDanny van Dam Monday, November 09, 2009 4:15 PM
- Unproposed As Answer byLionel Chen - MSFTMSFT, ModeratorThursday, November 12, 2009 7:03 AM
- All the components have been configured correctly. I only have a problem because TS is not working correctly. TS session broker is directing the client back to the original connection, and that is the problem. The connection is dead. It is like a traffic cop that keeps sending a car down a dead-end street.
- John,
Have you tried setting GPOs to control the resetting of idle and disconnected settings?
Computer Config | Admin Templates | Windows Components | temrinal Services | Temrinal Server | Session Time Limits
Also, can you please use the command line to try to end this session?
on the terminal server, open a command prompt and type:
query session
this will give you all the sessions running on this server.
Find the ID of the bad session and run:
reset session <Session ID>
Then run:
query session command again. What do you see?
Hope this helps,
Kristin L. Griffin
Co-Author of the Windows Server 2008 Terminal Services Resource Kit (and a SUPER BIG fan of the Microsoft RDV Team!!!) - Yes, I have set the timeouts via GPO
I tried reset session at the command prompt, and it reported success, but query session shows the session as still active. - can you reconnect to that session using a different machine, say a desktop computer?
Can you remote control it (shadow it)?
Or is it just dead but a ghost...
any weird event logs on the server?
Hope this helps,
Kristin L. Griffin
Co-Author of the Windows Server 2008 Terminal Services Resource Kit (and a SUPER BIG fan of the Microsoft RDV Team!!!) - Attempts to remote control it give me an Access Denied error. I don't get that error when I remote control other sessions on the same server.
I am not sure how to connect to that particular session from a desktop.
When I check the thin client trying to reconnect to the session, it has the blue Windows background, the 'busy' circle, and 'Welcome', that will stay like that for several minutes, then timeout. - do you restrict your users to one session? If so then log into the server as the same user that has the weird session and see if you connect from a desktop or get any other even log errors,
anything in the event logs on the server? Is the server fully patched?
Hope this helps,
Kristin L. Griffin
Co-Author of the Windows Server 2008 Terminal Services Resource Kit (and a SUPER BIG fan of the Microsoft RDV Team!!!) - Users are restricted to one session.
I tried logon at console as the user account with the dead session. I get the as the thin client - 'Wecome' screen for about 10 minutes, then error message that the logon attempt timed out.
There is nothing in the event logs on the server to indicate what the problem is.
The server is SP2. - ok, how about looking at this from a "profile" perspective. Can you delete (or rename for now) the user's profile and try to log in again? Perhaps the profile is corrupt, since it seems that you are getting logged in but then timing out at a black screen.
Hope this helps,
Kristin L. Griffin
Co-Author of the Windows Server 2008 Terminal Services Resource Kit (and a SUPER BIG fan of the Microsoft RDV Team!!!) - I can rename the roaming profile on the file server, but the terminal server still thinks this user is connected, so a copy of the profile still exists locally, and it will not let me delete it.
Also, the screen is not black, it is the standard blue windows screen you get at login, where it says "Welcome". - You said you could reboot the server. Can you do this, then delete the local copy of the profile, rename the roaming profile and then try to connect as that user?
Hope this helps,
Kristin L. Griffin
Co-Author of the Windows Server 2008 Terminal Services Resource Kit (and a SUPER BIG fan of the Microsoft RDV Team!!!) - That will 'solve' the problem for now, but it is a recurring problem, and rebooting terminal servers in production is not a good solution.
Is there no other option? - I think what Kristin is getting at is if it's a profile problem. have you eliminated the profile as the problem by giving the end user a new profile and then see if it happens again.
- yep. Just do this as a test. Rebooting is not what I am suggesting as a fix. I just want you to do it so that you can eliminate the profile on the TS box.
Hope this helps,
Kristin L. Griffin
Co-Author of the Windows Server 2008 Terminal Services Resource Kit (and a SUPER BIG fan of the Microsoft RDV Team!!!) - I can't reboot the server right now.
I know from recent previous experience with this problem that deleting the profiles is not a requirement. I have three other thin clients that had this exact same problem. Rebooting the server cleared the dead connection. The thin clients were then able to connect to the servers. The problem has not yet returned to those particular three clients. Does that answer your question?
I can not delete the profile on the server without rebooting the server, so there is no way for me to test if the profile alone, without a server reboot, is the source of the problem. I seriously doubt it is. Hello John,
If you don’t use the session broker and try to reconnect to the session directly, is the issue occurring? If it is, the issue is not related to the session broker and we will troubleshoot it from the TS service side; If not, we may need to collect some logs on the TS session broker server and analyze it.
Please let us know the result. Thanks.
Regards,
Lionel Chen· Lionel Chen
- I am not sure I understand you.
I have tried reconnecting to the dead session, both from a thin client and the server console. I think the later bypasses session broker. If not, tell me what to try.
Again, we seem to have drifted from the original problem, which is that I can not get rid of the session without rebooting the server. I don't see the point of trying to reconnect to it. It is a dead session - reconnecting is not something I want to be able to do anyway.
