4 Replies Latest reply on Apr 23, 2016 1:23 AM by DonCollier

    FM Server not listening on https://<ipaddress>:16000

    ebsanford

      I have a new FM Server installed on a Mac Mini running El Capitan and Server 5.1. Installation seems to have finished normally, and the FMServer_Sample file is available to FMP desktops and my iPad. Further I can connect to admin-console on the "localhost" with no issues. But I am experiencing two issues of note:

       

      (1) Even though I can connect (using Safari on the Mini) to https://localhost:16000, I cannot connect (still on the Mini) to https://192.168.1.5:16000.  Nor can I connect to  https://192.168.1.5:16000 from any other machine on the network.

       

      (2) When working from a FM solution on my iMac, whenever I attempt to share my updated solution to the Mini, I get a connection error. The connection dialog does find and display the server's name. But a connection error still occurs. If I manually copy the solution file to the correct folder on the server, set permissions, etc. the Mini will serve the solution across the network as expected.

       

      As far troubleshooting, I did a port scan using the server's Network Utility.  Both ports 16000 & 16001 show open when scanning on the "localhost" address, but neither port shows open when scanning on the "192.168.1.5" address.

       

      Any help or advice would be greatly appreciated!!

      Thanks.

        • 1. Re: FM Server not listening on https://<ipaddress>:16000
          DonCollier

          What is the OS of the mini?  have you checked there are no firewalls working either on net mini or elsewhere that would be using this?

           

          Probably ought to confirm as well that the min is  on 192.168.1.5 and that nothing else is.

          • 2. Re: FM Server not listening on https://<ipaddress>:16000
            ebsanford

            Don, thanks for the reply.

             

            Yes, I did verify that the Mini server (and ONLY the Mini server)  is using 192.168.1.5, as a ping of this address returns only a single reply.  The Mini is running El Capitan with Server 5.1 installed.  Since this is an internal server with limited access, no firewall is presently running.  Below is a copy of two port scans run on the Mini using 192.168.1.5 and "localhost" respectfully.  Clearly port 5003 is open in both cases, but port 16001 is open only under "localhost".

             

            Port Scanning host: 127.0.0.1

             

              Open TCP Port: 21     ftp

              Open TCP Port: 22     ssh

              Open TCP Port: 80     http

              Open TCP Port: 88     kerberos

              Open TCP Port: 311    asip-webadmin

              Open TCP Port: 443    https

              Open TCP Port: 445    microsoft-ds

              Open TCP Port: 548    afpovertcp

              Open TCP Port: 625    dec_dlm

              Open TCP Port: 1895

              Open TCP Port: 4444   krb524

              Open TCP Port: 5003   fmpro-internal

              Open TCP Port: 5013

              Open TCP Port: 5900   rfb

              Open TCP Port: 8008   http-alt

              Open TCP Port: 8333

              Open TCP Port: 8443   pcsync-https

              Open TCP Port: 8800   sunwebadmin

              Open TCP Port: 8843

              Open TCP Port: 10355

              Open TCP Port: 10548

              Open TCP Port: 10631

              Open TCP Port: 16001

              Open TCP Port: 16004

              Open TCP Port: 20300

              Open TCP Port: 20343

              Open TCP Port: 20344

              Open TCP Port: 20345

              Open TCP Port: 20346

              Open TCP Port: 20543

            Port Scan has completed…

             

            Port Scanning host: 192.168.1.5

             

              Open TCP Port: 21     ftp

              Open TCP Port: 22     ssh

              Open TCP Port: 80     http

              Open TCP Port: 88     kerberos

              Open TCP Port: 311    asip-webadmin

              Open TCP Port: 443    https

              Open TCP Port: 445    microsoft-ds

              Open TCP Port: 548    afpovertcp

              Open TCP Port: 625    dec_dlm

              Open TCP Port: 5003   fmpro-internal

              Open TCP Port: 5013

              Open TCP Port: 5900   rfb

              Open TCP Port: 8008   http-alt

              Open TCP Port: 8333

              Open TCP Port: 8443   pcsync-https

              Open TCP Port: 8800   sunwebadmin

              Open TCP Port: 8843

              Open TCP Port: 10548

              Open TCP Port: 10631

              Open TCP Port: 20300

              Open TCP Port: 20343

              Open TCP Port: 20344

              Open TCP Port: 20345

              Open TCP Port: 20346

              Open TCP Port: 20543

            Port Scan has completed…

            • 3. Re: FM Server not listening on https://<ipaddress>:16000
              ebsanford

              After more hours of struggling with this issue I finally decided that something was going on between FMS and Apple's Server bundle. Although I did disable the Server bundle Apache, there was still something amiss. So I removed FMS completely from that system and installed it on a different Mini that didn't have the Server bundle. Everything appears to be working now.

              • 4. Re: FM Server not listening on https://<ipaddress>:16000
                DonCollier

                I think you just preempted my next test.  I was going to suggest hat you who'll look at the DNS.  Putting FMP on a xserve you need to have the DNS properly set up and an FQDN in play or you can have issues. I haven't tested FMPS 14 and El Capitan xserve so I don't know if there are other issues but there may be with Apache. Perhaps someone who has can feed in here .