www.server domain.com

[JoelBC]

Apologies in the event that this is a naive or obvious question...

I am reading up on installing and setting up OS X Server in my home [only thing I am waiting for is the September 9th announcement to determine what I will use as my server, hopefully a new Mac Mini].

I will setup my internet connection such that it will be static and public...I will also setup a fully qualified domain name [i.e. server.homenetwork.com ].

When I want to externally connect to the server [i.e. from the cottage, from work, etc.] and I enter http://server.homenetwork.com what will I access / see...will I see the server log on screen, will I see the server configuration / control panel / other?

TIA,

Joel

 

[irnchriz]

Apologies in the event that this is a naive or obvious question...

I am reading up on installing and setting up OS X Server in my home [only thing I am waiting for is the September 9th announcement to determine what I will use as my server, hopefully a new Mac Mini].

I will setup my internet connection such that it will be static and public...I will also setup a fully qualified domain name [i.e. server.homenetwork.com ].

When I want to externally connect to the server [i.e. from the cottage, from work, etc.] and I enter http://server.homenetwork.com what will I access / see...will I see the server log on screen, will I see the server configuration / control panel / other?

TIA,

Joel

That depends on what services you run on the Mac and if you have the appropriate ports opened and pointing to it from your router.

Example:

You purchase macminidomain.com and create an A record in DNS for server.macminidomain.com and point it to 80.80.80.80 (your routers external IP address)

Now on your router you open port 80 and point it at your servers internal ip address. And finally on the server you enable the wiki on port 80.

So when you enter http://server.macminidomain.com it will take you to your wiki site on your server.

As I use only Macs I have back to my mac enabled and use this for accessing all of my macs remotely through screen sharing rather than opening the server to the world.

 

[JoelBC]

That depends on what services you run on the Mac and if you have the appropriate ports opened and pointing to it from your router.

Example:

You purchase macminidomain.com and create an A record in DNS for server.macminidomain.com and point it to 80.80.80.80 (your routers external IP address)

Now on your router you open port 80 and point it at your servers internal ip address. And finally on the server you enable the wiki on port 80.

So when you enter http://server.macminidomain.com it will take you to your wiki site on your server.

As I use only Macs I have back to my mac enabled and use this for accessing all of my macs remotely through screen sharing rather than opening the server to the world.

Appreciate the response, very helpful indeed and understood...that said, is there a way to configure OS X server such that it opens / points to the server desktop over https://?

And, on this point, are you suggesting that it would be better to forgo this and simply use the VPN service and then use screen sharing?

Am just trying to figure out i) the benefit / need to register a fully qualified domain name [i.e. rather than setting us OS X as .private] and ii) where to point the server?

Thanks,


Joel

 

[irnchriz]

Appreciate the response, very helpful indeed and understood...that said, is there a way to configure OS X server such that it opens / points to the server desktop over https://?

And, on this point, are you suggesting that it would be better to forgo this and simply use the VPN service and then use screen sharing?

Am just trying to figure out i) the benefit / need to register a fully qualified domain name [i.e. rather than setting us OS X as .private] and ii) where to point the server?

Thanks,


Joel

If you are looking for remote access then I would recommend the VPN and screen sharing route. As for using a FQDN, unless you are hosting websites and want to keep it all the same internal and external or are using SSL then its not necessary. I have a FQDN for my server but i have an SSL cert for a couple of services I have setup for external access plus it keeps it all tidy.

I have a domain name and have an A record of server.myserver.co.uk which is also the FQDN of my server. This A record points at my external IP address and I have NAT rules pointing certain ports to the server. Other than the services I am running for external access the only other thing I need is screen sharing and as its only the server I want onto I haven't bothered with a VPN but use back to my Mac through my iCloud account. I also have a logmein client installed as a backup incase I don't have my Macbook on me or want to get in from my iPad or a PC.

 

[JoelBC]

If you are looking for remote access then I would recommend the VPN and screen sharing route. As for using a FQDN, unless you are hosting websites and want to keep it all the same internal and external or are using SSL then its not necessary. I have a FQDN for my server but i have an SSL cert for a couple of services I have setup for external access plus it keeps it all tidy.

Again, appreciate the response...

I will not -- at least for now -- be hosting or running websites...

One of the services I will be running / using is Profile Management which as I understand things [based on my readings] is i) best used with an SSL certificate [rather than a self signed certificate] and ii) best used with a FQDM...is my understanding correct or am I wrong...

Would also appreciate you expending on what you mean by keeping "everything tidy" as I am big fan of consistency, ease of use, etc...

I have a domain name and have an A record of server.myserver.co.uk which is also the FQDN of my server. This A record points at my external IP address and I have NAT rules pointing certain ports to the server. Other than the services I am running for external access the only other thing I need is screen sharing and as its only the server I want onto I haven't bothered with a VPN but use back to my Mac through my iCloud account. I also have a logmein client installed as a backup incase I don't have my Macbook on me or want to get in from my iPad or a PC.

Agree and understood as this is one of the reasons I current have a Team Viewer account setup albeit for my MBA in case I need access to it while travelling...

I will need to investigate both Back to my Mac and Apple Remote Desktop some more...

 

[irnchriz]

By keeping everything tidy I mean, my server name is the same on or off my network as it's a FQDN. I just like it that way

I know that you need an SSL cert for the MDM part of profile manager but I have only ever set that up for a client of mine who uses it to manage the firms iPhones. It's not something I deemed necessary for my own iPhone and iPad.

 

[JoelBC]

By keeping everything tidy I mean, my server name is the same on or off my network as it's a FQDN. I just like it that way

As do I so I will likely go this route as well, at least initially until I have enough experience to get everything sorted as this gives me maximum flexibility...

I know that you need an SSL cert for the MDM part of profile manager but I have only ever set that up for a client of mine who uses it to manage the firms iPhones. It's not something I deemed necessary for my own iPhone and iPad.

Agreed, I too feel the same way but very much want to play with things both for fun and to fully understand what can be done...I hope this does not prove to be a mistake and a very frustrating experience.

 

[JoelBC]

So, back to my initial question, is their a way to configure OS X server such that from outside my network https://server.serverdomain.com presents the OS X Server's logon screen?

Thanks,


Joel