This guide provides instructions for using the UMD ARD+ macOS app, which makes use of the Campus SSH jumpbox to view (Screen Sharing) or to SFTP (SSH FTP) onto another macOS computer on campus. This resource is designed for use on the Policy Driven Network to enable SSH access to other macOS resources. Please read these instructions carefully to ensure proper usage and avoid connectivity issues.

If you need assistance, please contact it-desktop@umd.edu

Prerequisites

• Request access to campus jumpbox.
• A wired connection is recommended.
• You have previously logged in with your UMD directory ID to the target computer
• Your local IT Administrator has turned on Screen Sharing, Remote Login, and set the account access permissions accordingly.
• Recommended: FileZilla for a third-party SFTP.
• macOS 14.6 and latest

Note: The Mac computer needs to be in a state where it has been logged in past the FileVault login screen. FileVault login screen does not allow network connections in general.

Download the UMD ARD+

Via IT-Self Support

1. On your Jamf-managed macOS computer, open IT Self-Support application.
2. On the Search field, search for UMD ARD+.
3. Click Install.
   
4. The app will reside in your Applications folder.

Download FileZilla 

1. On your Jamf-managed macOS computer, open IT Self-Support application.
2. On the Search field, search for FileZilla.
   
   
   
3. Click Install.
4. The app will reside in your Applications folder.
5. One-time setup: Go to your Applications folder and open FileZilla. It will prompt you to which folder you want the FileZilla to have access to for transferring files from your computer to the other macOS computer. Feel free to select a folder you want so that FileZilla defaults to navigate your computer to that folder (Documents, Desktop, Downloads, etc.)

Top

Use UMD ARD+

1. Connect to GlobalProtect vpn.
2. Go to your Applications folder and open UMD ARD+
3. When you open the app, you will be presented with 2 options:
   • ARD Connector - This is to view the screen of another macOS computer.
   • SFTP Connector - This is to SSH-SFTP to another macOS computer.
     

ARD connector

1. On the DirectorID field, type in your directoryID (with or without @umd.edu).
2. On Target Host, click the box and select [Enter new target hostname].
3. A new target hostname field will appear, and then input your target hostname.
4. Click Connect.
5. Type in your directoryID credentials and click Connect again.
6. The built-in Screen Sharing app will automatically open.
7. On the screen sharing app, type in your credentials again to begin viewing the screen of the other computer. Click the Remember password then click Sign in.
   
   Note: You have to make sure your directoryID credentials have the same password when you login to your target hostname.
   

SFTP connector with FileZilla

1. On the DirectorID field, type in your directoryID (with or without @umd.edu)
2. On Target Host, click the box to select [Enter new target hostname]
3. Below it will appear a box to input your target hostname.
4. Click Connect.
5. Type in your directoryID credentials and click Connect again.
6. [Using FileZilla available to download from IT Self-Support] Under the Port Forwards: click Open in FileZilla.
   
7. Input your directoryID password again then click OK.
   
8. FileZilla is now connected to the other macOS via SFTP connection.

Fetch.app SFTP Client

Fetch is available to download from Terpware.

1. Follow the SFTP Connector steps 1 to 5.
2. On the SFTP Connector window, under Active SSH-SFTP Connections, the target hostname, localhost and port number are listed. Note this down.
3. On Fetch.app window, input the following:
   • Hostname: localhost
   • Username: your directoryID username to SFTP
   • Connect using: SFTP
   • Password: your directoryID password to SFTP
   • Click Add to keychain.
   • Click the drop-down arrow.
   • Port: 49153 (this is the port that shows up on step 2)
4. Click OK to start sftp connection.
   

Top

Turn on Screen Sharing on your Mac

1. On your target host Mac computer, click and select System Settings.
2. Click  in the sidebar, then click Sharing. You may need to scroll down.
3. If Remote Management is turned on, turn it off. If you are already using Remote Management and have set the permissions, you can skip these steps and use the ARD Connector.
   
   Note: You can't have both Screen Sharing and Remote Management on at the same time.
   
   
4. Click next to Screen Sharing.
5. Turn on Screen Sharing.
6. Click the Allow access for pop-up menu, then do the following:
   • Choose who can share your computer’s screen: Click the pop-up menu next to Allow access for, choose Only these users, and click the plus button at the bottom of the list, select allowed users, then click Select.
   • If you don't see a user you want to allow access for, that means the user has not logged in before to the machine or is hidden. By default, Administrators have access.
7. Click Done.

Reference: Mac User Guide

Turn on Remote Login on your Mac

1. On your target host Mac computer, click and select System Settings,
2. Click  in the sidebar, then click Sharing. You may need to scroll down.
3. Click next to Remote Login.
4. Turn on Remote Login.
5. If you want remote users to have full access to the disk on your Mac, turn on Allow full disk access for remote users.
6. Click the Allow access for pop-up menu, then do the following:
   • Choose who can log in to your computer: Click the pop-up menu next to Allow access for, choose Only these users,” click the plus button  at the bottom of the list, select users who can log in remotely, then click Select
   • If you don’t see a user you want to allow access for, that means the user has not logged in before to the machine or is hidden. By default, Administrators have access.
7. Click Done.

Known application bugs

1. Password error handling. The app doesn't have a clear error handling mechanism if the user's password is incorrect.
2. Offline error handling. The app doesn't have a clear error handling mechanism if the campus jumpbox is offline, the target hostname is offline, or the target hostname ssh or VNC permissions are incorrect.

Top