The server however looks to be shut out from outside access: no VPN service for a while, privately hosted websites are down and network shares that were mounted prior to the freeze are ejected (indicating a network freeze within the LAN also). I know for a fact that at these 'freezes' the AEX remains up and running, because the PMS on my Synology NAS is still accessible. I have even accessed media from outside of LAN, but then immediately (or after a few seconds) the Plex client freezes/hangs as the PMS on OS X Server is not only disconnected from MyPlex, but also becomes inaccessible when I try to VPN back in to my server. PMS broadcasts within my LAN without Plex clients having to authenticate (using MyPlex). Yes, I can access the media locally via PMS without problems. So if it is not the adaptive firewall, and Port Mapping seems to work for one network client, then why not for the computer running OS X Server? Any ideas or advices are very Davis: BTW, both internal ports are both set at 32400 as the PMS-software expects incoming connections at this port. If I switch 32401 to point at the server and 32402 at the NAS, then only 32402 is found 'open' by a port scan. So, for instance if I open external port 32401 up to point at the static IP of the NAS and port 32402 at static IP of the server, only port 32401 registers as opened upon a port scan. I even experimented by editing/switching the IP-addresses of the server and the NAS in the Port Mapping: the Port Mapping that points to the server does not open up, whereas the Port Mapping to the NAS is registered with every Port Scan that I make, on every edit. Somehow OS X server (or something) seems to hinder or block the Port Mapping, as another Port Mapping to a second PMS running on a Synology NAS works just fine. The Port Mapping to the server is correct and corresponds to the static IP-address of the server. I checked wether there was an exception for PMS when the firewall was switched on and there is incoming connections are accepted for PMS, even when the firewall is switched on.Īlso, the server has a static IP-address, of course, as it handles a few other services for client computers: my AEX has several reserved IP-addresses for network computers based on their MAC-addresses and this has never let me down. The built-in Firewall is switched off, so that should not hinder PMS. Note: the AEX is behind a cable modem which is in Bridge Modus.
MAC OS FIREWALL OPEN PORT 80 MAC
Mac Mini (2009) running OS X Mavericks 10.9.4 (13E28)Īirport Extreme (4th gen), Firmware 7.6.4 The things I found on the internet use the ipfw-command, which is deprecated in Mavericks. Also I would like to learn how I can open up a specific port in OS X Server/Mavericks, maybe using Terminal.
I don't know where to look to confirm wether or not it is true that the Adaptive Firewall is blocking, but maybe some of you can point out where to look. When the block was released and I could VPN back into my server I also noticed that mounted Network shares from within the LAN were ejected. Attempts to connect from outside the LAN using the Portforwarding brings down the server, or at least services like the VPN-service. The Firewall in OS X server is off, according to System Preferences, but I figured that Apple's Adaptive Firewall is blocking access through this port. Although the Port Mapping looks as if it set correctly within Airport Utility, a port scan reveals that it isn't. For this MyPlex-service to work I have made a Port Mapping in my Airport Extreme (AEX) pointing to my Mac Mini running PMS-software. PMS uses a service called MyPlex for any Plex clients you have outside of your LAN (like iPhones, iPads or roaming MacBooks) to connect to PMS easily. I am running Plex Media Server (PMS) on a Mac Mini and OS X Server (10.9.4) and I am having issues with it to function properly.
0 kommentar(er)
