Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Connect to non-standard ports with MS Remote Desktop Apps
If you have ever worked in an environment with multiple Windows servers to manage, you know how useful Microsoft's Remote Desktop, aka Terminal Server client, is. In a situation where you have to access a NAT-ed, remote site with multiple servers, having servers listen on ports other than the default (3389) is quite handy.

Unfortunately, Microsoft claims that "the Remote Desktop Connection Client for the Mac supports only port 3389. 3389 is the default port." I was frustrated with this until recently, when on a whim, I entered the port number preceded by a colon immediately after the IP address of the remote site (e.g., 10.10.10.10:3380). Voila! I can now access all of the servers, regardless of their port, using my Mac.
    •    
  • Currently 3.33 / 5
  • 1
  • 2
  • 3
  • 4
  • 5
  (3 votes cast)
 
[18,257 views]  

Connect to non-standard ports with MS Remote Desktop | 12 comments | Create New Account
Click here to return to the 'Connect to non-standard ports with MS Remote Desktop' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Connect to non-standard ports with MS Remote Desktop
Authored by: lullabud on Oct 14, '04 12:29:54PM
Amazing, I had no idea that MS claimed to not support this function. I've been using it for a loooong time and mkutny is absolutely right, it is VERY handy. My room mates and I all use Mac laptops and Windows XP desktops, and this makes it possible for us all to connect to our home systems while at work or on the road.

For those who don't know, the Microsoft Knowledgebase article #187623 shows how to change the port number on the Windows side of things.

The gist of it is to change the PortNumber key in the registry at:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp


[ Reply to This | # ]
You Can Use Multiple Instances of RDC Too
Authored by: olivermomo on Oct 14, '04 04:07:32PM

We've also found that you can duplicate the RDC app (even when it is running!) and run several copies at the same time in order to connect to several machines at the same time.



[ Reply to This | # ]
You Can Use Multiple Instances of RDC Too
Authored by: smanzo on Oct 15, '04 08:44:58PM

Must you be using multiple target port numbers for this to work? I can't STAND the single RDC connection that i have to deal with right now, as I admin a few MS 200x servers, and find I need to hop between them often.



[ Reply to This | # ]
You Can Use Multiple Instances of RDC Too
Authored by: olivermomo on Oct 19, '04 11:53:21PM

No, you can connect to more than one target machines, all of which use the standard port 3389. Or, you can create multiple connections to the same machine, all using port 3389.



[ Reply to This | # ]
Connect to non-standard ports with MS Remote Desktop
Authored by: sfederman on Oct 14, '04 05:26:55PM
This is documented within Remote Desktop Connection 1.03 at (assuming it's installed in the standard location in your /Applications folder):

file:///Applications/Remote%20Desktop%20Connection/RDC%20Help/Help%20Files/SpecifyNetworkPort.htm

[ Reply to This | # ]

Connect to non-standard ports with MS Remote Desktop
Authored by: watersb on Oct 14, '04 06:32:56PM

I am a somewhat experienced Windows and Macintosh admin.I have never been able to get Remote Desktop Client to work.

The client on the Macintosh takes a very very long time, thinking about the connection, then gives up. The Windows XP Pro machine claims to be allowing Remote Desktop users, and the network connection claims to have a firewall rule set to allow connections on port 3389. I added a rule for port 3389 to my Macintosh firewall via the System Settings:Sharing Preference Pane. Still no luck.

What am I missing here?



[ Reply to This | # ]
Connect to non-standard ports with MS Remote Desktop
Authored by: watersb on Oct 14, '04 06:35:01PM

I can ping both ways between machines, also SSH works between the Windows and Mac: they see each other's TCP network services. But no Remote Desktop!



[ Reply to This | # ]
Connect to non-standard ports with MS Remote Desktop
Authored by: carlost on Oct 14, '04 09:15:14PM

Are you sure you've enabled (or ublocked the port in the firewall settings) Remote Desktop? If you are trying to connect to W2K Server then make sure Terminal services are installed as well.

HTH

CJ

---
To mess up an OS X box, you need to work at it; to mess up your Windows box, you just need to work on it.



[ Reply to This | # ]
Connect to non-standard ports with MS Remote Desktop
Authored by: rhithyn on Oct 14, '04 10:56:10PM

I was having a similar problem until I realized that Zone Alarm was not allowing the connections... now I'm used to being prompted with Zone Alarm, but it was refusing to prompt on requested connections or even when I tried to force it locally... Only after disabling zone alarm was I able to restore the connection functionality. Strange indeed.

Another thing I noticed is you can specify exceptions for specific network interfaces (assuming you have more than one). You may want to make sure that the interface you have connected to the 'net is also marked to exclude 3389 from it's firewall filtering.



[ Reply to This | # ]
Comcast, ...
Authored by: jimhoyt on Oct 15, '04 07:41:23PM

... bless their icy little heart, block port 3389 to "protect us." No amount of pleading, cajoling or screaming will get it unblocked.

My kids live in another state and use PCs. Maybe this hint will finally get our machines to talk.



[ Reply to This | # ]
Connect to non-standard ports with MS Remote Desktop
Authored by: legacyb4 on Oct 15, '04 09:46:02PM

Microsoft is full of it, as usual.

For quite a while now, RDC has supported non-standard port calls which allows you to port forward to any number of Windows machines through a Linux box using SSH.

Simply set up your SSH tunnels with:

-L 13389:192.168.1.1:3389 (to machine 1)
-L 23389:192.168.1.2:3389 (to machine 2)
etc.

run multiple copies of RDC and connection to:

127.0.0.1:13389 (to machine 1)
127.0.0.1:23389 (to machine 2)
etc.

for as many connections that your bandwidth can support.



[ Reply to This | # ]
Connect to non-standard ports with MS Remote Desktop
Authored by: raven42rac on Oct 18, '04 08:58:37AM

Explicitly supporting something, and something actually working are two totally different things.



[ Reply to This | # ]