Making Snow Leopard Server services accessible through Time Capsule

Sorry, this will be a fairly long explanation. I think this is the right forum but the question kind of spans several component elements.
During the setup of Snow Leopard Server I let it configure the Time Capsule for services that it is providing, which I want to make available to both the local network and to computers coming in from the Internet. However, there seem to be some conflicts between Time Capsule ports and Snow Leopard ones.
First my set-up: I have Verizon FIOS and have set up my Actiontech Router into bridge mode to the Time Capsule so that the Time Capsule grabs the public IP address. The Snow Leopard Server has a dedicated private IP from the Time Capsule through the DHCP reservation. I have a dynamic DNS setup which consistently points to the public IP address assigned to the Time Capsule. After starting services on Snow Leopard Server, I can see the port mappings created on the Time Capsule by the server allocated to the server's dedicated private IP address. However, the File Sharing (AFP, SMB) entry can't be enabled because the ports used for those services conflict with the ports opened by the Time Capsule to enable backups from client Time Machines (TCP Ports 548, 139). Therefore, any external access to those ports are going to the Time Capsule and not routed to the Snow Leopard Server.
Two questions:
1. Should I map the DNS hostname to the Time Capsule on the Hostnames screen on AirPort utility? While this will enable remote access to the Time Capsule (so that if my client computers are outside coming from the Internet), will this mess up remote access to the Snow Leopard Server?
2. How do I get around the problem of the port conflicts between what Time Machine needs to get to the Time Capsule for backups versus enabling the ports for AFP and SMB on the server?

I actually found an Apple support tip and am posting it here to answer the question:
http://support.apple.com/kb/TS2963
Bottom line: you can't have both devices doing file sharing unless you set up VPN access.

Similar Messages

Is it possible to browse a Snow Leopard back-up on a Time Capsule shared with a Lion backup using the Lion-only machine?

