Remote Desktop Connection Issues

[Ensign]

I'm trying to use Remote Desktop Connection to connect to my home PC from work, but I'm having some problems.

I know, by default, that Remote Desktop Connection needs to use ports 3389 and port 80. I first tried setting the port to something other than 80, but I couldn't even use the Remote Desktop Web Connection to get the the first "Connect" screen.

Then, I changed back to the default of 80. I was able to get the first "Connect" screen, but I get the standard error of "VBScript: Remote Desktop Disconnected 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. Please try connecting later. If the problem continues to occur, contact your administrator. "

I'm guessing that port 3389 is maybe blocked from work. I tried changing the listening port per MS instructions and I changed it to 8080 (thinking this would be open at work), but I couldn't even get past the "Connect" screen from another PC at home.

What am I missing here? Can I safely tell which ports are allowed from work?

Thanks for any help you can provide!

 

[acemcmac]

Originally posted by: Ensign
I'm trying to use Remote Desktop Connection to connect to my home PC from work, but I'm having some problems.

I know, by default, that Remote Desktop Connection needs to use ports 3389 and port 80. I first tried setting the port to something other than 80, but I couldn't even use the Remote Desktop Web Connection to get the the first "Connect" screen.

Then, I changed back to the default of 80. I was able to get the first "Connect" screen, but I get the standard error of "VBScript: Remote Desktop Disconnected 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. Please try connecting later. If the problem continues to occur, contact your administrator. "

I'm guessing that port 3389 is maybe blocked from work. I tried changing the listening port per MS instructions and I changed it to 8080 (thinking this would be open at work), but I couldn't even get past the "Connect" screen from another PC at home.

What am I missing here? Can I safely tell which ports are allowed from work?

Thanks for any help you can provide!

It does not need port 80... just 3389. I think it needs both UDP 3389 and TCP 3389... not sure... try changing that and see if that helps.

 

[Ensign]

I don't know that I can differentiate between UDP and TCP on my Netgear WGR614 router. I'll have to check when I get home. I had 3389 forwarded though. Until I set my home PC to use port 80 for Remote Desktop and forwarded that port, I couldn't get to the "Connect" screen though. I believe it needs two ports (3389 and 80 by default) though.

Thx for the suggestion.

Originally posted by: acemcmac
It does not need port 80... just 3389. I think it needs both UDP 3389 and TCP 3389... not sure... try changing that and see if that helps.

 

[wkinney]

Also make sure if you have any software firewall on the computer, that 3389 is opened up on that (including norton AV, under internet worm protection settings).

also you might try setting the default port from 3389 to say 443 or 21 instead of 8080, as those two are more likely to be not blocked by your work firewall than 8080.

and port 80 is not used by remote desktop.

 

[Ensign]

No software firewall running on the PC. I disabled Norton AV internet worm protection.

I was basing port 80 on this article, which said, "By default, IIS is identified on your computer by the TCP port number 80." So, you guys are saying this isn't involved with Remote Desktop Connection? Also, it's weird that I couldn't get to the "Connect" screen until I used port 80 for IIS.

Thx again.

Originally posted by: wkinney
Also make sure if you have any software firewall on the computer, that 3389 is opened up on that (including norton AV, under internet worm protection settings).

also you might try setting the default port from 3389 to say 443 or 21 instead of 8080, as those two are more likely to be not blocked by your work firewall than 8080.

and port 80 is not used by remote desktop.

 

[wkinney]

That article is based on remote desktop web connection, which is just a utility that allows remote desktop via a web browser. You shouldn't need this if you have the remote desktop client (installed by default on XP, need to download it for 2000).

Most likely the reason you couldnt get the connect screen directly with remote desktop client is because your work firewall is blocking it, and not (obviously) the web client (80).
I would bet if you edited your registry to change from 3389 to 443 or 21, it would work. Remembering to change the router port number as well.

