• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 19059
  • Last Modified:

Failing to connect via remote desktop because of terminal connection busy.

I have this XP computer that I remote desktop to, and when the XP machine first reboots, I can make the first connection to it with no problem.
But if the first connection goes down, then I get the following error when I try to connect again:
"The requested operation cannot be completed because the terminal connection is currently busy processing a connect operation"

How can I fix the XP machine so the second logon attempt works, and is there any way to force it to kill existing connection remotely?
  • 2
1 Solution
Check out this Group Policy setting in XP.

Start > Run > gpedit.msc

The navigate to
Computer Configuration > Administrative Templates > Windows Components > Terminal Services

With Terminal Services highlighted on the left, there will be a list on the right. (clicking on "standard" makes it easier to see)  Double click on "Keep-alive connections" and look at the Explain tab. I think enabling this will solve your problem.

From the explain tab

"After a terminal server client loses the connection to a terminal server, the session on the terminal server might remain active instead of changing to a disconnected state, even if the client is physically disconnected from the terminal server. If the client logs on to the same terminal server again, a new session might be established (if Terminal Services is configured to allow multiple sessions), and the original session might still be active. "



AxterAuthor Commented:
What should it be set to?

It's confusing (as many group policy items are) because it sounds like it's going to keep your connection alive, but I think that this line explains it.

"You can use this setting to enable keep-alive connections and ensure that the session state is consistent with the client state. By default, keep-alive connections are disabled."

It seems like the server isn't recognizing that the client has disconnected and enabling this should force it to check it.

I would think that setting the time to around 5 (mins) would be OK.


How i will know that from which system session is establish. I have changed on my XP machine and try to logged on server but still same issue. Pls any one help me out
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now