Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Mountain Lion Server Profile Manager not accessible externally

What do I need to be checking if I can't access our Mountain Lion server's Profile Manager externally. From a test iPad on a carrier's 3G network, I get a "server not found" error when using http://fqdn/. I can bring up the server page if I use https://publicipaddress. but not https://publicipaddress/profilemanager. Apple tried accessing the server with the same findings. We're a state agency behind tight firewall and security and we're told that all Profile manager needed ports are open... Thanks.

Posted on Dec 7, 2012 2:09 PM

Reply
10 replies

Dec 8, 2012 9:23 AM in response to RichB

ME either. It seems anything after the first slash (i.e. /mydevices or /profilemanager) is almost always sloowww... and will usually (not always) come up wether I'm using the public IP or the server name but https://publicipaddress is usually pretty snappy and reliable.


I won't be able to test again until Monday unfortunately but I'll be sure to post all results here. A second level Apple technician from their Enterprise support will also be contacting me hopefully Monday. Hate thinking that some of the issues may have been Safari on the iPad all along... On that suspicion I have cleared cache, history, cookies etc. several times to no avail.


For clarification, we're just trying to enable a corporate self-help, profile manager web portal for iOS policy enforcement/enrollment. That's it. All other services are off except DNS, Profile Manager, Web Services, Open Directory. All internal DNS checks (various different kinds) check out. There's been some ambivalence on the part of our separate network group (tonsay the least) so I can't definitively say all requisite ports are forwarded/open per cptmrgnx's suggestion above yet but I hope to nail that down Monday.


Also, the server did go through an IP address change (I know I know - couldn't be avoided) so Apple had me gut the server.app surgically in order to flush out any hard baked IP addresses left over from the initial IP. So again, All internal DNS checks (various different kinds) check out.


thanks again

May 20, 2013 6:41 AM in response to Nelson Liu

Nelson -


Pretty much everything boiled down to DNS, firewalls and ports. Unfortunately, I was never able to acertain which of the three items were causing this problem because we have a separate group who manages the network and firewall (plus a separate security team). If I recall, once they focused on what it was I was trying to accomplish, most of the problems "magically" went away.


Is your reverse DNS working the way it's supposed to? Ex:


yourserver:~ login$ hostname

yourserver.yourdomainname

yourserver:~ login$ host yourserver.yourdomainname

yourserver.yourdomainname has address 10.x.x.x

yourserver:~ login$ host 10.x.x.x

3.34.2.10.in-addr.arpa domain name pointer yourserver.yourdomainname

yourserver:~ login$


Also be sure to follow "burton11234's" posts. https://discussions.apple.com/profile/burton11234?view=overview

Mountain Lion Server Profile Manager not accessible externally

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.