edit: the port you open it for only has to be TCP btw, not UDP.

 

[Ensign]

Ah! I should have clarified that I was using remote desktop web connection. If I use the remote desktop client, can I get away with not having IIS running? When I checked some standard ports through canyouseeme.org, all seemed to be blocked from work, but I can surf the web freely.

Sorry for my ignorance on this port stuff and remote control.

Thx again!

Originally posted by: wkinney
That article is based on remote desktop web connection, which is just a utility that allows remote desktop via a web browser. You shouldn't need this if you have the remote desktop client (installed by default on XP, need to download it for 2000).

Most likely the reason you couldnt get the connect screen directly with remote desktop client is because your work firewall is blocking it, and not (obviously) the web client (80).
I would bet if you edited your registry to change from 3389 to 443 or 21, it would work. Remembering to change the router port number as well.

edit: the port you open it for only has to be TCP btw, not UDP.

 

[JackMDS]

May be this can Help.

L=Microsoft - Remote Desktop in Windows XP.]http://www.microsoft.com/windowsxp/remotedesktop/[/L]

Link to: Set Up Remote Desktop Web Connection with Windows XP.

Link to: How to use remote Desktop Access in Windows XP.

And if you find it too complicated there is an Easy free alternative.

Link to: Ultr@VNC (Remote Control for your Network/Internet) - Installation, and Settings

:sun:

 

[wkinney]

yes, there is no need to run IIS to use remote desktop, it is only needed if you want to access it through the web.

the web version usually has slower response times that the standard client, so i would just use that.

if those ports are closed scanning from your works LAN, then they are most likely being blocked by your work firewall.

 

[Ensign]

UPDATE

By changing the listening port to 80, I was able to use the Remote Desktop client from work to connect to my home PC! I went ahead and uninstalled IIS, since I don't really have a need for it now.

Thx again for everyone's help!

 

[Ensign]

BTW, how unsafe is it having port 80 left open on my router? Thx again!

Originally posted by: Ensign
UPDATE

By changing the listening port to 80, I was able to use the Remote Desktop client from work to connect to my home PC! I went ahead and uninstalled IIS, since I don't really have a need for it now.

Thx again for everyone's help!

 

[wkinney]

safe. people would see that the port is open on your ip if they are scanning, probably try to use an assortment of IIS exploits, and move on.

unless there is some buffer overflow exploit out for remote desktop, you should be fine.

 

[JackMDS]

I guess that spending few 20 minutes in trying UltraVNC (or any other secure variant of VNC) is not an alternative (To reduce anxiety you can try it while leaving your current arrangement as is).

UltraVNC can be secures easily with Encryption and Password leaving only port 5800 open.

Much safer then leaving Port 80 open and Remote Desktop running.

:sun:

 

[Ensign]

I'm not opposed to using UltraVNC by any means. It's just that I'm not sure if that port will "work" from my work (no pun intended) or not. I guess I could test it out by trying Remote Desktop with port 5800.

Does Remote Desktop use encryption? I thought I had heard that it does.

Originally posted by: JackMDS
I guess that spending few 20 minutes in trying UltraVNC (or any other secure variant of VNC) is not an alternative (To reduce anxiety you can try it while leaving your current arrangement as is).

UltraVNC can be secures easily with Encryption and Password leaving only port 5800 open.

Much safer then leaving Port 80 open and Remote Desktop running.

:sun:

 

[wkinney]

remote desktop uses encryption

 

[wkinney]

Originally posted by: JackMDS
I guess that spending few 20 minutes in trying UltraVNC (or any other secure variant of VNC) is not an alternative (To reduce anxiety you can try it while leaving your current arrangement as is).

UltraVNC can be secures easily with Encryption and Password leaving only port 5800 open.

Much safer then leaving Port 80 open and Remote Desktop running.

:sun:

He did not use the default port of remote desktop b/c of a work firewall, he would have the same problem with ultravnc on 5800