Remote Logon Connect Fails... TS busy

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I tried to connect to a client computer (Windows XP Pro) using the remote web
workplace. Everything appeared to be working until I hit ok after entering
the appropriate username and password. Then the screen went blank, and
didn't appear to be responding, so I x'd out the session and tried again.
Since then, every time I have tried to connect, after entering the
appropriate username and password, over a period of 5 hours, I receive this
message:

Logon Connect Failed: The requested operation cannot be completed because
the terminal connection is currently busy processing a connect operation.

I have administrative access to the server/domain controller, and I've tried
using tools like qwinsta and rwinsta, to no effect. (qwinsta returns an
error to the effect of "access is denied")

I'm out of ideas, and hope someone can tell me what to do, short of driving
to the office and restarting the offending workstation.
 
Michael said:
I tried to connect to a client computer (Windows XP Pro) using the
remote web workplace. Everything appeared to be working until I
hit ok after entering the appropriate username and password. Then
the screen went blank, and didn't appear to be responding, so I x'd
out the session and tried again. Since then, every time I have
tried to connect, after entering the appropriate username and
password, over a period of 5 hours, I receive this message:

Logon Connect Failed: The requested operation cannot be completed
because the terminal connection is currently busy processing a
connect operation.

I have administrative access to the server/domain controller, and
I've tried using tools like qwinsta and rwinsta, to no effect.
(qwinsta returns an error to the effect of "access is denied")

I'm out of ideas, and hope someone can tell me what to do, short of
driving to the office and restarting the offending workstation.
Click to expand...

It sounds like a process or three froze up on you. There can be many
reasons for this - so troubleshooting exactly why right off would be a shot
in the dark.

Depending on how you access the computer remotely (through VPN?) - you may
be able to send a restart to it using the shutdown command. You also may be
able to manage the computer remotely and restart the services for Remote
Desktop.
 
Back
Top