RDC error - client can not connect

  • Thread starter Thread starter Brian
  • Start date Start date
B

Brian

I'm running an XP Pro host and 98SE laptop client (both
fully updated) and Linksys 650+ and 520+ 802.11b wireless
cards and McAfee 8.0. The peer-peer network is controlled
by D-Link AirPlus software at both ends. Internet
Connection Sharing works.

After starting Remote Desktop on the laptop and clicking
connect, the following error is displayed: "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."

Anyone have any ideas?

Thanks for reading!

Brian
 
Can you ping the desktop from the laptop? Is the desktop running the ICF or some other personal
firewall? Is Remote Desktop enabled on the desktop? Are you calling the correct IP?

--
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...
 
1. Yes, I can ping the desktop from the laptop.
2. The desktop is running a firewall only on the internet dial-up network. No 3rd party firewall is installed. Using 128 bit encryption on the D-Link network software wouldn't contribute to the problem, would it?
3. Yes, Remote Desktop is enabled on the desktop.
4. When I start Remote Desktop on the laptop, I specify the desktop by using the "browse" button and surfing to the desktop through the peer-peer network workgroup.

Thanks for your help.

Brian
 
Hmmm...

Item 4... Did you try using the IP of the desktop versus the browser method?

Anything running on the laptop that could be blocking TCP Port 3389 outbound, like personal firewall
software?

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

Brian said:
1. Yes, I can ping the desktop from the laptop.
2. The desktop is running a firewall only on the internet dial-up network. No 3rd party firewall
Click to expand...
is installed. Using 128 bit encryption on the D-Link network software wouldn't contribute to the
problem, would it?
3. Yes, Remote Desktop is enabled on the desktop.
4. When I start Remote Desktop on the laptop, I specify the desktop by using the "browse" button
Click to expand...
and surfing to the desktop through the peer-peer network workgroup.
 
1. Yes, I can ping the desktop from the laptop.
2. The desktop is only running ICF on the internet dial-up
connection. No 3rd party firewall is installed.
3. Yes, Remote Desktop is enabled on the desktop.
4. After I start Remote Desktop on the laptop, I click the
browse button to locate the desktop on the peer-peer
network workgroup.

Thanks so much for your help, Al!

Sincerely,

Brian
 
1. Yes, I can ping the desktop from the laptop.
2. The desktop is running a firewall only on the internet
dial-up network connection. No 3rd party firewall is
installed.
3. Yes, Remote Desktop is enabled on the desktop.
4. After I start Remote Desktop on the laptop, to specify
the computer I click the "browse" button and surf my way
to the desktop through the peer-peer network workgroup
I've established.

Thanks so much for your help.

Sincerely,

Brian
-----Original Message-----
Can you ping the desktop from the laptop? Is the desktop
Click to expand...
running the ICF or some other personal
firewall? Is Remote Desktop enabled on the desktop? Are you calling the correct IP?
Click to expand...
for the mutual benefit of all of us...
 
Hmm looks like the NNTP servers may be a bit flakey today!

See if I have this right:

You've an XP Pro desktop, running ICS and ICF connected wirelessly to a
laptop.

You've verified that the ICF is only enabled on the interface to the
Internet, which is separate from that to the wireless network?

I'm puzzled by your description of browsing to the desktop machine--unless
it is running Windows 2000 server or Windows Server 2003, browsing isn't
enabled by default and should have required a registry change--did you do
that?

Have you tried, rather than browsing, typing the netbios name of the XP Pro
desktop machine into the box, or, the private IP address of the XP Pro
machine?

The options here are failures of name resolution, firewalls, or the feature
not being configured, or active in the first place. You can look at the
list of running services to see whether Terminal Services is amongst them.
Does the McAfee package include any firewall functionality?
 
IT LIVES!!! Al, I love you, man! Last night I tried
entering what I thought was the IP of the desktop
(192.168.0.185 is what came up when I ping'ed it from the
laptop), but it connected on the first try with
192.168.0.1. What gives?

I'm not familiar with TCP Ports, but the only thing out of
the ordinary that I've got going on this laptop is an
internet gateway for Internet Connection Sharing.
Sometimes the internet gateway doesn't show-up in the sys
tray and upon reboot it does. Choosing IG from the
Communications folder doesn't bring it up either.

Thanks for your help, Al!

Sincerely,

Brian
-----Original Message-----
Hmmm...

Item 4... Did you try using the IP of the desktop versus the browser method?

Anything running on the laptop that could be blocking TCP
Click to expand...
Port 3389 outbound, like personal firewall
software?
Click to expand...
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...
Click to expand...
internet dial-up network. No 3rd party firewall
is installed. Using 128 bit encryption on the D-Link
Click to expand...
network software wouldn't contribute to the
problem, would it?
Click to expand...
the desktop by using the "browse" button
 
Bill:

I tried entering the IP address of the desktop and it
worked!

When I first started RDC on my laptop, I clicked on the
drop down box where the "computer" is specified. The
first time I tired to connect, intuition told me to
choose "browse" from the drop down box, which led me to
the workgroup. I don't have a Windows server and have not
tweaked the registry.

Anyway, it's working like a charm now. Thanks for your
assistance.

Brian
 
Great! The name of the machine should also work--one place you can find
that is on the remote tab of properties of My Computer.
 
Back
Top