Help - Snow Leopard Server Setup with AEBS

Hi.
I am trying to setup two things at once. Good start, eh ;0)
Step-by-step, this is what I have:
Internet connection
Static IP address
Apple Airport Extreme Base Station
Mac Mini Server (Snow Leopard)
Registered Domain name with access to control panel for the name
This is what I want to do:
Connect the AEBS to the Internet
Connect the Server to the Internet via AEBS
Connect Client computers (all Mac, iPhone & iPad) to the server network and the internet locally
Connect Client computers (all Mac, iPhone & iPad) to the server network and the internet remotely
This is the information that I have been given by my ISP (I have added letters before the address to help you to help me identify where they should be entered):
Router IP: (a)192.xxx.94.x (maps to (b)195.xxx.xx.xx)
Subnet Mask: (c)255.255.255.0
Default Gateway: (d)192.xxx.94.x
DNS 1: (e)192.xxx.50.xx1
DNS 2: (f)192.xxx.50.xx2
SMTP: (g)smtp.xx.net
I can't really find any obvious instructions, particularly about pointing my domain name to the router/server. Do I change the name servers/the A records, the A&MX Records on the domain control panel?
If anyone has any experience with setting-up the server with an AEBS, I would be truly grateful for some pointers! e.g. put IP address (a) in box (x)
Ha! if only it were that easy, but any help would be appreciated.
Thanks in advance.

Easy answer. Paid a local IT company to come and check my settings. Turns out that due to the office that I am in, I am in a 'double NAT' environment. When AEBS was throwing-up NAT errors, I was unsure about continuing.
Al sorted now with a few phone calls to the ISP and 2 hours' work by the IT company. Done. What else can I try and break???

Similar Messages

Snow Leopard Server combined with Snow Leopard OS

I have a MacPro (4x1 TB Drives, 16GB, RAID Card, 2 x Quad-Core Intel Xeon 2.8 GHz) that has MacOS 10.5 installed (including MS Windows running under VMWare Fusion).
The RAID setup is shown at https://www.radii.org/doc
The computer is used as an everyday workhorse (running OS 10.5.7 on Volume RS1, with Volume R1V2 partitioned into 2 data and file/document stores).
Given the specs of the machine, I plan to setup Snow Leopard Server (Raid 0) also — on a separate partition so that when the system on RS1 freezes, the server does not have to be crashed also.
Is there any advantage in partitioning the volume OSXSERVER to install Snow Leopard Server to perform a number of tasks:
1. provide first level backup and coordinate backup of data to an external/offsite filestore in the clouds for two Microsoft Small Business servers, plus about 5 Mac and Windows desktop machines
2. Provide a mail server
3. iCal server
4. address book server.
The above assumes that I can run both OSs simultaneously — is that possible, or does the system for everyday usage need to be virtualised within the Server OS?? If not, which OS will manage access to the processors?

I guess my biggest concern is the frequency with which Mac OSX gets itself tied in knots and a reboot is the only way out of the mess.
I haven't seen that myself, personally. About the only time any of my machines get rebooted is after software update.
Of course, server systems tend to be more focussed than client systems, so that might help too - the server is typically setup, configured and left to do its thing. It's not like you're constantly launching and quitting different applications throughout the day.
However, I know from years of experience with desktop systems in a variety of flavours that they will need to be rebooted at least once a week.
Ahh, there's the Windows-thinking coming through.
I have Mac OS X Server systems that, quite literally, have not been rebooted in years. Most of them have months of uptime. Of course, this means that not all my systems are running the latest OS updates but that's a call I've made.
in general, the smaller the capacity (memory, speed, HD) the more often they need to be rebooted.
Sure, but that's a matter of right-sizing your server for the load you're putting on it.
Again, there's a difference between client and server installations - client systems tend to jump between active processes with minimal background processing, whereas server systems tend to run more focussed tasks.
I have found that software such as MS Office has been highly unreliable in the last couple of years — I still get Excel saying that it 'had to close' sometime in about 10% of the times I am using it.
Right, but you're not running Office on your server, right?
I was hoping there would be a better solution than having to reboot the server — or crash it when the system freezes with a kernal panic brought on by a desktop app
Sure - don't run a desktop app on your server
If you do see that need, then run another virtual machine for your desktop apps. That means you've got one 'master' OS running multiple virtual machines - one per server process, plus another one for desktop/GUI apps.
Or, run all your server processes on a single server with sufficient resource (CPU, disk, memory, etc.) for the tasks you're running, and get an iMac or a Mini for those desktop tasks. Be cheaper that way, anyway.

