May 25, 2017 Remote Desktop for Mac OS X 10.8.5. Windows Server Remote Desktop clients.desktop-for-mac-os-x-1085 Question 3 5/18/2017 2:03:08 PM 5/25/2017 3:48:05 PM Discussions related to the use of Microsoft Remote Desktop Clients 0 1. Question; text/html 5/18/2017 2:03:08 PM joy mac. Version 6.0 client is available for Windows XP SP2, Windows Server 2003 SP1/SP2 (x86 and x64 editions) and Windows XP Professional x64 Edition. Microsoft Remote Desktop Connection Client for Macintosh OS X is also available with support for Intel and PowerPC Mac OS versions 10.4.9 and greater. Server 2012 can support RDC 6.0 or later.
- Mac Os X Windows Remote Desktop Client
- Mac Os X Remote Desktop Client
- Remote Desktop Connection Client 1.0.2 For Mac Os X 10 13 6 Or Later Required
- Remote Desktop Connection Client 1.0.2 For Mac Os X Mac
| Click here to return to the 'Connect to non-standard ports with MS Remote Desktop' hint |
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:
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.
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.
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.
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?
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!
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.
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.
... 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.
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.
Explicitly supporting something, and something actually working are two totally different things.
Microsoft Remote Desktop, a free application from Microsoft, allows you to use a Mac laptop or desktop to connect to and work from a Windows desktop computer that you have RDP access to in your on-campus office or lab. If you aren't sure whether you have RDP access to a certain machine, feel free to check with ECN via our Trouble Report System:
Put simply, Microsoft Remote Desktop from a laptop or a home computer makes it as if you're sitting at the desk in your office using your computer's keyboard and mouse -- even if you're two buildings, two miles, or two continents away.
By remotely accessing an ECN-supported desktop computer and refraining from storing your Purdue files locally on your laptop or home computer, your data remains safely stored in your home directory on ECN's network servers -- which receive daily backups.
-
If you have a Windows-based laptop or home computer, Microsoft provides Microsoft Remote Desktop for Windows 7, please see Remote Desktop Connection in Windows 7.The instruction on the page you're reading now focus on the MacOS version.
You'll want to follow these instructions on your Mac laptop and/or at-home Mac-- not on the on-campus desktop computer! Before you begin, download and install Microsoft Remote Desktop free via the App Store to your Mac.(Please note you'll need to be running 10.12.6 MacOS Sierra minimally, to run/download this application from the App Store).
When connecting from off-campus, please make sure to Purdue's VPN (www.webvpn.purdue.edu) first, as seen in step 1.
Who can use Microsoft Remote Desktop?
A remote-controlled computer can be used by only one person at a time. As such, this service is intended for use only by those who do not share the same office computer with other people. A graduate student may use Microsoft Remote Desktop with the permission of their supervisor.
Every ECN-supported Windows PC which will be used remotely must be pre-configured by ECN before this service will work. Please contact us in advance; we will provide you with the value that you'll need in step #3 as well.
Connecting to the Desktop Computer in Your Office
Mac Os X Windows Remote Desktop Client
1. Connect to Purdue's Virtual Private Network. When using a computer off-campus, this step is required. Establish a connection to Purdue's Virtual Private Network (https://webvpn.purdue.edu). For a description of this service, please see ITaP's VPN 'Getting Started' page.
2. Launch the Microsoft Remote Desktop application from your Applications folder. The appropriate icon can be seen below:
3. Once the application opens up, you'll need to add your specific machine to the 'My Desktops' list. To do so, click on New. A new dialog will appear. Fill it out as seen below-- making sure to substitute '128.46.xxx.yyy' with the actual IP address of your machine, 'username' for your Purdue Career Account user name, and 'Password' for your account password. Please note though that you will need to type either 'boilerad' or 'ecn'before your user name in order to successfully authenticate to your machine.
NOTE: If using the ECN RemoteAvailability website, please instead use the computer hostname INSTEAD of the IP. you can do this by appending .boilerad.purdue.edu to the selected PC name from a green box.
IMPORTANT
If your computername begins with x- you will use 'boilerad' prior to your username.
If your computername DOES NOT begin with x- you will use 'ecn' prior to your username.
Again, if you do not know your computer's IP, feel free to check with ECN via our Trouble Report System. Once you enter all of the necessary information, click the red circle in the top right corner of the dialog to close it out and save your configuration. You should now see 'Office PC' in your list under 'My Desktops.' Feel free to change the 'Connection name' of your configuration to anything you like. More specific names can be helpful when you need to set up connections to multiple machines on campus.
4. When you double click on your newly created RDP connection ('Office PC'), the following 'Verify Certificate' prompt may appear.
If it does, simply choose 'Continue.' Your Windows screen should then appear to you.
5. When you're ready to disconnect from your Windows machine, you may end the session in one of these ways:
- Click on the Start menu and select 'Disconnect.' This will end the remote session but leave files and programs open and running on your office PC.
- Click on the round red button at the top-left corner of the window. This will end the remote session but leave files and programs open and running on your office PC. If you do not see the Microsoft Remote Desktop application menu bar with the red button, simply hover your mouse at the top of your screen until it appears.
- Click on the Start menu and select 'Log off.' This will close all open files and programs on your office PC and also end the remote session.
Last modified: 2020/04/13 09:53:23.524808 GMT-4 by jerry.j.rubright.1
Created: 2008/07/31 10:21:59.307000 GMT-4 by john.a.omalley.1.
Categories
- Knowledge Base > OS > Mac > OS X
- Knowledge Base > ECN > RDP
- Knowledge Base > Software > RemoteDesktop
- Knowledge Base > OS > Mac
Mac Os X Remote Desktop Client
Search
Remote Desktop Connection Client 1.0.2 For Mac Os X 10 13 6 Or Later Required
Type in a few keywords describing what information you are looking for in the text box below.
Remote Desktop Connection Client 1.0.2 For Mac Os X Mac