Can't connect using Remote Desktop

Intel / To be filled by o.e.m.
June 23, 2009 at 13:16:25
Specs: Microsoft Windows XP Professional, 1.699 GHz / 510 MB
I'm using cable internet and my friend has DSL. He can access my computer over the Internet using remote desktop, but when I try to access his desktop remotely, I can't. It doesn't work even when the firewall on his computer is off. We've checked all the settings and didn't find a problem.
I would really appreciate some help.

See More: Cant connect using Remote Desktop

Report •


#1
June 23, 2009 at 13:24:10
Is he running XP Home? Home doesn't have remote desktop those according to google there is a work around.

Report •

#2
June 23, 2009 at 13:28:37
It might be the way his or your router is configured.

"Best Practices", Event viewer, host file, perfmon, antivirus, anti-spyware, Live CD's, backups, are in my top 10


Report •

#3
June 23, 2009 at 14:44:26
Is he running XP Home? Home doesn't have remote desktop those according to google there is a work around.

I mentioned he can access my computer using remote desktop, which means he's using XP pro.

It might be the way his or your router is configured.

Neither of us is using a router. I'm using a cable modem and he's behind a DSL modem. One thing that is different is when I type ipconfig in my command prompt, I see my public IP address, whereas his ipconfig output shows him a private IP address. He needs to go to the Internet(e.g. whatismyip.com) to find his public IP address.


Report •

Related Solutions

#4
June 23, 2009 at 14:49:56
"I mentioned he can access my computer using remote desktop, which means he's using XP pro."

Sorry that is an incorrect assumption. Xp home can connect to but can't be connected to which mean he can access you but you can't access him.

Confirm he has xp pro AND has enabled remote desktop access.

If he has Home, solution is to use tightVNC


Report •

#5
June 23, 2009 at 14:58:25
Yes he has XP pro and has remote desktop enabled.

Report •

#6
June 23, 2009 at 15:14:09
have him go to shields up! and test for port 3398 to see if it is open or not.

Report •

#7
June 23, 2009 at 16:16:38
"but when I try to access his desktop remotely, I can't". So, what happens? And which IP are you trying to access? Do you receive any errors? If so, what? What settings have you checked?

LIR


Report •

#8
June 24, 2009 at 15:00:14
whereas his ipconfig output shows him a private IP address.

As above,

Could just go to Acrobat.com and use it. Seems to work on hardened systems.

"Best Practices", Event viewer, host file, perfmon, antivirus, anti-spyware, Live CD's, backups, are in my top 10


Report •

#9
June 25, 2009 at 05:53:20
Thanks to all of you for trying to help!

upstandingnetizen:
"This suggests his DSL modem is also a router, or he is somehow otherwise behind a router. If his computer has a private IP address, something (port forwarding) must be done to bridge the connection between his public IP and private IP."

His PC connects to just one device (It's not like PC - Router - Modem), so the device is a modem cum router as you rightly pointed out. The make is Shiro.
How to configure port forwarding?

wanderer:
"have him go to shields up! and test for port 3398 to see if it is open or not."

You mean 3389 right? It is open as the option "Allow users to connect remotely to this computer." is checked in the properties. And just to confirm, he had it checked with Shields Up as well - it's open.

Jennifer SUMN:
"And which IP are you trying to access? Do you receive any errors?"

I'm trying yo access his public IP address, obviously not the private. This is the error I get: "This computer can't connect to the remote computer."

jefro:
"Could just go to Acrobat.com and use it. Seems to work on hardened systems."

Didn't get that - mind elaborating?


Report •

#10
June 25, 2009 at 08:07:28
Yep 3389. Port is open so that ends the discussion of forwarding since it's not required.

He can get his currect public ip from whatsmyip.com

Perhaps his local firewall is blocking access.

If remote desktop continues not to work you may want to try tightvnc instead to see if you get different results.


Report •


Ask Question