[jethro]

Thanks a lot for the help!

I had already tried that fix. It does limit the ports that the server sends out (which is nice), but it doesn’t seem to help the fact that it’s sending the local IP address instead of the public IP address.

Anything else I might try???

[jethro]

Well, before I go down the road of trying to figure out another FTP program (including setup, installation, etc.), can anyone state verifyably if the built-in FTP server is definitely NOT able to do this??

Thanks. I’m just learning servers and would love to stick with the built-in stuff for now for the sake of support and compatibility. A 3rd-party solution may be a last resort for me if this isn’t at all possible, though.

[jethro]

OK, after searching COUNTLESS forums for the answer to this, I think I may understand what’s happening, I just don’t know how to implement the fix.

I’ve only been using servers for a couple weeks now, so forgive me if I’m a bit off on anything 😆

What I believe is happening is that when the server responds to the client’s request for an open port, it is sending out it’s internal private IP address (192.168.1.x) instead of the public IP address the client would need to respond on. Apparently this may be because the Linksys router isn’t handling the NAT functions very well.

So can anyone tell me if it’s possible to force the server to reply with the static IP address our ISP assigns us instead of the internal IP address we use behind the router? If it needs to be done in Terminal, can you give me a bit of walk-through (again, I’m a newbie).

I’ve searched everywhere, but cannot seem to find the instructions on how to do this. Apple won’t help me because they say it’s the router’s fault. Linksys won’t help me because, well, they’re a bit clueless to advanced stuff like this. They all say “just open the proper port”, which of course I’ve tried to no avail.

Thank you!!

[Author]

Posts