![]() If you’re running macOS Server on a NAT’d network you’ll want to set up local DNS when it arrives. Once a netowrk connection by IP address works, then a connection using DNS can be tested. The DNS-based testing is secondary to getting the IP address and connection working. (Passthru is what’s available with the Apple Wi-Fi gear.) It’s good residental gear, but can lack support for features server-based configurations might need or want. The Apple Wi-Fimhear can do that, but it’s somewhat under-featured for servers. Once one box is working, then added boxes can be configured incrementally, probably starting with thr box you’ll be using for NAT and firewall duties. If you’re running your own gateway, the ISP box will normally require being configred as a bridge or transparent-mode or whatever the ISP calls the “stay out of the way” setting for the particular box being used as your ISP network demarc. You don’t mention the ISP box here, and an ISP gateway box can be configured for NAT and firewall duties, which you probably don’t want here and will need to re-evaluate in any case. Or try an ssh connection or a traceroute, from a remote host. Then run a port scan remotely for some open port on the MacBook Pro at the public static IP address. ssh is one of the safest choices, assuming you have solid passwords. Make sure some port that wil be remotely accessible is open on the MacBook Pro. Get rid of most, configure the MacBook Pro at the public static IP, ensure its firewall is enabled but allowing at least one port, and try a connect directly to the ISP box. Okay, so you have a whole lot of gear involved in this.
0 Comments
Leave a Reply. |