Remote desktop connection error

[Guest]

Hi all,

I cant connect into my XP prof (SP2) machine using remote desktop, remote
desktop
is enabled,
checked and the rule is listed in the firewall exceptions, to allow from
internal network.

if i run netstat -a,

TCP main:3389 main:0 LISTENING

its listening on 3389, I can telnet from the box and the port is open,
but cant access from other boxes on same network.

The only problem i can see is in 'Select Remote Users' area, In the location
field only the localhost is listed, and i cant edit. I thought may be due to
an inactive service, so ive enabled all of the serives i have previously
disabled, now all active, and still same problem.

anyone have any ideas


thnx

michael

 

[Sooner Al]

The account you use to log onto the PC with Remote Desktop must be an Administrator or a member of
the Remote Desktop Users Group *AND* have a password. That account is local to the machine your
trying to log onto, not the remote PC that your sitting at...

http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetupandTroubleshooting.html

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...

 

[Michael]

yeah, im admin and have p/w set, im listed as a user,

its just not opening the port externally, just got me stumped



thnx

Michael

 

[Sooner Al]

Any error messages?

Anything of interest in the logs?

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...

 

[Michael]

only info I get is connection refused, which made me initially try telneting
to port 3389 on my XP machine from another machine on my network and the
port was closed.

so either the firewall isin't actually allowing the exception rule, although
it is set, or Remote Desktop, isn't for some reason initiallising and
opening the port. The firewall is allowing some excetptions, ftp... , so it
should be working

when you said check the logs, did you just mean use the 'Event Viewer'

thanks

Michael

 

[Sooner Al]

The Event and the firewall logs...

See the logging section on the page I pointed you to earlier...

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...

 

[Michael]

checked the firewall logs, nothing relating to remote desktop,

so i tried unchecking the 'remote desktop exception' in the firewall
settings and then tried connecting in, and the packets registered in the
firewall logs and were dropped, so the firewall must be working its just
that RD isin't listening on the port.

can i remove remote desktop and reinstall?

btw, thnx for the help

michael

 

[Steven L Umbach]

Check that your XP firewall does allow exceptions and that the "scope" is
correct as to IP addresses or subnet or all. If possible try to disable the
XP firewall when trying to connect from another computer on your network and
connect using the computer's IP address instead of name to see if the
problem is the firewall or something else. Of course do not disable the XP
firewall when connected to the internet without other firewall protection
such as a NAT router. And if using a NAT router, port 3389 TCP will need to
be forwarded to the internal IP address of the computer you want to remote
into. --- Steve

 

[Michael]

Hi steve,

yeah scope set to internal network, when i disable the exception the DROP'd
packects show up in the firewall log, yeah ive tried connecting via IP,

maybe its just me, but if the port isn't open its either going to be the
firewall or the app that uses/opens the port. And as i have tried with and
without the firewall, and with both 3389 is closed to external access, so im
guessing it Remote Desktop.

Would make sense if the scope was only to allow from localhost, but i have
enabled for local subnet, also tried all sources, neither would actaully
open the port.

really appreciate the help

thnx


Michael

 

[Sooner Al]

Weird problem, although I seem to remember another person with a similar problem. My problem is
trying to find that old thread.

So if you disable the Windows SP2 firewall on the PC you still can not access it using Remote
Desktop from another PC on your local LAN?

Any chance you have some other personal firewall software installed on that particular PC? Any
anti-virus software running that may be causing a problem?

Going back to the Event Log, was there anything in the log of interest? You should be logging both
successful and failed log on attempts...

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...

 

[Steven L Umbach]

Does the computer have more than one network adapter?? Try booting into safe
mode with networking to see if you can access it that way. If you can you
have another service/application interfering in which case you can use
msconfig to troubleshoot.Check that the Terminal Services service and the
Remote Procedure Call services are both started. Also check that
administrators and remote desktop users groups are included in the user
right for "allow logon through terminal services" and that there are no
entries in the "deny logon through terminal services" user right. You can do
that by opening Local Security Policy and looking under security
settings/local policies/user rights. --- Steve

 

[Michael]

worked as soon as i tried the safe mode w/ network support.

so went through msconfig, nuffin out of ordinary, I have recently upgraded
to Norton Systemworks 2005, and explicitly did not install norton internet
security. But they now include a cutdown firewall in the Antivirus portion
of the package to handle worms. As soon as i disabled the norton worm
protection, all worked like a charm.

Steven, Sooner : I really appreciate the help thanks guys

Michael

 

[Sooner Al]

Michael,

Thanks for the feedback about Norton...

Glad its working for you...

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...

 

[Tony]

Open the MS firewall app. Go to the Exceptions Tab. Click Add
Program...

Click Browse and add "C:\WINDOWS\system32\mstsc.exe"

This should do it.

 

[Steven L Umbach]

Cool. Glad you got it working. More and more people are finding that they
have software on their computers that are restricting network access in some
way. What tipped me off that may have been a possibility for you is when you
mentioned that localhost was configured as the only entity that had
permissions for Remote Desktop. Thanks for reporting back what it took to
fix the problem. --- Steve

 

[Peter Sale]

I might be suffering a related sort of problem with "remote Assistance" and
Norton System Works 2005. Exactly how did you disable the Norton Worm
protection in Systemworks 2005?

--
Regards,

Peter Sale
Santa Monica, CA USA
To email me, just pull 'my-leg.'

 

[Michael]

In the 'Options menu' select anti-virus, and theres an option there to
disable the worm protection

if you have any probelms, email me directly if you want,



Michael