How To Make My OS X Server Be Accessible Out Of My Local Network.

The simplest way to access your OS X server from a remote location is to use Back to My Mac. Otherwise you will need a combination of using DDNS & port mapping to make it possible.

Please take a look at the following AirPort User tip for additional details. Note: This tip was designed to address accessing an AirPort Disk remotely, but there is some similarity to accessing your server as well. The key is what services on the Server do you want to access.

If you don't have an iCloud account or don't want to use Back to My Mac, then set up will be more involved based on the type of Internet service that you have. By that, I mean does your ISP provide you with a dynamic or static Public IP address.

Ok, I will try to assist you where I can.

Did you take care of acquiring a DDNS account?

Is the server connected to the Extreme or the Cisco router? If the Extreme, is the Extreme connected to the Cisco by Ethernet? Is the Extreme also reconfigured as a bridge?

What services on the server do you want to access from a remote location?

If your goal is to access these services remotely for just yourself, then the combination of DDNS and the proper ports to be mapped should be all you need.

However, if you goal is host a website, wiki site, etc., then you need to discuss this with your ISP for, at least, two reasons: 1) Are they providing you with enough upload bandwidth to support the number of users attempting to access your services, and 2) Replacing your dynamically-provided Public IP address with a dedicated static one. Actually a third one would be do they allow what you are doing with their consumer-grade level of service.

Since your Cisco router is providing NAT service, it is the device that you will need to set ports on. Cisco, like most non-Apple routers, uses a web-based administration interface.

You would need to use a web-browser to access the Cisco router, and then, access the appropriate page where you would enter port mappings. Each service you need to access will require certain ports to be opened. To get an idea of which ones, check out this link.

Basically to map a port, you need to identify at least the following items:

• The IP address of your server. This should be a local static IP address.
• The TCP port(s) on the server that the service requires.
• The UDP port(s) on the server that the service requires.
• The TCP port on the router that you want it mapped to.
• The UDP port on the router that you want it mapped to.

Again, to give you an idea on how to do this with an Apple router, check out this AirPort User Tip. It WILL be different for the Cisco.

As an example, we will open TCP port 80 for web-based traffic. Our example server is located at: 192.168.1.100

On the port mapping page, you would enter the IP address of the server in the IP Address field. In the Private TCP port field you would enter the value: 80. In the Public TCP port field you would enter something like: 8080.

What you have done here is traffic coming from the Internet will enter port 8080 on the router, and then, be sent to port 80 on the server. Folks would enter something like: http://<your router's WAN IP address>:8080. Note: If you have a dynamic Public IP address, this is where you want to use a DDNS-provided URL as you IP address will change over time and remote users will not be able to access it.

If this all seems like a daunting task, I would suggest that you hire a professional to help you set up your server. Again, your ISP should be supportive or that will be your first roadblock in running a server.