Apple Support Communities > Servers and Enterprise Software > Mac OS X Server v10.6 Snow Leopard > Discussions
This discussion is archived
4423 Views 7 Replies Latest reply: Dec 21, 2009 12:01 AM by Ryan Vetter1
Currently Being ModeratedOct 15, 2009 10:14 PM (in response to mike.habermeier)I agree, not in the documentation. However the marketing page
Shows a regular https://mobile.example.com in Safari. I have the MA server behind an Airport and thought that may be the problem. So I put in directly into the cable modem, updated my external DNS and tried again. I was using my iPhone to try to load the MA login page.
There was this from page 184 of the Network Services Admin manual
After you configure NAT, start Mobile Access service to make it available.
So I turned on NAT, but still no luck.
What do you need for this to work? Does the MA server need to be the gateway? Why wouldn't the login page serve up even without NAT?
Message was edited by: jmcaMacBook, Mac OS X (10.6.1)
(That quote from page 184 of the manual contains an error; it should make no reference to NAT.)
The most common misunderstandings of Mobile Access service are:
1. You need to run it on a separate host from the one where your HTTP services run, and the Mobile Access host needs to be the one on the public internet.
2. You need to use split DNS, and that usually means getting your ISP to create a public DNS record that maps your origin server host name to the public IP address of the host running Mobile Access.
Currently Being ModeratedOct 18, 2009 9:10 AM (in response to mike.habermeier)I'm pretty sure I have split DNS setup correctly. I'm using no-ip on the outside and OS X server inside. They both have and entry for mobileacces.server.com. The outside is a public address the inside is an internal address.
The problem is that when I go to the public address nothing comes up. I would expect a login page over the default http ports. To test out the DNS I turned on the webserver and I got the default web page. So my DNS is going to the right server on the outside & inside.
It's like Mobile Access is not listening. I would think that there would be something in the logs when I try to hit it.MacBook, Mac OS X (10.5.2)
While these training videos require prior expertise in server admin, they explain mobile access and how to set it up. It's a very real feature, but one that Apple decided not to cover in detail in their manuals.
Funny, because it's pretty much one of the best features of the server.
Here are the videos:
For those reading in a future where the above link is broken, search with keywords in Google:
sean colins lyndaMacBook Pro 15" 2.4 GHz; Mac Mini 1.83 GHz; MacBook Air 2.13 128 SSD., Mac OS X (10.6.2)
You'll need a second server (reverse proxy) to implement Mobile Access. Check the Apple manual, it is mentioned.
KostasDual 1.25 PowerPC G4 - MacBook Pro 2.16, Mac OS X (10.6.2), ACMT, ACHDS 09