Does Snow Leopard Server come with a website design software

I'm running Snow Leopard Server on my Mac Mini-We've decided to take our website in house, and have set it up on the server. The site was created by someone for us and is in HTML files. Is there software that came already on our server that will permit us to edit the files, or do we have to buy additional software? I don't see iWeb on our server. Thanks.

iWeb works, but many sites will find it limiting (eg: no imports) or will outgrow it.
The typical evolution is from static HTML web pages and CSS and such along to some sort of web content management system (CMS). That might be home-grown, open-source, or commercial, and most of the CMS packages can be "themed" to present a particular appearance. Static HTML doesn't scale, and gets fussy to manage.
If static HTML is your chosen path, then Web (HTML) editors are widely available, and do get discussed here on occasion. Some that are mentioned include Adobe Macromedia Dreamweaver, RapidWeaver, Webacappella, Freeway, etc. (Google for details, reviews, trials, etc)
Migrating your server in-house means maintaining the server and its security, keeping any CMS you pick current, and getting DNS and some other pieces in place, and run-of-the-mill stuff like regular backups and monitoring disk space, and dealing with the usual network and hardware errors.
One of the other options (as differentiated from operating fully in-house) is to host your web site and related pieces on one of various hosting providers. (That outsources a bunch of the "fun" here, and usually for little money.)

Help with CF9 Standard Install and Mac OS Server (Snow Leopard Server)

Hello,
I recently purchased a mac mini server (with snow leopard server) and will be using it to host my CF9 applications. This install is WAY different than the install needed on a windows machine. I tried to install it once and somehow hosed up Apache and now I can't even get it to start up (apache). So I am having the colo company to do a full restore of the server and I took notes on the Mac Server install and below is the questions I have.
1.) Since Snow Leopard Server comes with Apache webserver, it is what CF wants to use. This is fine, I just need to know where these things are...
It is asking for the Configuration Directory: I'm guessing it is /private/etc/apache2 ? Right or Wrong???
2.) It is asking for Directory and file name of server binary: It currently defaults to /usr/sbin/httpd is this right or should I point it to another directory?
3.) It is asking for Directory and file name of server script: It currently defaults to /usr/sbin/apachectl is this right or should I point it to another directory?
It also wants the location where I can place the CFIDE. Can I place this anywhere I wish or is there a preferred location to point this to?
and finally, I have CF9 Standard, so on the mac server should I install it as a server configuration (self contained instance) or Enterprise Multiserver config. I was reading online that its better to install as an Enterprise Multiserver setup, but I don't know if this will work for me since I'm useing the standard edition.
Please Help ANYONE, if you have mac os experience and installing CF9 onto a mac server
Thanks

I have been getting this exact same problem. CF installer is somehow writing some invalid information into the httpd.conf file. I was able to replace the httpd.conf file with the default one, and was able to go through the webconnector process again and (sometimes randomly) it works. I also spent about 4 hours on the line with adobe CF support and made no progress beyond what I'll post here .
To answer your questions about file locations:
/private/etc/apache2/ for the httpd.conf files
/usr/sbin/ for both the apachectl and the httpd binaries
Although I'm able to get past where you are, and it seems to work correctly, Immediately upon adding a new site via server admin it all breaks. Coldfusion then will only work if I manually go to a cfm document. For example: http://example.com/ will give me the raw text from the (default index) index.cfm file. But typing http://example.com/index.cfm works.
I am lost here as well. After 4 hours on the phone with adobe support I would have hoped it would be an easy fix. I've completely nuked and reinstalled the server from scratch with the exact same results both times.
Does anyone have the slightest clue about what may be going on here?

Can I use Snow Leopard Server with Windows clients?

