Remote Desktop - Lan Can't Connect

[GeorgiaIceCream]

I have 2 XP Pro PCs on a Lan. I can connect from A to B with Remote Desktop
Connection. I can't connect from B to A.

In so far as I can tell, A and B are setup identically. Terminal Services
is started on both. I am using the correct local IP address. I have tried
disabling software firewalls et cetera.

Any suggestions as to what I can check next on PC A?

[Sooner Al [MVP]]

Any chance your running NAV worm protection or MS OneCare Live Beta or
something similar?

Otherwise see this page for some troubleshooting help...

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

"GeorgiaIceCream" <Georgia...@discussions.microsoft.com> wrote in
message news:53BFDC1C-CFCF-4822...@microsoft.com...

[GeorgiaIceCream]

I have the answer. The problem PC is my wife's. She recently received an
"install this" CD from her employer.

Among the items installed was Cisco VPN Client Version 4.6.03.0021. Whatever
was installed was preconfigured by the company IT guys. Anyhow, a "service"
also got installed which appears as "Cisco Systems Inc. VPN Client". It is
setup to start automatically. I stopped the service and RDC works fine.

I tried defining the service as a "manual" start and re-booted. That didn't
work. You have to let the Cisco VPN Client service start and then stop it.

Thanks for your help.

[Sooner Al [MVP]]

Thanks for the feedback...

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

"GeorgiaIceCream" <Georgia...@discussions.microsoft.com> wrote in
message news:4923ABA6-4036-4F54...@microsoft.com...