OS X and OS X Server use TCP 49152 through 65535 as the ephemeral port range. Or acquire a firewall that can detect and sniff the ftp traffic and open (just) the port the data connection has chosen. Alternatively, you can get yourself a firewall that can trigger the port range when it receives ftp traffic, as that avoids having the range open and forwarded for any random remote access. To get ftp to work, you are required to open the entire ephemeral port range at your server firewall and any firewalls in front of it, or to open the ephemeral range on the client firewall and any firewalls in front of that, as the second (data) connection used by ftp chooses a port from that port range. Open and forward TCP ports 49152 through 65535.
OSX GO FTP PORT MAC
Last confusing bit: If I turn on web services and put my domain name in the browser of my mac book air I see the server default web page. The same thing happens on my mac book air withįtp forwarding is set up by Server app, and when I check it with Airport Utility it looks correct with port 21 as private and public TCP ports. I open a terminal shell on my mac mini and tryįtp *** and it works (10.1.0.9 is the mini local IP)Īll is great so I open a terminal shell on my macbook air and tryįtp IP address) *** and it hangs, eventually sayingĤ21 Service not available, remote server timed out. Using Server app I added FTP as a public service to my airport base station. I set up os x server on my mac mini using my subdomain. My mac mini is connected to the internet through my airport base station, which is connected by u-verse (via the DMZ). I created a subdomain (on godaddy) and set the A record to my home IP address (u-verse). I am trying to set up my mac mini as an ftp server (and only an ftp server).
0 kommentar(er)