Mainly for e-mails and calendars. I have small office with 12 windows computers from XP to Win 7 and MS Office from 2003 to 2007. Will Snow Leopard Server work with that?

Can Mac OS X Server do this? Sure.
You're going to be learning a whole lot about running a server, regardless.
You really need to sort out what you have here and where you want to be, and how to upgrade or replace yor migrate your environment, and before you add the substantial increase in complexity of serving Windows from Mac. If you can't get off of Office circa 2003 or similarly old software, what are you going to do when you find, say, an incompatibility, or a need to migrate mail clients? Who are you going to call for help?
I'd guess that Small Business Server (SBS) is likely your best target here.
AFAIK, Exchange Server (which I'm guessing is what you're using) supports larger mailboxes in newer releases.
Look at the sustaining costs for what you're considering purchasing, too. How much it'll cost to configure, deploy and maintain the box and the network. Up-front costs are an obvious consideration, but maintaining many boxes and many versions itself introduces costs.
The arrival of Lion Server next month does not change my opinion. (And I'm not usually suggesting Windows and Windows Server boxes, either.) (And with the arrival of Lion and Lion Server, I'll follow my usual approach and not look to upgrade to the first release of that (or any other) new platform, if there are business-critical functions and services involved. You need time to debug and test the deployment.)

Snow Leopard Server VPN and other Servers

I am thinking of deploying Snow Leopard Server at work using the Mac MiniServer option. We have a few Macs that we would like to manage their settings with. We also have Active Directory. I plan to use Open Directory with the Mac then use kerbos for logins.
My question is if I use the Snow Leopard Server VPN with the Macs, will the users be able to access other resources on the LAN like Active Directory Shares, Exchange, and internal Intranets? Or only the Snow Leopard Server?
Thanks,
WillGonz

It sounds like you will have 2 different kerberos realms, one in OD and one in AD.
If you want them to use the same realm (the AD one) you need to look at a "golden triangle" setup.
If you want to authenticate the VPN connection using Kerberos I suspect you need to be able to reach the KDC server from Internet before the VPN is up. That would mean it needs to have a public IP and same name as on the LAN(?).
As an alternative a Radius connection for the VPN authentication from the Mac to an AD/Radius server might be possible.

TS2959 Snow Leopard Server "invalid serial number" due to bridged ethernet

Help,,
Snow Leopard server continues to claim "invalid Serial number"
due to bridged ethernet. (It is valid when I unbridge..invalid when I bridge,)
Apple claimed to fix this bug here
http://support.apple.com/kb/TS2959
But has not.
I need bridged ethernet for multiple servers within virtualbox.
Any ideas?

You'll want to figure out why you have both 10.0.2.2 and 192.168.1.113 addresses here for the same host (and particularly where the host doesn't know about the second and separate subnet as "itself"); that's incorrect, and that's the likely trigger.    I'm guessing there's NAT here, and NAT gets ugly in general.
This isn't so much a problem with Apple's serial number licensing, it's with the disparate addressing configuration combined with a NAT "device" that's also passing Ethernet multicasts.   Taken together, you're seeing exactly what is expected with that. The OS X Server licensing is doing exactly what it should be doing.
What's happening is that the network configuration error here means that OS X Server is detecting itself via a typical Ethernet multicast, and with a different NAT'd address that it doesn't recognize as its own; as being itself, via a NAT.   Other stuff that uses Ethernet multicasts, too, so protocols including Bonjour will likely be cranky within this configuration, too. DNS, as was mentioned earlier, must also be configured for this; if you have a host with its own self-IP and visibility to a NAT'd IP visible, then DNS will get cranky. Security, too, will get cranky when DNS is cranky. And Open Directory, being based on DNS and IP and security, will very likely get confounded, too.
You can either block the Ethernet multicasts from crossing at the NAT device (which is what a NAT firewall does), or can switch to a routed network configuration and get rid of NAT (which is what a router and IP subnet routing does).
And irrespective of the rest of the discussion around licensing and multicasts, having anything in 192.168.1.0/24 is a bit messy, if you're planning on getting VPNs involved. Using another subnet (in this case) within the 10.0.0.0/8 block would be a better choice, rather than 192.168.0.0/24 or 192.168.1.0/24 subnets.

