See this page for troubleshooting help...
http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetupandTrouble
shooting.html
Make sure...
1. Your calling the correct static private LAN IP.
2. If your running any software firewall software on the PC your trying to
connect to make sure TCP Port 3389 is open on the firewall.
3. If your running NAV 2005 worm protection or Microsoft OneCare Live Beta
you may need to configure the software to allow incoming Remote Desktop
connections...
Post questions concerning Remote Desktop to the...
microsoft.public.windowsxp.work_remotely
...news group...

Signature
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...
> If I type the IP address, I quickly receive the error, "The connection was
> ended because of a network error. Please try connecting to the remote
[quoted text clipped - 33 lines]
>> in
>> the box...or its IP address.
srtriano - 14 Jan 2006 00:15 GMT
I tried stepping through the tips on the page you suggested. I reached the
section on trying "netstat -a" at the cmd prompt (of the host machine). The
command returned the title (Active connections) and the column headings
(Proto, Local Address, Etc.) and then froze. I had to close the command
window. Is this a symptom of some bigger problem? I can map and share files
between the computers just fine! On the XP Home laptop, the "netstat -a"
command worked perfectly.
Also, I saw a line on the website suggested by Lem
http://www.microsoft.com/windowsxp/using/mobility/getstarted/remoteintro.mspx
and it said that "both computers must be connected to the internet. is this
really true? I only have dial-up with one computer able to use the Internet
at a time. I am using the network for File and Printer sharing only right
now. Doesn't Remote Desktop work on a LAN without an Internet Connection?
Thanks!
srtriano
> See this page for troubleshooting help...
>
[quoted text clipped - 52 lines]
> >> in
> >> the box...or its IP address.
Sooner Al [MVP] - 14 Jan 2006 11:25 GMT
Remote Desktop works over a local LAN or over the public internet. You
simply need to use the correct address when calling.
Look in the event log for messages that may provide a clue to why netstat is
locking up. It may be indicative of other issues with your PC.

Signature
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...
>I tried stepping through the tips on the page you suggested. I reached the
> section on trying "netstat -a" at the cmd prompt (of the host machine).
[quoted text clipped - 85 lines]
>> >> in
>> >> the box...or its IP address.
srtriano - 14 Jan 2006 16:01 GMT
Netstat was locking up because I was connected to the internet via a
glacially-slow dial-up connection. Offline, netstst worked flawlessly and
showed that I was listening to port 3389.
I decided to try Real VNC (www.realvnc.com) and it worked flawlessly for me.
I was up and running with a remote desktop in less than 15 minutes (including
the download and configuration time!). I will give up on the MS Remote
Desktop for now. . . maybe forever!

Signature
Thanks!
srtriano
> Remote Desktop works over a local LAN or over the public internet. You
> simply need to use the correct address when calling.
>
> Look in the event log for messages that may provide a clue to why netstat is
> locking up. It may be indicative of other issues with your PC.
Sooner Al [MVP] - 14 Jan 2006 17:38 GMT
Keep in mind VNC (any flavor) is *NOT* natively encrypted. That is a
potential and probable security risk particularly if you use it over the
public internet. If you do use VNC then I suggest using UltraVNC with its
encryption plug-in over the public internet or run VNC (any flavor) through
a VPN or Secure Shell (SSH) tunnel for added security...

Signature
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...
> Netstat was locking up because I was connected to the internet via a
> glacially-slow dial-up connection. Offline, netstst worked flawlessly and
[quoted text clipped - 13 lines]
>> is
>> locking up. It may be indicative of other issues with your PC.
TechnoStuff - 27 Jun 2007 21:24 GMT
EURIKA!!!
One very helpful and crucial tidbit in this post from Sooner ---- "3. If
your running NAV 2005 worm protection".
If you have Norton Anti Virus 2005, shutting OFF the Worm Protection will
open Port 3389 from the "filtered" status to the "listening" status and allow
the RDC to connect!
Thank you SOONER!!
> See this page for troubleshooting help...
>
[quoted text clipped - 52 lines]
> >> in
> >> the box...or its IP address.
Sooner Al [MVP] - 27 Jun 2007 21:58 GMT
> EURIKA!!!
>
[quoted text clipped - 8 lines]
>
> Thank you SOONER!!
Great... Thanks for the feedback... Glad to hear its working for you...

Signature
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...
How to ask a question
http://support.microsoft.com/KB/555375