Remote Desktop Connection Problem

  • Thread starter Thread starter John
  • Start date Start date
J

John

I am having a problem with Remote Desktop Connection with Windows XP Pro. I
am able to connect but after I disconnect the session and try to use RDC
again at a later time Iam unable to connect again. I have found that the
remote computer becomes locked and the only way to gain access is to have
someone unlock the computer at the remote location. Obviously if nobody is at
the remote computer I cannot get access. If the computer is in a locked state
it will not allow RDC connections. Is there a way to keep RDC from locking
the computer when I disconnect from it? I have never had this problem before,
but have primarily access Windows servers with remote desktop, not XP Pro
workstations. Any help would be appreciated. Thanks.
 
John said:
I am having a problem with Remote Desktop Connection with Windows XP Pro. I
am able to connect but after I disconnect the session and try to use RDC
again at a later time Iam unable to connect again. I have found that the
remote computer becomes locked and the only way to gain access is to have
someone unlock the computer at the remote location. Obviously if nobody is
at
the remote computer I cannot get access. If the computer is in a locked
state
it will not allow RDC connections. Is there a way to keep RDC from locking
the computer when I disconnect from it? I have never had this problem
before,
but have primarily access Windows servers with remote desktop, not XP Pro
workstations. Any help would be appreciated. Thanks.
Click to expand...

Some questions:
- What exactly do you mean with "the remote computer is locked"?
- What do you see on the screen when you try to make a connection?
- You say that you never had this problem before. What's happened since
then?
 
Thanks for getting back to me. The remote computer in question is my business
partners home office PC and I am going off what he has told me. When I say
the computer is locked he said it says: "Computer Locked. This computer is in
use and has been locked. Only (his login name) or Admnistrator can unlock the
computer. Press Ctrl.Alt.Del to unlock this computer." which appears to be
the standard Windows screen. On my end when I try to make a connection I get:
The client could not connect to the remote computer. Remote connedctions
might not be enabled or the computer might be tto busy to accept new
connections. etc...
When I said I have never had this problem before I just meant that I
normally use RDC to connect to Windows servers not workstations and have
never had an issue like this. If someone is at the remote location and they
press Ctrl-At-Del and log into the computer and I try to connect it works.
His remote computer has a static IP address and we are using a Sonicwall
TZ170 and NAT to translate the public to the private IP address. Let me know
if you need any further clarification as this is driving me crazy. Thanks.
 
I'm not the OP.
more inline...

John said:
This computer is in
use and has been locked. Only (his login name) or Admnistrator can unlock
the
computer. Press Ctrl.Alt.Del to unlock this computer."
Click to expand...

Sounds like screen saver with password protection kicks in. Uncheck "On
resume, password protect" option in Display Properties - Screen Saver tab.
When I said I have never had this problem before I just meant that I
normally use RDC to connect to Windows servers not workstations and have
never had an issue like this.
Click to expand...

Servers are different.
 
OK, let's try this diagnostic command, both when the remote machine is not
locked (so that you know what to expect) and when it is locked.
1. Click Start / Run / cmd {OK}
2. Type this command:
telnet NameOfRemotePC 3389{Enter}
Report what happens in both cases.
 
When it is locked I get the following:
C:\Documents and Settings\John>telnet xx.xx.xxx.xxx 3389
Connecting To xx.xx.xxx.xxx...Could not open connection to the host, on port
338
9: Connect failed (I edited out the actual IP address with xxx's)

When it is unlocked It appears to be connected but the cmd window is just
blank (the line that reads C:\Documents and Settings\John goes away) with a
flashing cursor
 
Your tests tell you why you can no longer connect when the machine is
locked: It has turned off the port that is used for Remote Desktop (port
3389). I suspect that your screen saver does a little more than just turning
off the screen - does it have some firewall-related functions that turn off
ports? I would run some experiments with a different screen saver. I would
also temporarily disable the firewall (but only if you have a hardware
firewall such as a router between your network and the outside world).
 
As far as I know, he is not using a screen saver or if he is it is just the
standard Windows XP without the password protect enabled. I will check it
and get back to you. He did also tell me something interesting, he said if he
left the computer on he could come back 2-3 hours later and it would still be
at the desktop (no screen saver) and not in a locked state. It must go into
the locked state after more than 3+ hours. If he does not have a screen saver
enabled, what would cause windows to go into a locked mode? I will also check
the firewall (Windows firewall is disabled he is using Symantec Internet
Sedcurity) settings and try to disable it over the weekend, unfortunately I
can not remotely access the computer now due to the issue! Thanks.
 
After reading quite a few critical reports about Symantec products I am
rather critical about them. If this was my show then I would at least
disable but preferably uninstall this product. I suspect that it might solve
your problem immediately.

Alternatively you could check the Symantec FAQs and look for "Remote
Desktop" issues.
 
(I'm not the OP)

John said:
If he does not have a screen saver
enabled, what would cause windows to go into a locked mode?
Click to expand...

PC might go to standby mode and requires password when resuming from
standby. Check Power Options setting.
I will also check
the firewall (Windows firewall is disabled he is using Symantec Internet
Sedcurity) settings and try to disable it over the weekend
Click to expand...

Checking Symantec firewall settings would be a great idea. Disabling
firewall is a different story. Make sure the PC is protected with hardware
firewall such as a home router. Don't leave the firewall disabled too long.
 
The problem was that it was set for standby after 3 hours in the power
options with a required password. I thought I checked for that originally but
must have missed it. Thanks to all for your assistance.
 
Back
Top