Skip navigation

TS3960: Server App or Server Admin can't connect to a newly upgraded Lion server

Learn about Server App or Server Admin can't connect to a newly upgraded Lion server

TS3960 Unable to connect to Lion Server with Server App or Server Admin

1246 Views 9 Replies Latest reply: Aug 12, 2012 11:15 PM by Mark23 RSS
Subrunner7 Level 1 Level 1 (0 points)
Currently Being Moderated
Aug 12, 2012 9:21 AM

I'm running 10.7.4 on my Mac Mini and my iMac.  I administer my Mac Mini server from my iMac.  I am unable to connect using fully qualified domain name. Even after checking the items in this article. 

I am able to connect if I use the internal network ip address or the servername.local name.

Has anyone had this problem and what was done to fix it.  Thanks

Mac mini, Mac OS X (10.7.4)
  • Mark23 Level 3 Level 3 (975 points)

    Is the external interface configured with your static IP, asuming that you indeed have one as any server should?

    If so, the first thing that comes to mind is af firewall issue. What services are you tying to reach and are the associated port numbers open to be accessed from the outside?

  • Mark23 Level 3 Level 3 (975 points)

    It's port 687 (TCP) that needs to be opened.

    For L2TP VPN you'd need port 1701 (UDP) to be opened.

    For PPTP VPN you'd need port 1723 (TCP) to be opened/

    (source: Well known TCP and UDP ports used by Apple software products)

     

    The server being located on the same subnet should not be a problem, however do make sure all the ports needed are forwarded from your modem and router to your server. If you choose to forward all incomming traffic to your server, please make sure you have the firewall enabled and configured to allow only access to the ports you want to as listed in the document above at least from the "any" group within server admin's firewall section.

  • Mark23 Level 3 Level 3 (975 points)

    I believe I read your post wrongly... Lion Server sets up it's own DNS server if it can't find one at install time, so adding the internal IP as a DNS server to your client's network preferences should enable you to access the machine by it's FQDN, provided that the DNS service lists the FQDN.

     

    You can access the DNS server via Server Admin.

  • Mark23 Level 3 Level 3 (975 points)

    The certificate verification warning isn't supposed to come up if:

    - you connect through to a connection that isn't supposed to be encrypted, or

    - you have a valid certificate set up that has been issued by an official certificate authority.

     

    I have noticed that when I try to connect using the internal ip address I don't  see the certificate verification warning come up.

     

    Could I have a bad certificate that is not popping up for verification?

     

    Since you are administering the server from the same subnet behind a firewall, I guess there's no need for an encrypted connection

     

    Did you enter your server's IP as an additional DNS server in your client's network preferences?

  • Mark23 Level 3 Level 3 (975 points)

    It was a joy helping you out

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.