Setting up Snow Leopard Server with Address Book, iCal for Small Business

Hello Folks,
I have a small business with 2-3 people and I want to setup Snow Leopard Server on a Mac Mini. I have everything in place, RAID, Backup drive etc.
What I need is a guide on how to setup the server correctly and how to setup Address Book Server, iCal Server, DNS, etc. I was in IT a long while back but have gone back to my creative roots and sworn off IT but I am in a situation where my IT guy's wife is pregnant so he is busy painting the baby's room, etc.
I was looking at Snow Leopard Server for Dummies and a few other books. Do you guys have any suggestions on resources for me to read or research that would give me very straightforward steps in getting this setup. I am at a point where I can re-install from scratch if needed.
For the ease of those that might respond let's assume I know my way around Mac and general networking as a whole.
Thanks in advance for any advice.
Cheers,
Jason

Hi Guys,
First of, I will give you a brief background on me regarding networking as a mac user since 1994. I can setup and network multiple macs without a server in our home and small office. Turning file, print and internet sharing with a regular Mac OS X client version at no problem at all. This would be my first time setting up a Mac OS X Snow Leopard Server.
I'm in the same boat as Jakekub but we do not have a static IP from our DSL provider. We just bought a Mac Mini Server for our small office with 3 iMacs and 1 MacBook. We will just use the server for internal usage and to centralized things out and use some of server's features like Address Book, Mail, iCal etc. I've search the forums and found Orhidy's post here:
http://discussions.apple.com/thread.jspa?threadID=2148553
I even followed the sample IP Address, Subnet Mask, Router, DNS Server and I think I had it correctly setup initially. And I think I got it all running on the basic setup base on his instructions. So I tried to test my DNS settings via Terminal > hostname then got answer as
servername.companyname.private
And double checking DNS again with a command: sudo changeip - checkhostname and was given an answer of:
Primary address = 192.168.1.192
Current Hostname = servername.companyname.private
DNS Hostname = servername.companyname.private
The names match. There is nothing to change
dirserv:success = "success"
But here's another one that bugs me. I tried to follow from "Mac OS X Snow Leopard for Dummies" the command line:
NSLOOKUP hostname
and got an answer of:
;; Got SERVFAIL reply from 192.168.1.192, trying next server
Server: 192.168.1.1
Address: 192.168.1.1#53
** server can't find hostname: NXDOMAIN
So does it mean that I still haven't configured my server properly?
Thank you all for the help in advance!
dive

Unable to access gateway and DNS via VPN (L2TP) with Snow Leopard Server

