Access your [powered-on] work computer from home to use its programs and files.
Operating system: Macintosh 10.12+ [home computer] to Windows 7+ [work computer]
Processor: 64-bit
Getting ready
- Contact your IT support to configure your University computer for remote desktop connectivity.
- Make sure your university computer is on and locked before you leave. If your workstation computer is off, you will not be able to remote into it.
Set up your home Mac [first time only]
1. On your home Mac, download the free Microsoft Remote Desktop 10 from the Mac App Store
- Follow the onscreen prompts to install and open the program [you will need to sign in with your Apple ID]
- If you would like to use your microphone and camera, click OK
2. Click the Microsoft Remote Desktop Menu [top left of your screen] and then select Preferences
3. Click the Gateways tab
4. Click + in the bottom left corner
5. Fill in the fields as follows:
- Gateway Name: ubremote.buffalo.edu
- Friendly name: UB Gateway
- User Account: Use PC User Account
6. Click Add and close the Preferences window:
Add the connection information [first time only]
1. Have your default Duo-enabled device close by to verify you login during the last step
2. Add the connection:
- Click the Connections menu [upper left] and then select Add PC:
- Fill in the fields as follows: PC name: [enter the name of the computer you're connecting to]
User Account: Ask when required
- Click General [if you don't see General, click Show More], fill in the fields as follows:
Friendly Name: MyUB PC [or whatever name you like]
Gateway: UB Gateway - Uncheck Bypass for local addresses
- Click Devices & Audio [if you don't see Devices & Audio, click Show More]
- Check Microphone and click Add:
Remote into your UB computer
1. From the main Microsoft Remote Desktop 10 window, double click on the new connection you just created [the "Friendly Name" you gave will be shown; we used MyUB PC in the example above]
2. A window will open showing Connecting ... [it may take several moments to connect]
3. If prompted to log in, use the following:
- Username: ad.buffalo.edu\{YourUBITName}
- Password: {Your UBITName password}
4. Since RD Gateway requires two-factor authentication, you must approve login from your default Duo-enabled device. The Mac screen will not prompt you – Please check your default Duo device.
Page content loaded
In response to rcook349
It's more likely that its the Mac's fault than that the remote server is refusing you. It's probably something to do with a failure to establish an encrypted connection to the Server.
I'd recommend using Microsoft Remote Desktop. It's a free app in the app store for OS X and iOS devices and connects flawlessly to PCs from Apple devices.
Jan 12, 2015 11:05 AM
Reply Helpful [8]
Thread reply - more options
In response to jaredfs
I am using Microsoft's Remote Desktop Connection for Mac. Like I said, on Windows machine [using RDC for Win] success. On Mac [using RDC for Mac] failure.
Jan 12, 2015 11:41 AM
Reply Helpful [7]
Thread reply - more options
In response to rcook349
Did this ever get resolved? I'm having the SAME EXACT problem. Using, Microsoft Remote Desktop... I can't connect remotely on my Mac... but I can connect without issue using the Windows version.
Jan 21, 2015 10:10 AM
Reply Helpful [5]
Thread reply - more options
In response to rcook349
I doubt this a 'problem' with the mac as such nor does it have anything to do with Remote Desktop for Mac which is an entirely different product and for which this forum is for. Questions about RDC for Mac should be put on the relevant Microsoft forum rather than here. However your problem may be with your understanding of the secure remote connections requirements between your server and remote connections. I doubt you'd be aware of any of this as generally server administrators won't necessarily discuss them. By default a mac will not have server-client trust certificates installed simply because the exchange won't happen transparently between an MS based server and non MS-OS such as OS X.
You begin to solve the problem by asking your server administrator for the server's root certificate. He/she has to export this using the built-in tools. They should know how to do this? Once exported save it to a memory stick, insert it into your mac, double click on the .cer file and when prompted install it as a system keychain. On further prompts make sure you select 'Always Trust'. Launch RDC for Mac and you should be OK?
If your server administrator does not know how or, worse still, won't do this for you, then you have far deeper problems that go well beyond OS X in particular and IT as a whole in general.
Jan 26, 2015 5:05 AM
Reply Helpful [3]
Thread reply - more options
In response to rcook349
Did anybody figure this out? It used to work perfectly before until I installed the latest Windows 10 build.
Other Windows computers can still connect. I'm just having this issue on my MacBook using Microsoft's Remote Desktop app.
Thanks
Feb 9, 2015 5:11 PM
Reply Helpful [4]
Thread reply - more options
In response to JohnnyG76
Hi,
I have the exact same problem.
After update the Windows10 for the latest build [10049] i have this problem too.
Before the update everything works great. With Ms RDP app for Osx and with RoyalTS X.
Now none of them work.
The problem is with this update, because i have another machine that i have not updated and works fine
Apr 10, 2015 5:07 AM
Reply Helpful
Thread reply - more options
In response to jaredfs
Thanks jaredfs. Im running Mac OS X Yosemite and just upgraded to Win10. I used to use the Remote Desktop Connection App but after the upgrade to Win10, I couldnt connect from my Mac. I installed Microsoft Remote Desktop and now I can connect to my Win 10 machine with no issues. Thanks for the quick fix!
Aug 5, 2015 6:58 PM
Reply Helpful [6]
Thread reply - more options
In response to _GeeBe
i have been fighting this since first installing windows 10 on one of my test systems....i FINALY have the solution.
So i HAVE been using CORD to log into my PCs from OSX. But it was not working on the Win10 box. I was in the insiders Beta program. and after some update CORD finaly started working. Well as said above, that was short lived with the next update CORD stopped working again. I can remote desktop in from a PC but not from CORD on my Mac.
So following the advice above i downloaded MICROSOFTS's remote desktop. and as soon as i tried to remote into my Win10 box, a message come up about generating a security certificate for this user. I said Yes, and boom! remote desktop ed in perfectly!
Sadly CORD [my preferred client] is still NOT working, but now we know WHY! Win 10 looks for this "security certificate" and if it doesnt find it Win10 will REFUSE the connection. This must be a PC to PC handshake that we never see.
So for CORD we need to ether:
1. Disable this "security certificate" check in remote login [best solution]
2. Get CORD updated to deal with this "security certificate" [doubt this will happen]
Oct 23, 2015 8:43 AM
Reply Helpful
Thread reply - more options
In response to darshsen
This Orange remote desktop app from darshen's link worked. The original app that came with my microsoft install on Mac with Disk and Antenna icon didn't.
Nov 9, 2015 9:25 AM
Reply Helpful
Thread reply - more options
In response to rcook349
Have you tried turning Windows Firewall off completely - this worked for me.
Nov 9, 2015 11:37 PM
Reply Helpful [1]
Thread reply - more options
In response to darshsen
That's the ticket... if you check your version of remote desktop for mac it says it's up to date... you have to know that the new version of RDP for mac is called Microsoft Remote Desktop.... maddening!!
Use the link mentioned above
//itunes.apple.com/en/app/microsoft-remote-desktop/id715768417?mt=12
Nov 25, 2015 12:33 PM
Reply Helpful [1]
Thread reply - more options
In response to Ryan Duff
FRUSTRATING!!!!
So I did a inplace upgrade to Windows 10, from a Working window 7 system. CORD logged in PERFECTLY just as under Windows 7!
Now I need to play the difference game. What setting is WORKING on the newly upgraded box, that is not set on my original Windows 10 system.
All the setting for Remote Administration looks the same. All the firewalls are off.
Again the only lead I have is that Microsoft Remote Desktop app works on the original box, but not CORD. And i THINK this is due to a security certificate issue. Problem is I have not idea where to find that in Windows 10
Any new ideas?
Dec 28, 2015 10:02 AM
Reply Helpful
Thread reply - more options
In response to rcook349
I had the very same issue. But, as suggested by someone here, I downloaded Microsoft Remote Desktop from the Appstore and the connection went through instantly
Jan 13, 2016 9:49 PM
Reply Helpful [6]
Thread reply - more options