Remote Desktop Access

[Guest]

Approximately 2 weeks ago I was able to access a computer via remote access
and everytime I try now I cannot access it. I have spoken with the business
that I am trying to access and they have not changed anything in regards to
their system, however, I can't access it. I am currently running on Windows
XP Home edition and they are running on Windows XP Pro. Does this make a
difference? And if so how come I was able to access their computer before?

 

[Guest]

I just got off the phone with the owner of the company who's computer I am
trying to access, and I went through all the set up requirements again for
remote desktop connection and everything is set up accordingly. I am still
getting the following error message:

***The Client could not connect to the remote computer.

Remote connections might not be enabled or the computer might be too busy to
accept new connections. It is also possible that network problems are
preventing your connection.

Try connecting again later. If the problem continues to occur, contact your
administrator.***

We have tried quite a few things, and I am still not able to connect. The
AV settings are set to off for allow intrusion detections.

What else could this possibly be? If you could please help me I would
greatly appreciate it.

Thanks

 

[Sooner Al [MVP]]

Are you calling the correct public IP?

If the PC is behind a firewall/router then you need TCP Port 3389 open...

Can you connect to the PC from another PC on the local LAN?

http://theillustratednetwork.mvps.o...pSetupandTroubleshooting.html#Troubleshooting

--

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

 

[Guest]

I double and triple checked that I was using the correct IP address. We also
tried connecting from another computer to the "host" computer and no luck. I
tried to trouble shoot the TCP port 3389 and it says that it is available and
that it is "listening", however, I think it is the router that is causing it
to not work. I tried to see if I could find the port online through some
trouble shooting tips from that website below and it doesn't seem to be able
to find that port through the internet. I am still at a loss as to what I
can do to correct this issue. If you can think of any other suggestions I
would appreciate it.

Thanks

 

[Sooner Al [MVP]]

So did you test over the local LAN?

http://theillustratednetwork.mvps.o...andTroubleshooting.html#Test_on_the_local_LAN

http://theillustratednetwork.mvps.org/RemoteDesktop/TroubleshootingDiagrams/Basic.html

If you can not connect over the local LAN then something on the PC itself is
blocking the incoming RDP request. Check for personal firewall software or
OneCare Live or NAV worm protection, etc...

If it works over the local LAN then it comes down to a addressing issue, or
a blocked port on the router, etc... Its possible a simple power reset of
the router may solve the issue...

--

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

 

[Robert Whitacre]

by chance is it a linksys firewall router that you are going through?