Summary:
After rebooting my VPN server, i am able to establish a VPN (L2TP) connection from outside my private network. I am able to connect (ping, SSH, …) the gateway only until the first client disconnects. Then i can perfectly access all the other computers of the private network, but i cannot access the private IP address of the gateway.
Additionally, during my first VPN connection, my DNS server, which is on the same server, is not working properly with VPN. I can access it with the public IP address of my gateway. I can access it from inside my private network. A port scan indicates me that the port 53 is open, but a dig returns me a timeout.
Configuration:
Cluster of 19 Xserve3.1 - Snow Leopard Server 10.6.2
Private network 192.168.1.0/255.255.255.0 -> domain name: cluster
-> 1 controller, which act as a gateway for the cluster private network, with the following services activated:
DHCP, DNS, firewall (allowing all incoming traffic for each groups for test purposes), NAT, VPN, OpenDirectory, web, software update, AFP, NFS and Xgrid controller.
en0: fixed public IP address -> controller.example.com
en1: 192.168.1.254 -> controller.cluster
-> 18 agents with AFP and Xgrid agent activated:
en1: 192.168.1.x -> nodex.cluster with x between 1 and 18
VPN (L2TP) server distributes IP addresses between 192.168.1.201 and 192.168.1.210 (-> vpn1.cluster to vpn10.cluster). Client informations contain the private network DNS server informations (192.168.1.254, search domain: cluster).
_*Detailed problem description:*_
After rebooting the Xserve, my VPN server works fine except for the DNS. My client receives the correct informations:
Configure IPv4: Using PPP
IPv4 address: 192.168.1.201
Subnet Mask:
Router: 192.168.1.254
DNS: 192.168.1.254
Search domain: cluster
From my VPN client, i can ping all the Xserve of my cluster (192.168.1.1 to 18 and 192.168.1.254). If i have a look in Server Admin > Settings > Network, i have three interfaces listed: en0, en1 and ppp0 of family IPv4 with address 192.168.1.254 and DNS name controller.cluster.
The DNS server returns me timeouts when i try to do a dig from my VPN client even if i am able to access it directly from a computer inside or outside my private network.
After i disconnect, i can see in Server Admin that the IP address of my ppp0 interface has switch to my public IP address.
Then i can always establish a VPN (L2TP) connection, but the client receives the following informations:
Configure IPv4: Using PPP
IPv4 address: 192.168.1.202
Subnet Mask:
Router: (Public IP address of my VPN server)
DNS: 192.168.1.254
Search domain: cluster
From my VPN client, i can access all the other computers of my network (192.168.1.1 to 192.168.1.18) but when i ping my gateway (192.168.1.254), it returns me timeouts.
I have two "lazy" solutions to this problem: 1) Configure VPN and DNS servers on two differents Xserve, 2) Put the public IP address of my gateway as DNS server address, but none of these solutions are acceptable for me…
Any help is welcome!!!

I would suggest taking a look at:
server admin:vpn:settings:client information:network route definitions.
as I understand your setup it should be something like
192.168.1.0 255.255.255.0 private.
at least as a start. I just got done troubleshooting a similar issue but via two subnets:
http://discussions.apple.com/thread.jspa?threadID=2292827&tstart=0

SNOW LEOPARD SERVER PROBLEMS REQUIRE CERTIFIED CONSULTANT TO HELP

I've had a pretty unstable Snow Leopard server install since it was upgraded from Leopard a few months ago. Some of the problems were said to be hardware related, but I've been unable to migrate it to a different computer (Mac Mini).
The current installation is running, albeit poorly.
We had a Mac consultant involved in these issues, but he has proven to be unstable and unreliable as well - so we're on a search for a new consultant to give us some paid assistance in straightening this thing out.
We're not on the US mainland, but can make the server accessible by ARD and/or SSH to someone.
Someone with Apple certification would be preferred.

