Re: Remote Desktop Connection Problem

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

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.

"Pegasus (MVP)" wrote:

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).


"John" <John@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:60BE9C3E-3603-4BAD-9C99-9644F2D4841B@xxxxxxxxxxxxxxxx
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

"Pegasus (MVP)" wrote:

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.


"John" <John@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:09A2B824-D9B6-4D14-B8E2-F8110A1FCA9D@xxxxxxxxxxxxxxxx
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.


"Pegasus (MVP)" wrote:


"John" <John@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AD2D7927-F149-4702-A288-E0B9EA34ACB5@xxxxxxxxxxxxxxxx
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.


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?









.

Relevant Pages

  • Suddenly Denial of getting into Control Panel....
    ... online everytime i open the Network Connection Program to ... of critical Windows updates. ... local area network and remote connections. ...
    (microsoft.public.win2000.security)
  • Re: Can not connect via remote desktop
    ... Al Jarvi (MS-MVP Windows Networking) ... How to Setup Windows, Network, VPN & Remote Access on ... My remote desktop connection was working fine within my LAN (all ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: not able to connect with remote desktop
    ... More important => Can you make a telnet connection to that specific workstation on port 3389? ... MCSA/MCSE Windows 2000/2003 ... remote computer. ... Also checked that remote desktop is enabled, ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: ActiveSync 4.1 Kills Wireless
    ... Is there some sort of wireless 'manager' application from the computer ... I had initiated the BT connection ... When wifi on Laptop is connected to WPA-PSK access point and when Windows ... Remote Access Auto Connection Manager ...
    (microsoft.public.pocketpc.activesync)
  • Re: Unable to reconnect to Remote Desktop (Windows XP SP2)
    ... I get the EXACT same behavior: I can connect using TS to my Windows XP ... Remote Desktop Host the very first time, but when I log out and try to ... > The client could not establish a connection to the remote computer. ...
    (microsoft.public.windowsxp.work_remotely)