Using Screens without Screens Connect

Screens Connect is the easiest way to make a computer available for connections from outside its local network, but under certain circumstances, Screens Connect isn't a viable option. In such cases, it's still possible to connect to a computer from across the Internet.

Note: Make sure you enable Screen Sharing on your Mac before you go through these instructions. Refer to Screens' help documentation to learn more.

Step 1: Update your public IP address automatically

Your public IP address will change from time to time. To make sure that Screens can find your computer when connecting locally, you will need to subscribe to a service that will monitor IP address changes.

For this example, we chose a free service called No-IP, which is not associated in any way with Edovia. There are many similar services available on the web and they all have a similar setup procedure.

Create a No-IP account and host

  1. Go to
  2. Select “No-IP Free”.
  3. Sign Up for the service.
  4. Once your No-IP account has been created and validated, go to to log in.
  5. You'll land on your No-IP page.
  6. Select “Add a Host”.
  7. Type a Hostname. 
  8. Make sure “DNS Host (A)” is selected.
  9. Do not change the IP address. It is your current public IP address.
  10. Click on “Create Host”.

Install the Host Updater

Many routers will let you do this easily, without having to install any additional software on your Mac. Consult this page to see if your router supports the No-IP service.

If your router doesn't support the service, follow these instructions:

  1. Go to
  2. Select the download for your OS (Mac, Windows or Linux).
  3. Download the latest version of the app.
  4. Scroll down the Download page in order to get the installation instructions.

Step 2: Make your Mac's local IP address static

Like your public IP address, your local IP address may change from time to time. We need to make sure it stays the same.

  1. Open System Preferences → Network.
  2. Select “Using DHCP with manual address”.
  3. Select a static IP that will not conflict with anything else on the network. It’s best to pick a number far out of the normal range of assigned IP’s, in the example below we chose because most of the machines on this network stop at Check your router's IP address to know which range to use. 
  4. Click on the “Apply” button in the lower right corner.
  5. Your IP will now manually set to the static address you provided, you will briefly disconnect from the network while this occurs.
  6. Close Network settings and System Preferences.

Step 3: Port-Forwarding

As your network requires a public IP address, you will also need to create public ports that will redirect to your new static IP address and the private port used by Screen Sharing (normally 5900 unless you have changed it).

For the sake of this example, we'll use an Airport Extreme. If you have a different router, we suggest that your consult the excellent Port Forward website. Select your router brand and model, and then select “VNC” on the next page.

  1. Open “Airport Utility”.
  2. Select your router if it's not already selected.
  3. Click “Manual Setup” and enter your administrative password.
  4. Click the “Advanced” tab, then the “Port Mapping” tab.
  5. Click the + button to add a new port mapping.
  6. A settings window will appear.
  7. Select “Apple Remote Desktop” in the Service list.
  8. In the “Private IP Address” field, enter the static IP address you've created in Step 2. 
  9. Click “Continue”, then “Done”.
  10. Click “Update” to apply the changes on your router.

Step 4: Setting up Screens

  1. Open Screens and create or edit a screen like you would normally do.
  2. In the Address field, type your No-IP host. In our case, it's “”.
  3. Set the Port field to 5900 or whatever port number you used in Step 3.
  4. Select the correct Operating System, Authentication method and credentials.
  5. Save.
  6. Select the screen to initiate a connection.


Was this article helpful?
0 out of 1 found this helpful
Have more questions? Submit a request


Article is closed for comments.
Powered by Zendesk