Benches macOS

3

Remote AFP Access

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

I have a Mac OS X 10.6.3 Server. I am able to mount AFP shares locally but would like to access them when I'm at a remote location.

I have allowed File Sharing in the Security area in Server Preferences, but can not mount the AFP shares over the Internet. I can still SSH into the server just fine.

Am I missing a step here?

3 replies

Sign in or join Beachball Help to reply.

  1. 0

    Camelot

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Am I missing a step here?

    Yes. AFP uses a different port number - port 548 - so you'll need to make sure you've setup port forwarding in your router so that external connections to port 548 can get to your server.

    That is, of course, one approach. Another would be to setup a SSH tunnel on your existing SSH configuration, which adds the benefit of encrypting the AFP connection.

    A third option would be to setup a VPN, which gives unfettered, secure access to the network, including other protocols you might want to access.

    Port forwarding is the easy option, though. You already did that for SSH (port 22) so just replicate that setup for AFP (548).

  2. 0

    dmason

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I was under the impression that adding File Sharing to the Security area in the Server Preferences are forwarded the ports by accessing the AirPort Extreme. It's how I setup SSH and VPN forwarding. Am I better off using the AirPort Utility for forwarding ports and such?

  3. 0

    MrHoffman

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    If you have VPN and ssh lit and working, you don't need anything else; you should be able to tunnel in and have access to your disks because (with the VPN) you're on the same network.

    And as for your question, yes; use the Airport Utility. And Server Preferences is not my preference; I've found it somewhat buggy. Server Admin is more complex, but tends to be more reliable.

    And as for the question you haven't gotten to, no, Airport port forwarding isn't entirely reliable with some VPNs; L2TP doesn't work right with various recent firmware releases.

    And ... yes, a firewall-based VPN server is an easy solution, because Airport really isn't a good firewall for servers; they're good home devices, but they're not really intended for servers.

    Oh, and a common problem with VPNs is the use of 192.168.1.1 or such; of the same IP subnet blocks within the same 192.168.0.0/16 block. Get your servers out of this block, and move to either the 172.16.0.0/12 or 10.0.0.0/8 block. That avoids VPN subnet routing restrictions as every coffee shop and every home network on the planet is in 192.168.0.0/16 and that means VPNs won't work when you're in the same subnet or 192.168.0.0/16.