Remote desktop on another port

[doc]

Does anyone know of a way to successfully connect to a remote desktop if I've configured the server to connect on a different port?

For instance, on my laptop when connecting to my home computer by remote desktop I just use www.mydomain.com:3222 as the url where 3222 is the port I've told the server to use. If I try www.mydomain.com:3222 from a PPC it will not connect. As far as I can tell this is because the PPC client doesn't like the :3222 at the end.

[Dave Beauvais]

I never even tried the Web Connection feature before. Honestly, didn't know you could even do that. I've found that sometimes when specifying a port, you must type "http://" at the start of the URL. With standard ports you can often get away with leaving the protocol off.

This page (http://www.microsoft.com/windowsxp/expertzone/columns/russel/02January14.asp) may also help, but it sounds like you already know how to get it setup properly.

--Dave

[JonnoB]

If you are talking about the terminal services client... unfortunately the RDP client software on the Pocket PC does not support alternate ports :(

[Jason Dunn]

Does anyone know of a way to successfully connect to a remote desktop if I've configured the server to connect on a different port?

You're out of luck. :( Details here:

http://www.geek.com/news/geeknews/2003Aug/fea20030828021469.htm

[doc]

I'm not using the Web Connection, I'm just NAT'ing the port from my firewall/router. NAT just redirects the external port to a machine:port on my internal network.

Is there a 3rd party solution for RDP that supports the client connecting on a non standard port?

[Bandito]

Have you configured the actual RDP server itself to use a different port, or have you just configured a NAT device to listen on a different port for requests coming from outside your network? It's not clear from your post.

If you're using a NAT device (routing port 3222 external to port 3389 on your internal box) then you're probably out of luck.

If you've modified the RDP server itself (using a registry hack) to listen on port 3222, then you should be able to use your NAT device to listen on port 3389 external and route to port 3222 internal.

[doc]

If you're using a NAT device (routing port 3222 external to port 3389 on your internal box) then you're probably out of luck

Yup, that's what I'm doing.

So, the PPC OS is what's limiting the off port? And not the actual client? :roll:

Thanks for the replys.

[Bandito]

Well, it is the client that's restricting what port you can get to, but I'm not aware of another RDP client for Pocket PC. Theoretically you could get another client that wouldn't have that restriction.

You could always use VNC as well. There's a Pocket PC client available. I wouldn't say it's any better or worse than RDP, just has its own strengths and weaknesses.

[doc]

True, I've used VNC in the past. May have to try that again. Thanks.

[Sooner Al]

...is to run your TSC session through a VPN tunnel. That way you can access files/folders, ActiveSync and access one or more Remote Desktop sessions by simply opening one port on the firewall/NAT/router. All of the Remote Desktops need to be listening on TCP Port 3389 (the default)... See my VPN page to see this illustrated...

Al's PPTP VPN How-I-Did-That (http://www.oecadvantage.net/ajarvi/PpcVPN.html) page...

Note that the VNC data stream is NOT ENCRYPTED so that may be a concern to you over the public internet. VNC works equally well through a VPN tunnel and solves the encryption issue as well...

[Jason Dunn]

So, the PPC OS is what's limiting the off port? And not the actual client?:roll:

Correct - that's why I gave you my article URL. ;-) The Pocket PC is hard-coded to port 3389. You can add another port at the end of the IP string (:3381), but it seems to ignore it. :(