RDC to XP pro from Vista HP

[Marcus]

Greetings,

OFFICE PC: XP Pro, RDC enabled, User has password, port 3389 open, Firewall
exceptions include RDC

HOME PC: Vista HP, pings PUBLIC IP address of OFFICE PC successfully, but
attempts to connect to PUBLIC IP address generate error as follows:

This computer can't connect to the remote computer. Try connecting again. If
the problem continues, contact the owner of the remote computer or your
network administrator.

ISP is clueless (but I noted that they, too, were attempting RDC to OFFICE
PC on Vista machines...for what it's worth).

Furthermore, attempts to connect from HOME PC via RDC to a Terminal Server
(running Server 2008 on altogether different network, i.e. not on OFFICE PC's
network) are always successful.

Any help would be greatly appreciated.

 

[Bob Lin \(MS-MVP\)]

Port 3389 may be blocked or doesn't forward to the office PC. Can you telnet
port 3389?

--
Bob Lin, Microsoft-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com

 

[Marcus]

Thank you for your reply.

You pose a great question. My attempts to telnet the public IP address from
the HOME PC resulted in requests for name and passsword, which I take as a
good sign; but my ISP doesn't provide that information to me.

So I had them do it. They say that telnetting the IP address and port 3389
is successful, claiming that it "shows in the net translation table."

I hope this answers your question.

 

[Bob Lin \(MS-MVP\)]

This could be the problem: "My attempts to telnet the public IP address from
the HOME PC resulted in requests for name and password". First of all, have
you enable telnet in the Vista? By default, telnet is disabled in Vista.

If some one can telnet port 3389, but your pc, I would double check your
computer firewall.

--
Bob Lin, Microsoft-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com

Thank you for your reply.

You pose a great question. My attempts to telnet the public IP address
from
the HOME PC resulted in requests for name and passsword, which I take as a
good sign; but my ISP doesn't provide that information to me.

So I had them do it. They say that telnetting the IP address and port 3389
is successful, claiming that it "shows in the net translation table."

I hope this answers your question.

 

[Marcus]

I am fairly certain I enabled telnet through Add/Remove Windows Components
(which, as I am sure you know, is an altogether different problem for a
different community/forum). Before telnet was enabled I got the

'telnet' is not recognized as an internal or external command, operable
program or batch file.

error message. Since enabling, I now get prompted for name and password. I
could be mistaken, but that's why I assumed telnet was working (but had to
abandon it as my ISP doesn't give me their router's name and password).

You bring up yet another good point. Having recently inherited this
computer, I hadn't thought about the possibility of added security software
(a Norton, say, or McAfee) on the system. I will see about that. Thanks

 

[Marcus]

MS Firewall has remote desktop as an exception and McAfee's firewall is
configured to allow remote desktop. Despite this, I tried to connect with
both disabled. No dice.

 

[Marcus]

MS Firewall has remote desktop as an exception and McAfee's firewall is
configured to allow remote desktop. Despite this, I tried to connect with
both disabled. No dice.

 

[Marcus]

Any other clues on this issue? I've noticed that when it comes to remote
desktop not working, one tends to get a lot of "no brainer" suggestions (i.e.
"did you configure remote desktop?", "does the user have a password?", "is
your computer turned on?", etc.) before being ignored. If you people have no
idea why this doesn't work, just say so.
--
Marcus

MS Firewall has remote desktop as an exception and McAfee's firewall is
configured to allow remote desktop. Despite this, I tried to connect with
both disabled. No dice.

 

[Shenan Stanley]

<snipped>

<entire conversation>
http://groups.google.com/group/micr...k_remotely/browse_frm/thread/e535f8293418f54f
</entire conversation>

Any other clues on this issue? I've noticed that when it comes to
remote desktop not working, one tends to get a lot of "no brainer"
suggestions (i.e. "did you configure remote desktop?", "does the
user have a password?", "is your computer turned on?", etc.) before
being ignored. If you people have no idea why this doesn't work,
just say so.

Peer-to-peer newsgroup. No one here owes anyone any effort or lack of
effort for anything. ;-)

I wouldn't throw out an attitude and expect assistance though.

The local software firewall is usually not the only obstacle - routers/NAT
devices/port forwarding on said devices may also be necessary. It's also
entirely possible that either machine has corrupt files of some sort.

I'd install the latest Remote Desktop Client and apply the registry fixes to
the Windows XP machine for CredSSP. I know that is the one you are
supposedly trying to get *to*, but let's just put everything into play here
and replace parts as we can.

I'd install the same updated client on the Vista machine, the CredSSP is not
necessary (it's a radio box in Vista.)

Remote Desktop Connection 7.0 client update (both)
http://support.microsoft.com/kb/969084

CredSSP for Windows XP
http://support.microsoft.com/kb/951608/
( How to turn on CredSSP )

I'd run a FULL scan with MalwareBytes on both machines.

I'd verify that when on the same network as the Vista PC - one can use
remote desktop to get to it. This is where one determines if it is behind a
NAT device or not (if it is, it will likely have a private IP like
192.168.x.x or 10.10.x.x...) and will need to figure out how to forward port
3389 to the devices' private IP address (which hopefully is static, but is
probably not.)

I'd probably install the full version of TeamViewer on the Vista computer
and the Host version of Teamviewer on the XP computer and try using
TeamViewer to get to the XP machine from the Vista machine. If that works,
it is either a firewall, port forward or software misconfiguration issue -
and one could either try to figure it out or just keep using TeamViewer.
The advantage of having teamviewer now - if one wants to solve the RDC
issue - is that one person can do it from the Vista machine - making changes
and rebooting the XP machine remotely as needed, managing any routers the XP
machine is connected to from it, etc.