My 2006 Macbook died but was backed up to my Time Capusle. This machine was running the most uptodate version of Snow Leopard at the time.
I've read that I should be able to access this backup using a different Mac but I can't see it when I CTRL-click the Time Machine icon (in the dock), when using my Macbook running Lion 10.7.1. It only shows me the current backup for this machine.
I know the old backup must be there somewhere as the Time Capsule is almost completely full (700 gb of the 1tb was dedicated to the old MA

If you control-click on the Time Machine icon and select "Browse Other Time Machine Disks" but don't see the other backups, try this: Look in the "sidebar" of a Finder window for your Time Capsule. If you see it, select it, then look for the Time Capsule's disk (probably called "Data" if you didn't rename it). Double-click that to mount it. Now try again to control-click on the Time Machine Dock icon.

Configure DNS on Snow Leopard Server for Web Hosting

Hi Everyone,
I put together an article on my blog about Snow Leopard DNS setup for web hosting. http://www.mkahn.com/?p=279
I'll be revising it over the next few weeks to make it more informative based around feedback. Let me know if you have any questions or trouble setting up DNS on Snow Leopard Server for web hosting.

Thanks for your replies. I realize I'm not making clear the way this network is configured . Also, the only services running on the Snow Leopard server are (at this time):
dhcpd - in the 10.136.31.x range;
dns - same as before;
planned to add are:
Open Directory (for network logins)
Software update;
Web (only on the 10.136.31.x Ethernet);
mySQL (localhost only - for moodle);
NAT is not set up on the Snow Leopard server itself. We have an outside router, a Cisco 2811. This router provides routing for both the public IP range, and the NAT range is configured in this router. The forwarding dns is located in LR and Fayetteville. So what I need is dns on Snow Leopard to forward outside queries to the state DNS servers, and resolve the local NAT IP only for Open Directory and a set of Snow Leopard clients.
Is this going to be possible?

Installing Snow Leopard Server From a USB Sticki

In my job, I install Snow Leopard and Snow Leopard Server three or four times a day.
With Snow Leopard, I've found it easiest to install from a USB stick. So, I did a restore from a DVD to a USB in Disk Utility and it's worked great.
With Snow Leopard Server, it is not so simple. When trying to install from a USB stick, I get "Mac OS X 10.6 Server Cannot Be Installed To This Machine." Though strangely, installing from the DVD is no problem.
I've tried to restore straight from the DVD to the USB. I've also tried to install from the DVD to a disk image to the USB. Both times, the USB will mount fine, but I get that error message.
Am I missing a trick here?

Oddly enough it is working for me. I had some issues initially so I went out and bought ONE 16GB thumb-drive (major vendor) and partitioned into two partitions.
I restored one of the partitions with 10.6 and restored the other with 10.6 server. Works flawlessly for me though I do like netinstall. It is a bit slower than the FW800 drive though I do not have to carry around a power brick.
I hope this helps!

Time Machine on Snow Leopard Server

I would like to setup a backup service using Time Machine of a Mac Pro Snow Leopard Server (10.6.5) to an external hard drive connected with USB. Are there any gotcha's with this type of setup that I need to be aware of? My faint memory recalls an issue with Time Machine backing up a server.
The server is mainly used for file sharing in a small (<10) person office.

Are you backing-up the clients, or the server, or both?
Like most folks here, I'm not very familiar with the Server product, but I understand TM can do either or both.
You may find better advice in the Server forums, at: http://discussions.apple.com/category.jspa?categoryID=96

Can't Star iChat Service after update to Snow Leopard Server

We had installed Mac OS X Server on a Mac Pro, and we had the iChat Service working in the organization; but when we update to the Snow Leopard Server we can't start the iChat service again. In the Server Admin app, on the iChat node in the Overview I have this:
iChat Service is: Stopped
Start time: not available
Domain: not available
Client connections: not available
With the update if I choose the iChat service node, I can't see the Start iChat button.
Can somebody help?
Thanks a lot.

Please try here http://discussions.apple.com/forum.jspa?forumID=1352
OS X Server Snow Leopard > Chat and other items.
8:40 PM Monday; January 4, 2010
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

Upgrade from Snow Leopard Server to Lion Server hangs at configuring services...

I am running the Mac mini with snow leopard server 2.53 ghz 2GB of ram, 2x500GB hard drives, and have followed through the process to install Lion Server. The installation appears to be hung at the Configuring Services section of the setup process. I have left it for a couple of hours and nothing has progressed.
Should I leave it longer, hoping that it will work through the process (if in fact it is working through something)?
How long should this normally take?
As this is my work server, hosting mail, web, FTP, and file sharing, it is rather important to get it up and running as quickly as possible.
Any thoughts on how I can get it moving?
Hard power off of the Mac Mini reboots the machine, then proceeds back to the setup page, and then hangs on the same Configuring Services.
Any assistance would be much appreciated.
Thanks.

Lion Server Upgraders,
beware and proceed with caution.
Apple web site is naively optimistic on the upgrade process:
"To upgrade your Mac to OS X Lion, you don’t need to drive to a store, bring home a box, and install a bunch of discs. All you do is click the Mac App Store icon, buy Lion for $29.99, and your Mac does the rest. Just make sure you have what you need to download Lion to your Mac."
And then has a 3 step process...
This is completely miss leading.
Read this document first: http://manuals.info.apple.com/en_US/lion_server_upgrading_migrating.pdf
It will make it readily apparent that moving from Snow Leopard Server to Lion is not going to be simple.
Having done this twice now.. I have found that:
1. Open Directory migration is a weak point. Lion & Snow Leopard Open Directory are not compatible, so if you have masters & replica then expect trouble. I have an unresolved issue trying to get a simple Lion Server to Lion Server Open Directory replica up and running. This compatibility seems to also cause migration to fail, as I found that all my local User/Groups transferred ok but non of the /127.0.0.1/LDAPv3 (Open Directory) ones did. This is a very important item, as all the mail accounts in dovecot use LDAP generated UID, so you have to be careful that you do not loose mail accounts.
2. Mail - your mail aliases will not transferred, so you will need to reapply the aliases.
3. Web Server Setup - This broke, under migration as I gather the entire Web serving tree has changed. In particular I had "Snow Leopard" Web Mail (which is based on Squirel) on my "Snow Leopard" Server and this is now dead...
4. Digital Certificates - I found that the valid (ie signed by trusted CA's) did not get migrated, so I had to re-imported my Digital Certificates. If you have paid for third party CA certificates then make sure you have got these copied somewhere, as if you loose them then you will likely need to go to your provider and get a certificate revocation and new certificate, which will cost you money!
Cheers,
Zebity.

Error configuring services from Snow Leopard Server to Mountain Lion Server

I am trying to upgrade a Snow Leopard Server Mac Mini to Mountain Lion Server.
We have two Mac Mini servers at our office (production and backup) so I migrated the everything from our production server to the backup using the migration assistant when setting up the backup computer.
I now have the backup at home trying to upgrade it to Mountain Lion Server. I have downloaded and installed Mountain Lion as well as the Server App version 2.2. I basically followed the simple directions found in the Apple documentation.
I started the server app and it got to the part where it said "Upgrading services". After running for a few minutes, I get a window that states "An error occurred while configuring your server." It also sayd "The following actions failed or were not attempted:" with a red dot next to "Upgrading services". The other three items: "Authenticating to local directory", "Reading directory configuration" and "Authenticating to local directory services" have gray dots so I'm sure they were not even attempted.
Our Snow Leopard server is setup for SMB file sharing, LDAP services, FTP, Web, DNS, DHCP.
Can someone point me to where I can figure out what exactly is failing? Are there specific log files I need to look into?
Thanks

Have EXACTLY the same issue - also tried reinstalling mountain lion server fresh and still had the same problem...

Trying to stop MYSQL service without success in snow leopard server

Hello
I trying to enabled MySQL service on snow leopard server.
My hard drive name is "Macintosh HD2".
I receive this message :
Can't change dir to '/Volumes/Macintosh HD2/ServiceData/MySQL/' (Errcode: 2)
I try to stop without success MySQL service for rename my HD without blank
How do that please ?

That's set up via the [MySQL command line|http://labs.hoffmanlabs.com/node/376]. Or you can install the (free) Sequel Pro GUI package, given you're probably more comfortable in the GUI. The steps required for Mac OS X Server are the same as most any other platform, so [launch the MySQL client per the Wordpress Codex|http://codex.wordpress.org/Installing_WordPress], and follow the instructions.

Does Snow Leopard Server iCal Service support iCal Groups?

I have successfully configured iCal Service on Snow Leopard Server 10.6.8v1.1 and have several client Mac system (runing SL 10.6.8v1.1) connected to this service via CalDAV. I can create new calendars and those calendars and any test events propigate to all machines that have this CalDAV account configured. But whenever I try to create a calendar group it always appears as a local calendar group. Is this a feature missing when using iCal Server and CalDAV? Am I doing something wrong?
Thanks

Hi
I doubt if you'll find a step-by-step as most people's requirements are different. One of the places most people start is here:
http://support.apple.com/manuals/#macosxserver
Have you tried searching the Forum itself?
http://discussions.apple.com/forum.jspa?forumID=1352
Tony

Creating a versatile DNS and redirection service on Snow Leopard Server

For the few of us who use Snow Leopard Server as a main DNS for our small network, the following is a workflow that I would like to share with the board for creating redirection services to not just sites found on the locally hosted apache but also external sites.
+IF you are adding a second domain name, the reverse domain lookup will not appear and you will need to add a Machine/A record with the fully qualified domain "domainname.com." (don't forget the . at the end) into the new zone and it will point to the "server" Machine/A record ip address.+
*DNS Portion* : (ServerAdmin > DNS > Zones >
Add Zone > Primary > Create a fully Qualified Domain name and dns "server" in the Machine / A Record
Create the (add Record > Alias/ CNAME) subdomain pointing to the server.domainname.com e.g. (library)
*Web / Apache Portion :*
Create a new site (ServerAdmin > Web > Sites > Plus button)
With General > host name exactly as spelled in above subdomain in full (library.domainname.com)
Select Web Folder where the site is hosted
If you are creating a redirection, create a folder on the server, add an index.php (with the script below)
Add Alias with the same subdomain as number 2
_PHP script :_
<?php
$location = "http://example.net";
header("Location: ".$location, "301 Moved Permanently");
?>
// Edit the "http://example.net" to which ever e.g. "http://apple.com"
_Alternatively you can also mask the page with :_
<html>
<head>
<title>Same Title As Your Homepage</title>
<script type="text/javascript">
function changeTitle()
if (top.frames['main'].document.title)
top.document.title=top.frames['main'].document.title;
</script>
</head>
<frameset>
<frame name="main" src="http://actual-url.anotherhost.com/page.html"scrolling="auto" target="main" ONLOAD="changeTitle();">
<noframes>
<body>
Place a suitable message here for people with browsers that can't read frames.
</body>
</noframes>
</frameset>
</html>

Ok, local DNS services (unicast DNS) are typically straightforward to set up, very useful to have, and can be necessary for various modern network services, so I'm unsure why this is even particularly an open question. Which leads me to wonder what other factors might be under consideration here; of what I'm missing.
The Bonjour mDNS stuff is certainly very nice, too. But not everything around supports Bonjour, unfortunately.
As for being authoritative, the self-hosted out-of-the-box DNS server is authoritative for its own zone. That's how DNS works for this stuff.
And as for querying other DNS servers from that local DNS server (or, if you decide to reconfigure it and deploy and start using DNS services on your LAN), then that's how DNS servers work.
And yes, the caching of DNS responses both within the DNS clients and within the local DNS server is typical. This also means that there is need no references to ISP or other DNS servers on your LAN for frequent translations; no other caching servers and no other forwarding servers are required.

Snow Leopard Server with Lion Server for APNS

Hello Everyone,
I'm wanting to keep my Snow Leopard Server (Xserve) setup in place its working great, and cant afford to have any down time on the company network. What I would like to do is setup up an additional Mac Mini with Lion server to handel just the APNS. Is this possiable.
I would be running all of the services, mail, OD, addressbook, caladar, on the Snow leopard server but want to use Lion Server to push out and manage some Lion clients, and iPhone with a second server has anyone done this, can this setup work?
Thanks!
Robert

Hi Robert
"Can you provide the basics for setup?"
Apart from making sure DNS is configured correctly - as always - there's not much else you need to know. Server has to be configured as an OD Master. It does work with the default self-signed certificate although Apple do recommend you purchase one from a CA such as Verisign. I mention Verisign because it's trusted by the US Government. Once you've got your push notification certificate from Apple, enable the relevant option in the Server App. From there create the enrolment profile and key in the relevant url in your IOS device. The rest is fairly obvious. If DNS is not properly configured for your network this part probably will fail.
"Can this all be completed in server admin, or the new server.app?"
AFAIK Server Admin is not involved with APNS.
"Did you just bind Lion Server too Snow Leopard Server, connect to another OD, or replica?"
This was on a publicly accessible server that was its own OD Master. Provided things are configured correctly I can't see why it can't work with an environment that's behind NAT.
"What do I setup after this?"
Apart from making sure DNS is configured properly as well as the tip regarding trusted certificates I can't think of anything else? From what I've seen MDM in Lion Server is very good and what's more quick on the devices I tested. I only tested IOS devices and testing was done 'over the air.' You can still use the ICPU assuming you kept a copy of the download?
HTH?
Tony

I've got Snow Leopard Server, but don't need the server functions. What to do?

This is somewhat complicated, so please bear with me. My Mac Pro was running OS X 10.5 and required updating. But we have legacy Power PC apps (mainly FreeHand) that we want to continue using, even though Mountain Lion doesn't support them.
As a solution, I'm going to run Snow Leopard Server in emulation on Parallels 8 Desktop. I would rather have used plain old Snow Leopard instead of the server version, but Apple's EULA only allows 10.6 Server to run in emulation.
So, I got Snow Leopard Server and have used it to upgrade 10.5. Eventually, (once I get everything working properly), I'll upgrade that to Mountain Lion and use SL Server in Parallels emulation to run the old Mac apps we can't do without.
But I've run into a problem I didn't anticipate: I don't have a clue about running a server.
I'm having trouble setting it up so the other Mac user in my department can access a shared folder. Also, I want the login window to display the list of users, but that option is grayed out.
What I'd like to do is strip out all the server functions and just run as if 10.6.8 was a standard version of Snow Leopard, which I'm familiar with. If that's not practical, please explain how to get sharing to work since that's the main problem.
I've tried turning off the services listed in the Server Preferences (iCal, Mail, etc.) but that hasn't fixed the problems. I think there may be server functions running that I haven't found preventing me from fixing the problems. Or it could be something else entirely (as I said, no clue).

DON'T MAKE A MOUNTAIN (lion?) OUT OF A MOLEHILL!
Several points in response to your post, in chronological order, not necessarily in order of importance:
• It was a common Urban Myth that Snow Leopard (client's) EULA prohibited its virtualization in Lion or Mt. Lion on a Mac! That myth has been largely debunked in the last 18 months.
Here are detailed instructions on how to install Snow Leopard client into Parallels 7 or 8:
http://forums.macrumors.com/showthread.php?t=1365439
That being said, and being the author of the aforementioned thread, I STRONGLY recommend that, where possible, you use Snow Leopard Server in favor of Snow Leopard client. This will side step some later corruption problems that can arise from the improper use and shutting down of this Parallels partition.
Historically, this thread was written when Apple sold Snow Leopard Server for $499+ or ceased sales altogether. Now, Apple has rendered the (now diminishing) debate over the EULA moot, by its recent release of Snow Leopard Server to the US & Canadian community for $20; leaving those who cannot purchase SLS (or get someone to purchase it for them) to continue to follow the instructions in my thread (or asking me to purchase SLS for them and forward it to them; my preferred course of action!).
• I ALWAYS recommend that data files be stored on the real Mac's HDs and NOT in a virtualized world. This is easy to accomplish and establishes a backup regimine (Time Machine, etc.) that will protect the users data. Lost applications are easily restored from their installer discs.
• In practice I find that using SLS in Parallels 8 is the same as using SL client in Parallels. I have even removed the Server apps from the Dock so as to not be confused by them.
So, your solution is to establish a "shared folder" on the hard drive of the Mac that is hosting Parallels. When in SLS in Parallels you will have access to your shared folder, ironically through Parallels' "Shared Folders" feature that is now present in Mac OS Guest installs on version 8 (see the "Shared Folders" SERVER on the right side of the screenshot, below).
When using Freehand MX or other PowerPC apps, save your data files into your shared folder through access to it by Parallels' Shared Folders. Other users on your network will have access to the SAME data files, through their customary use of file sharing to access your shared folder from your Mac's hard drive.
IGNORE the Server applications in the Applications folder...
Freehand MX running in Snow Leopard Server installed into Parallels 8 for use in Lion or Mt. Lion:
[click on image to enlarge]
Postscript: your post was so easy to follow!

Complications migrating from Snow Leopard Server to Mountain Lion Server.

I'm migrating from Snow Leopard Server to Mountain Lion Server. The article "OS X Server: Upgrade and migration" (http://support.apple.com/kb/HT5381) says
"Make sure that any DNS or DHCP servers on which your server depends remain running during the upgrade"
This advice is reinforced by the details of the article "OS X Server: Steps to take before upgrading or migrating the Open Directory database" (http://support.apple.com/kb/HT5300).
As the server I'm migrating from provides these services it will need to be running during the migration process. This would seem to limit my options to doing the migration from a Time Machine backup (or, making a seperate clone of the server's drive and connecting it externally to the new box)
My main concern is the seemingly inevitable clash that is going to occur on the network as the new server takes on the roles of the old one - while it is still running.
What are my options here ?
This is my second attempt as on my first try I did the migration from the TM backup with the network down - and none of my local network users or their home directories were migrated, although the settings for the mount points were, but there were no actual directories where they pointed to!
Clear directions on how to procede would be VERY MUCH appreciated
Thank you.

Moving from Snow Leopard to Mountain Lion means first installing the client (non-Server) version of Mountain Lion and then install Server.app this means that for at least part of the process you will not be running DNS, DHCP or Open Directory.
If you are going to end up using the same DNS name and IP address after the change then an approach you could follow would be as follows.
Destroy any Open Directory replicas
Archive your Open Directory Master (to make a backup)
Note down your DNS records in case they get messed up
Export via Workgroup Manager your users, and groups (you might not need this but better safe than sorry), make sure you do not include the diradmin account
Keep a full back of the server (you should always have backups)
Note down your DHCP server settings in case they get messed up
Note down any other service settings
Install Mountain Lion
Install Server.app
Install Workgroup Manager (extra free download)
Run Server.app
Make sure settings for services are as much as possible the same as before
If your lucky that may be all you need to do, otherwise...
Restore Open Directory archive, if your lucky that will be all you need to do, otherwise...
Make new Open Directory Master
Run Workgroup Manager
Import users and groups you previously exported
You will then have to set passwords for each user as these are not preserved via Workgroup Manager export
When I did this, I was also being forced to change all my IP addresses so I had no choice but to use Workgroup Manager to export and import accounts.

Question about changing a Snow Leopard Server network settings

We have an Xserve running Mac OS X Server 10.6.8, the primary services running on it are afp, smb, dhcp, dns, jabber and the calendar sever.
Right now we have a router connecting two networks together, 192.168.0.0/24 and 192.168.1.0/24. The Xserve has a static IP address in the 192.168.0.0/24 range.
In order to combine two phone systems into one I am required to combine the above networks, this will involve removing the router and changing the subnet mask on every device from 255.255.255.0 to 255.255.254.0, any device that is currently part of the 192.168.1.0/24 network will also need to have it's router setting changed from 192.168.1.1 to 192.168.0.1. That part should all be easy.
However, this is my first experience expanding a network past a standard class C and am wondering if there is anything I need to watch for on my Snow Leopard Sever.
Specifically I wonder about dhcp settings, right now there are two dhcp servers, the Xserve which provides dhcp for 192.168.0.0/24 and the router that provides dhcp for 192.168.1.0/24. Once the router is removed the Xserve will need to provide dhcp for the entire network.
Looking at the Xserve dhcp configuration right now I have one subnet defined providing addresses 192.168.0.5 to 192.168.0.125.
Can I simply click the + to add another subnet and add for instance a range of 192.168.1.5 to 192.168.1.125?
Will it simply give out all of the ip addresses in the first range and then start with the 2nd? Or do I need to find a single range of ip addresses large enough to meet my needs? (e.g. 192.168.1.5 to 192.168.1.225 or something).
Is there anythign else to watch for after making this type of network setting change?
Thanks in advance.

Thank you for your very detailed reply.
I understand the problems that can arise using 192.168.0.x and 192.168.1.x and if this were a new project I would definitely switch to something else, however in this case we have been using these ip ranges for years (they were in use here long before I started) and I don't want to have to redo all of my dns settings at the same time I make these other changes so I'm going to stick with the same ip's we are using at least for now. Anyone here needing vpn access has already dealt with this issue but we have very few vpn users so it has not been a major problem for us to date.
My biggest question is about increasing the size of the dhcp pool. For instance, after I change all the network settings and set up a /23 network is it possible to have a single dhcp pool that includes some ip's in the 192.168.0.x range and others in the 192.168.1.x range? I guess what I am asking is when I am in Server Admin and click on DHCP one of the tabs across the top is "Subnets". Right now there is a single "subnet" configured that provides addresses from 192.168.0.5 to 192.168.0.125.
Ideally I would like one dhcp pool that provides ip's in the range of 192.168.0.5 to 192.168.0.125 and then if all of those are used up, moves to 192.168.1.5 to 192.168.1.125. Can I do that by simply adding another "Subnet" so there are two? Or do I have to find one larger single range? (e.g. 192.168.1.5 to 192.168.1.225?) You may have already answered this indicating I have to have a single larger range but I just want to be sure.
The parts about changing subnet masks, and routers and all that I think I have a pretty good understanding of.
Your last paragraph is something I have been worried about, I do have a feeling that after making this change there will probably be unforseen issues that will need to be resolved, I'm just hoping it is not too many. For the scope of this thread I will just focus on issues that may arise with the Snow Leopard Server however.
Again, thank you for your help.

Making Snow Leopard Server services accessible through Time Capsule

Similar Messages

Maybe you are looking for