Remote Desktop Connection sees NADA

[Guest]

I am trying to use Remote Desktop Connection on my Windows XP Home laptop to
view my Windows XP MCE 2002 Desktop computer over the wireless network.

I went to the System Control Panel, Remote tab on the XP MCE machine and
checked the box for "Allow users to connect remotely..." I also used the
Select Remote User" button to add the two main usernames.

When I open Remote Desktop Connection on the XP Home laptop, there is
nothing klisted in "Computer" so I coose "Browse for more." A dialog with the
name of my workgroup opens up (NOT the name of the wireless network). But
when I try to open the workgroup to see a list of machines, I get a message,
"The (WorkgroupName) domain/workgroup does not contain any terminal servers."

What am I missing here?

 

[Lanwench [MVP - Exchange]]

In

I am trying to use Remote Desktop Connection on my Windows XP Home
laptop to view my Windows XP MCE 2002 Desktop computer over the
wireless network.

I went to the System Control Panel, Remote tab on the XP MCE machine
and checked the box for "Allow users to connect remotely..." I also
used the Select Remote User" button to add the two main usernames.

When I open Remote Desktop Connection on the XP Home laptop, there is
nothing klisted in "Computer" so I coose "Browse for more." A dialog
with the name of my workgroup opens up (NOT the name of the wireless
network). But when I try to open the workgroup to see a list of
machines, I get a message, "The (WorkgroupName) domain/workgroup does
not contain any terminal servers."

What am I missing here?

You can't browse for it. You will have to type the XP Pro computer name in
the box...or its IP address.

 

[Sooner Al [MVP]]

You could apply this registry hack... Make sure you reboot the PC once you
make the change...

http://support.microsoft.com/default.aspx?scid=kb;en-us;281307

But as noted by Lanwench simply use the local LAN IP or NetBIOS name...

--

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]

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
computer again." And if i type the computer name (no backslashes), there is
a long pause (perhaps 30 to 60 seconds) followed by the lengthy error, "The
client could not connect to the remote computer. Remote connection 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. Please
try connecting again later. If the problem continues to occur, contact your
administrator."

Any other suggestions?

 

[Lem]

I am trying to use Remote Desktop Connection on my Windows XP Home laptop to
view my Windows XP MCE 2002 Desktop computer over the wireless network.

I went to the System Control Panel, Remote tab on the XP MCE machine and
checked the box for "Allow users to connect remotely..." I also used the
Select Remote User" button to add the two main usernames.

When I open Remote Desktop Connection on the XP Home laptop, there is
nothing klisted in "Computer" so I coose "Browse for more." A dialog with the
name of my workgroup opens up (NOT the name of the wireless network). But
when I try to open the workgroup to see a list of machines, I get a message,
"The (WorkgroupName) domain/workgroup does not contain any terminal servers."

What am I missing here?

Assuming that MCE can host Remote Desktop (IIRC, XP Home can't) are your
firewalls setup OK? See
http://www.microsoft.com/windowsxp/using/mobility/getstarted/remoteintro.mspx

 

[Sooner Al [MVP]]

See this page for troubleshooting help...

http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetupandTroubleshooting.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...

--

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

 

[Sooner Al [MVP]]

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.

--

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]

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!

 

[Sooner Al [MVP]]

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

--

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]

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

 

[Sooner Al [MVP]]

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

Great... Thanks for the feedback... Glad to hear 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...
How to ask a question
http://support.microsoft.com/KB/555375