Hi Brian,
I'm an IT consultant dealing with Mac OS Servers and Windows Servers as well as Linux. I can offer a few helpful suggestions since just recently I transferred data from a Mac OS 10.5.8 Server to a 10.6.2 Server.
My first question to you is what data are you immigrating from? example 10.5.8 Server Data to 10.6.2 server?
The reason why I ask this since IMAP data in 10.5.8 and before was using Cyrus and starting in 10.6 apple switched to Dovecot.
Initially, I did not realized that apple made the switch and had stalling problems using the apple migration tool. (Personally I don't think the tool works well since a lot of others are running into this problem when researching this issue).
In the end I decided it was best to important everything manually, mail and not use the apple immigration tool since I think it has some issues.
The first thing I would do is make sure the DNS is configure right so that the server can resolve it's name which is very important.
Hopefully you're been running Open Directory . Export the users from the old server and import it to the new 10.6.2 server.
Next transfer the IMAP mail from 10.5.8 server to the 10.6 server to the same locations.
Example in 10.5.8 server default location is
/var/imap
and
/var/spool/imap
note this is where cyrus stored imap data in 10.5.x and maybe before. I have to look at my old 10.4 server since I'll be upgrade my own server soon.
My clients Servers have been upgrade fine by doing the manual method.
anyway...
keep those two locations in mind of where you mail is stored.
next I would copy your old cyrus mail to the new server. Don't use the migration tool at all. Just setup the new server and get the DNS running so it can resolve itself before you do this.
also make sure mail server is not running and it's off.
open up a terminal window
copy and paste this but change the name of the volume/hard drive name (HD_name)
sudo /usr/libexec/dovecot/migratemaildata.pl --cyrusBin "/Volumes/HD_name/usr/bin/cyrus/bin" --database "/Volumes/HD_name/var/imap" --sourceSpool "/Volumes/HD_name/var/spool/imap" --targetSpool "/var/spool/imap/dovecot/mail"
ok do this will convert all of your cyrus mail to dovecot. Make sure you've already imported the users from Open Directory before doing this script.
after all of this
there's still one more step
for some reason the postfix "main.cf" file is configured to use cyrus in 10.6.2 update.
/etc/postfix/main.cf
you can use the pico editor if you like.
example
type in at terminal window
sudo pico /etc/postfix/main.cf
it should be near the end of the file
don't bother with anything that's in # which is ignored.
look for
mailbox_transport = cyrus
then change it to
mailbox_transport = dovecot
save the changes
edit settings in the mail server with server admin to what you had... I recommend don't importing the mail settings from the old server admin since some people reported that its better just to manually configure it.
however for other server admin settings you might try to export and import to the new server.
If you have any questions just let me know and I'm glad to help the mac community.

Snow Leopard Server DNS setup

Where is there a step by step setup for making my Snow Leopard Server with DNS? Essentially, I am looking to setup a mail server but seem to be missing what information I need to gather from the folks that host my domain and how to point traffic to my network.

When I started setting up my first Mac OS X Servers a few years ago I had to completely retrain my brain because the MacOS does not follow the traditional nomenclature of Windows Active Directory and DNS setup. That being said like AD for Windows MacOS relies very very heavily on a healthy and properly running DNS system, both internally and externally. So one great resource I found was about 10+ hours of training on Leopard Server over to Lynda.com. I think you can sign up for a month long membership but it's well worth the investment if your looking for some basics thru advanced setup of Leopard Server. Now SLS is much much easier at the setup and deployment and some of the fundamentals of the setup interface have changed greatly (as an improvement) but the videos are still very applicable.
Basically it comes down to the following steps in order to get your website/e-mail/wiki services working.
1. Purchase your .whatever with a registrar, godaddy, doster, network solutions ect...
2. Make sure you have a fully routable PUBLIC IP address from your ISP that you can assign to the WAN (internet side of your router)
3. Contact your ISP and ask then to create an rDNS entry for your .something to the IP address they assigned you. Usually this will look like xxx.xxx.xxx ---> mail.mydomain.com when you test later on.
4. Modify the DNS records with your registrar to point the MX & A record to your new IP. You will log in create an A record for mail.mydomain.com ---> xxx.xxx.xxx (your public IP on router) and then you will create an MX record for e-mail which will simply be mail.mydomain.com with a value of 10 (there is usually a screen for this).
5. Once all the DNS is setup and working properly (Can take several days for these changes to take affect and be visible by your ISP) then you can begin the configuration of your router. You will need to determine what IP internally you want your Mac to be. Usually 10.0.0.1 or 192.168.1.1 or other and document that. Program your router to port forward ports 25,110, 80, 143 to the IP that you decided your Mac will be at so those services will be publicly available to you to user. Otherwise nobody will ever be able to send you e-mail or visit your site.
6. This is a good time to check your work and settings by visiting www.mxtoolbox.com and you verify your rDNS (setup by ISP) and your DNS (Setup by you) before beginning your setup of OS X SLS. If everything checks out then start the install if not STOP HERE and fix it because it will haunt you in the long run.
7. Start the install of SLS and at some point the system will get you to the screens at which you input your domain information. If all was setup properly up to now SLS will auto-populate the domain and local hostname of your Mac Server. U can change the local hostname if you wish but the domain name information should reflect your rDNS and A record information of mail.mydomain.com and you can hit next and proceed with the rest of the install.
8. Once up and running you will need to make a small adjustment to the alias of your e-mail. For some reason the engineers at Apple left a flaw in (my opinion) that is as such. Whenever you send e-mail it will go as [email protected] instead of what you really want which is [email protected]. So follow this post below and you will be all fixed up in a jiffy.
http://discussions.apple.com/message.jspa?messageID=10110723#10110723
Hope this helps.

I'm having trouble with Snow Leopard server disconnecting.

I'm having trouble with Snow Leopard server disconnecting. Recently upgraded my laptops to latest MacBook Pro OSX Lion, but everything has been fine since December until now. I did just add a 2TB Drive to the set-up (OWC Mercury Elite AL-Pro) in a Daisy chain of 2 other 2TB drives and a 3TB Drive that had been working perfectly up until now. I was able to use it yesterday, but now it has gone haywire and I lose connections while working on files or saving files. Have to restart server and it works for a while, but then drops off. Could Server be corrupt?

Hi clemenbw,
Welcome to the Apple Support Communities!
In your situation, I would recommend reading over the attached article to help you troubleshoot your Magic Mouse Bluetooth connectivity issues.
Troubleshooting wireless mouse and keyboard issues
Have a great day,
Joe

Jetphoto Server on Snow Leopard Server - Need help.

Folks, I recently setup a machine using Snow Leopard Server and migrated our jetphoto server (http://www.jetphotosoft.com/web/?s=product_server) to this machine. I cannot get it to work. It worked perfectly on Leopard client.
I enabled my php5 module. I just don't know what to do on this one. I'd appreciate any help getting this going.
Essentially I downloaded the jetphoto server 1.3, moved the jpserver folder to the correct level of the webserver folder and attempted to load it in Safari.
All I get is:
Object not found!
The requested URL was not found on this server. If you entered the URL manually please check your spelling and try again.
If you think this is a server error, please contact the webmaster.
Error 404
lpiserver.local
Fri Apr 23 07:47:33 2010
Apache/2.2.14 (Unix) DAV/2 PHP/5.3.1

Folks, I recently setup a machine using Snow Leopard Server and migrated our jetphoto server (http://www.jetphotosoft.com/web/?s=product_server) to this machine. I cannot get it to work. It worked perfectly on Leopard client.
I enabled my php5 module. I just don't know what to do on this one. I'd appreciate any help getting this going.
Essentially I downloaded the jetphoto server 1.3, moved the jpserver folder to the correct level of the webserver folder and attempted to load it in Safari.
All I get is:
Object not found!
The requested URL was not found on this server. If you entered the URL manually please check your spelling and try again.
If you think this is a server error, please contact the webmaster.
Error 404
lpiserver.local
Fri Apr 23 07:47:33 2010
Apache/2.2.14 (Unix) DAV/2 PHP/5.3.1

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

Will Windows Outlook clients be happy with Snow Leopard Server Mail Server?

Our network at work has a Windows SBS 2003 server - and 40+ XP PCs running office 2003 (and outlook 2003).
Can I set up Snow Leopard Server so that the Outlook 2003 clients will be able to use contacts, calendars and mail etc from the mac (mini) that we would purchase for this?
I'd love to get everyone on Mac here, but we can't cos our core application is windows only and we would still need the MSSQL server. I know - we could install parallels or virtualbox for the windows apps but that is extra expense, and tbh I don't think our users could cope.
Thanks

Hi
+"Can I set up Snow Leopard Server so that the Outlook 2003 clients will be able to use contacts, calendars and mail etc from the mac (mini) that we would purchase for this?"+
For mail yes. For calendars you will need 'assistance' using 3rd-party applications or helper utilities. The iCal Admin manual has more details of what is available:
http://manuals.info.apple.com/enUS/iCalServerv10.6.pdf
Page 12. For Addresses/Contacts consult the Address Book Server Admin Manual for more details:
http://manuals.info.apple.com/enUS/AddressBkServerv10.6.pdf
Page 12. I don't see anything specifically listed so you may have to search for these yourself unless someone else posts with something more specific that works?
If you're expecting Exchange-like functionality you will be disappointed. If you really must have the functionality you're used but also want to move to the mac platform a better prospect (IMO) would be Kerio Mail Server:
http://www.kerio.com/connect
Depending on what other services you may or may not want you may not necessarily need OSX Server? Then again you could as easily install KMS on a Windows or Linux box instead. In which case why swop from Exchange?
Tony

Help - Snow Leopard Server Setup with AEBS

Similar Messages

Maybe you are looking for