Configure Joomla on Leopard Server

I just recently found out about Joomla and I really like what I see and what I can do for my website. I know my way around Leopard Server very well, except the command line (FYI). I want to configure Joomla 1.5.8 on Leopard Server 10.5.5. I currently have AFP, DNS, MySQL, Open Directory, and Web configured up and running. My site and the Wiki server is functional and works fine.
I already downloaded Joomla and placed it in Macintosh HD/Shared Items/Sites/joomla_1
It would be great if someone could guide me to configure this with my server. I have read some articles and it says I need to configure this with MySQL and PHP, and I don't have the slightest clue on how to do this. I would also like my server to be able to host multiple Joomla sites if possible (multiple MySQL databases). Sorry for being such a newb at this, but I am learning. Any help would be more than appreciated.

Just follow the joomla install guide that they provide, and follow the step by step web installer and point it at your mysql installation. Joomla 1.5 rund beautifully on Mac OS X Server. My joomla 1.5 site www dot 928 dot org dot uk is on an Xserve on 10.5.6

Similar Messages

OD / AD / Magic Triangle configuration in Snow Leopard Server

Hi:
I'm working on training / setting up a magic triangle. I've been able to perform the necessary binding of my 10.6.4 Server to the AD, Set up OD as an OD Master connected to AD and finally, binding a client 10.6.4 Mac to both AD and OD. FYI - I'm using the Apple Training Series: Macs OS X Directory Services v10.6 as my guide.
I'm running into issues which are based upon how I connect / authenticate. I tried the 4 scenarios listed below with different results. The first scenario is the way to view/administer the directories according to the training guide. I tried the other 3 scenarios just to see what might happen:
1 - local mac - run WGM and View Directories: Result: Can authenticate to AD directories, but can't authenticate to the OD directory on the OS X server.
2 - local mac - run WGM and Authenticate to OS X Server: Result: Can authenticate to OD directory on the Server, but cannot authenticate to AD directories as AD Administrator
3 - from the OS X Server - run WGM and Authenticate to OS X Server: Result: Automatically authenticate to OD directory on the Server, but cannot authenticate to AD directories as AD Administrator
4 - from the OS X Server - run WGM and View Directories Result: Automatically authenticate to OD directory on the Server, but cannot authenticate to AD directories as AD Administrator
Earlier today, while using #2 scenario, I was able to see the contents of the Active Directory and could even add computers/users to the groups I had created on the server's ldap directory and successfully tested attributes on the users/computers I assigned to the respective groups. This evening though, I can no longer see users/computers in the AD and the users I added to the OD groups have lost their connections - when I look at Members, each listing name initially shows loading then changes to not found. (The ID for each still appears though).
Any ideas? I've completely reset the server configuration for OD and its binding to the Active Directoy a couple of times now, but still can't get it working. I have the sense I've missed some detail here.
Thanks!

It sounds like you lose the AD connection intermittently from at least the server.
You are using the "AD" DNS?
Reverse lookup of the OS X server name works (OS X server name added to forward zone and IP added to reverse zone for your LAN in "AD" DNS)?
In SA, OD, Kerberos is not running (should use AD kerberos realm)?
Anything in logs about this (DirectoryService)?

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...

Mail Server and SMTP Configuration (Leopard Server)

Hello,
Our setup: Mac OS X SERVER 5.2 - LEOPARD SERVER
PowerPC G5
Orange Internet connection via a router / DHCP
We try to find such assistance in configuring your Mac book
OS Server at your service.
We set our server with a local area "domaine.intranet"
We created users with the interface, and have an address
"[email protected]."
Our messaging system works internally with the client MAIL.
We also have an Internet domain "domaine.fr", this area is hosted
In online.net.
We have personal e-mail addresses such as "[email protected]" always
Hosted by online.
We can check our e-mails via the client MAIL by IMAP.
However, we do not send emails to the outside world, and especially
"Domaine.fr" or "[email protected]."
In the console admin Server:
-- LETTERS: we have turned the SMTP protocol allowing mail
Entrant, authorizing "Relayer outgoing mail over the host:
Smtp.orange.fr "
At the tab relay, we leave the config classic 127.0.0.0 / 8
And 192.168.1.0/24.
In the history of mail, there are "postfix / postfix-7563]: fatal: the
Postfix mail system is not running, why then that the service operates on
Priori!
How can I be able to send emails to the outside knowing that we
Use addresses' [email protected]. "
Please tell us a direction to follow or procedure.
Sincerely,
ORIGINAL IN FRENCH
Notre configuration : Mac OS X SERVER 5.2 - LEOPARD SERVER
PowerPC G5
Connexion internet orange via un routeur/DHCP
Nous avons essayer de trouver cette aide à la configuration dans votre livre Mac
OS Server à votre service.
Nous avons configuré notre serveur avec un domaine local en "domaine.intranet"
Nous avons créé des utilisateurs à l'aide de l'interface, et avons une adresse
"[email protected]".
Notre système de messagerie fonctionne en interne avec le client MAIL.
Nous avons également un domaine internet "domaine.fr", ce domaine est hébergé
chez online.net.
Nous avons des adresses mail personnel du type "[email protected]" toujours
hébergé chez online.
Nous pouvons consulter nos emails via le client MAIL par IMAP.
Par contre, nous n'arrivons pas à envoyer des emails à l'extérieur, et notamment
sur "domaine.fr" ou "[email protected]".
Dans la console d'admin Serveur :
- COURRIER : nous avons activé le protocole SMTP en autorisant le courrier
entrant, en autorisant "Relayer le courrier sortant via l'hôte :
smtp.orange.fr"
Au niveau de l'onglet relais, nous avons laisser la config classique 127.0.0.0/8
et 192.168.1.0/24.
Dans l'historique de courrier, il y a "postfix/postfix-script[7563]: fatal: the
Postfix mail system is not running", pourquoi alors que le service fonctionne à
priori !
Comment faire pour pouvoir envoyer nos emails à l'extérieur sachant que nous
utilisons les adresses "[email protected]".
Merci de nous indiquer une direction à suivre ou une procédure.
Cordialement,
Message was edited by: serveurbense

Hello,
Thanks for the reply.
I modified according to your advice and tried to send mail, but it does only internally. My mail.log gives me the following information:
Apr 21 10:59:30 domaine postfix/smtp[4521]: 46D302308BE: to=<[email protected]>, relay=smtp.orange.fr[193.252.22.84]:25, delay=0.27, delays=0.05/0.01/0.16/0.05, dsn=5.0.0, status=bounced (host smtp.orange.fr[193.252.22.84] said: 554 <[email protected]>: *Recipient address rejected: Missing Authentication (in reply to RCPT TO command))*
Apr 21 11:00:27 domaine postfix/qmgr[4582]: 2147323090F: removed
Apr 21 11:00:27 domaine postfix/pipe[4608]: 022FF230937: to=<[email protected]>, relay=cyrus, delay=0.28, delays=0.01/0.04/0/0.23, dsn=2.0.0, status=sent (delivered via cyrus service)
Apr 21 11:00:27 domaine postfix/smtp[4606]: 022FF230937: to=<[email protected]>, relay=smtp.orange.fr[193.252.22.86]:25, delay=0.31, delays=0.01/0.04/0.18/0.08, dsn=5.0.0, status=bounced (host smtp.orange.fr[193.252.22.86] said: 553 <[email protected]>: *Sender address rejected: Domain not found (in reply to MAIL FROM command))*
Apr 21 11:00:27 domaine postfix/smtp[4606]: 022FF230937: to=<[email protected]>, relay=smtp.orange.fr[193.252.22.86]:25, delay=0.31, delays=0.01/0.04/0.18/0.08, dsn=5.0.0, status=bounced (host smtp.orange.fr[193.252.22.86] said: 553 <[email protected]>: Sender address rejected: Domain not found (in reply to MAIL FROM command))
Apr 21 11:00:27 domaine postfix/cleanup[4600]: 602A423094E: message-id=<[email protected]>
Apr 21 11:00:27 domaine postfix/bounce[4612]: 022FF230937: sender non-delivery notification: 602A423094E
Apr 21 11:00:27 domaine postfix/qmgr[4582]: 602A423094E: from=, size=3531, nrcpt=1 (queue active)
Apr 21 11:00:27 domaine postfix/qmgr[4582]: 022FF230937: removed
Apr 21 11:00:27 domaine postfix/pipe[4608]: 602A423094E: to=<[email protected]>, relay=cyrus, delay=0.06, delays=0.01/0/0/0.05, dsn=2.0.0, status=sent (delivered via cyrus service)
Apr 21 11:00:27 domaine postfix/qmgr[4582]: 602A423094E: removed
Apr 21 11:01:10 domaine postfix/postfix-script[4664]: refreshing the Postfix mail system
Apr 21 11:01:10 domaine postfix/master[2938]: reload configuration /etc/postfix
Apr 21 11:01:26 domaine postfix/smtpd[4516]: disconnect from domaine.intranet[192.168.1.11]
Apr 21 11:02:10 domaine postfix/postfix-script[4734]: refreshing the Postfix mail system
I am looking for solutions to correct mistakes 553 and 554, hoping that this will allow us to send mail out.
Do you have any other suggestions?
Thank you.
Bonjour
merci pour la réponse.
J'ai modifié selon vos conseils et essayé d'envoyer des mails, mais ça ne marche qu'en interne. Mon mail.log me donne les informations suivantes:
Apr 21 10:59:30 domaine postfix/smtp[4521]: 46D302308BE: to=<[email protected]>, relay=smtp.orange.fr[193.252.22.84]:25, delay=0.27, delays=0.05/0.01/0.16/0.05, dsn=5.0.0, status=bounced (host smtp.orange.fr[193.252.22.84] said: 554 <[email protected]>: *Recipient address rejected: Missing Authentication (in reply to RCPT TO command))*
Apr 21 11:00:27 domaine postfix/qmgr[4582]: 2147323090F: removed
Apr 21 11:00:27 domaine postfix/pipe[4608]: 022FF230937: to=<[email protected]>, relay=cyrus, delay=0.28, delays=0.01/0.04/0/0.23, dsn=2.0.0, status=sent (delivered via cyrus service)
Apr 21 11:00:27 domaine postfix/smtp[4606]: 022FF230937: to=<[email protected]>, relay=smtp.orange.fr[193.252.22.86]:25, delay=0.31, delays=0.01/0.04/0.18/0.08, dsn=5.0.0, status=bounced (host smtp.orange.fr[193.252.22.86] said: 553 <[email protected]>: *Sender address rejected: Domain not found (in reply to MAIL FROM command))*
Apr 21 11:00:27 domaine postfix/smtp[4606]: 022FF230937: to=<[email protected]>, relay=smtp.orange.fr[193.252.22.86]:25, delay=0.31, delays=0.01/0.04/0.18/0.08, dsn=5.0.0, status=bounced (host smtp.orange.fr[193.252.22.86] said: 553 <[email protected]>: Sender address rejected: Domain not found (in reply to MAIL FROM command))
Apr 21 11:00:27 domaine postfix/cleanup[4600]: 602A423094E: message-id=<[email protected]>
Apr 21 11:00:27 domaine postfix/bounce[4612]: 022FF230937: sender non-delivery notification: 602A423094E
Apr 21 11:00:27 domaine postfix/qmgr[4582]: 602A423094E: from=, size=3531, nrcpt=1 (queue active)
Apr 21 11:00:27 domaine postfix/qmgr[4582]: 022FF230937: removed
Apr 21 11:00:27 domaine postfix/pipe[4608]: 602A423094E: to=<[email protected]>, relay=cyrus, delay=0.06, delays=0.01/0/0/0.05, dsn=2.0.0, status=sent (delivered via cyrus service)
Apr 21 11:00:27 domaine postfix/qmgr[4582]: 602A423094E: removed
Apr 21 11:01:10 domaine postfix/postfix-script[4664]: refreshing the Postfix mail system
Apr 21 11:01:10 domaine postfix/master[2938]: reload configuration /etc/postfix
Apr 21 11:01:26 domaine postfix/smtpd[4516]: disconnect from domaine.intranet[192.168.1.11]
Apr 21 11:02:10 domaine postfix/postfix-script[4734]: refreshing the Postfix mail system
Je cherche des solutions pour corriger les erreurs 553 et 554, espérant que cela nous permettra d'envoyer des mails à l'extérieur.
Avez-vous d'autres propositions?
Merci d'avance.

DNS Configured-Best Practice on Snow Leopard Server?

How many of you configure and run DNS on your Snow Leopard server as a best practice, even if that server is not the primary DNS server on the network, and you are not using Open Directory? Is configuring DNS a best practice if your server has a FQDN name? Does it run better?
I had an Apple engineer once tell me (this is back in the Tiger Server days) that the servers just run better when DNS is configured correctly, even if all you are doing is file sharing. Is there some truth to that?
I'd like to hear from you either way, whether you're an advocate for configuring DNS in such an environment, or if you're not.
Thanks.

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.

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?

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.

I transferred files from a NAS server to the Mac Mini Snow Leopard Server and now some of the files have Custom Access and can't be opened by some users. How do I fix this?

We're setting up our Mac Mini Snow Leopard Server, and in the process transferred files that had been stored and accessed from our Blackarmor NAS server over to the Mac. These files were all created on PC's and are Office Excel files, WordPerfect files or PDF's. When you look at the files on the Mac from the Mac and bring up Get Info for the affected file, it says that the file has Custom Access. The files that work properly don't have that configuration. I can access and open the files on some computers, but some users can't open the files from their computer even though they can see it. We're all using PC's and they get the Error: Access Denied-Contact your administrator--or something similar. I've seen on the web similar issues and it may have something to do with ACL permissions. I don't know enough about Mac OS to understand this, but what is baffling is that they can be opened from some PC's but not others, and all of the Users have the same accessibility to the files. Thanks for a solution!!

Oh, on the losing Internet, try this...
Make a New Location, Using network locations in Mac OS X ...
http://support.apple.com/kb/HT2712
10.7 & 10.8…
System Preferences>Network, top of window>Locations>Edit Locations, little plus icon, give it a name.
10.5.x/10.6.x/10.7.x instructions...
System Preferences>Network, click on the little gear at the bottom next to the + & - icons, (unlock lock first if locked), choose Set Service Order.
The interface that connects to the Internet should be dragged to the top of the list.
Instead of joining your Network from the list, click the WiFi icon at the top, and click join other network. Fill in everything as needed.
For 10.5/10.6, System Preferences>Network, unlock the lock if need be, highlight the Interface you use to connect to Internet, click on the advanced button, click on the DNS tab, click on the little plus icon, then add these numbers...
208.67.222.222
208.67.220.220
Click OK.
PS. Your English is quite good & completely understandable.

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

Snow Leopard Server running extremely slow all of a sudden!!

Hi, I'm not a qualified server technician but am currently trying my best to run a server in a Secondary School! Please help, need to fix ASAP.
So basically we've got a Mac Pro running Snow Leopard server which has become incredibly slow in the past week. Nothing has changed in our department to trigger this. Here's everything I know so far...
- If I try to log on to the admin account when "Some Network Accounts Are Available", log on will take under a minute. If I try to log on to the admin account when the light goes green and "Network Accounts Are Available" log on will take forever and eventually just crash and which point I have to just force a shutdown and try again.
- When I can log on, some aspects of the computing seems fast and other aspects are really slow. For example, a few programs open as soon as I log on no problem, however a simple spotlight search or trying to open Sytem Preferences will crash the computer completely.
- Have tried booting in Safe Mode, and everything ran fast and how it's mean to but once restarting and booting normally the problems remained.
Sorry for the lack of knowledge!!
Thanks in advance.

Your comment indicates "crash the computer"? Do you mean that OS X Server itself fails, and you have to reboot? Or that the application crashes, and you have to restart it?
The following are some general approaches toward gathering some data:
Launch Console.app from Applications > Utilities and see if there are blocks of repeating errors.
Launch Terminal.app from Applications > Utilities and issue the following harmess, diagnostic command:
sudo changeip -checkhostname
After entering an administrative password and possibly seeing a one-time informational message about sudo, you should see some network configuration information and then an indication that no changes are required, or that there are DNS or network errors.
Boot from the Snow Leopard installation DVD and run a volume verification pass using Disk Utility, this from the Utilities menu of the installation disl.
FWIW...
If the applications or OS X Server are crashing, then you're generally heard toward either a reinstallation of the software, or a hardware repair, or quite possibly a combination of the two.
Forcing a hard shutdown can lead to corruptions, depending on exactly what's going on when the power drops out; that's probably best left as a last-resort approach and one best avoided.

DNS/web-server hosted off-site. How to set up Leopard server for mail?

Hey Everyone,
Brand new xserve with leopard server 10.5.2. Currently, Our web and DNS server for our domain,"company.com" is co-located off-site with an MX record of "mail.company.com" pointed at the static IP of the office where our mail server is. I want to replace the mail server with the xserve. With that in mind, how do I configure the DNS on the xserve during initial configuration to reflect that? Give it a self-referencing FQDN like server.company.office and see if the mail service can handle the domain hosted elsewhere?
I'm pretty new to servers and would love be able to keep this all in Standard but I'm not afraid to jump into Advanced if need be. I've created a test domain through GoDaddy of "company2.com" with an MX record of "mail.company2.com" pointing at the IP address of the xserve. Any help would be greatly appreciated!

Hello,
Have a look at this blog post:
http://blogs.adobe.com/captivate/2010/08/reporting-the-quiz-results-to-a-local-server.html
Lilybiri

How to resolve network issue or dns to access web page on snow leopard server?

I have my network setup like as follows:
internet > router 1 > ethernet ports > switch > router 2
I have a mac osx snow leopard server connected to "router 1", but it is so slow when accessing a web page hosted on the server from a browser on a workstation connected to either router 1 or router 2?
Is there a problem with my network setup or maybe because I changed the name to newservername.local?

@Jeff and @Camelot,
I think it is a DNS issue. I completely reset the DNS settings on server and the local name with the steps below, but now cannot access the site hosted on the server at all
I used a modified version of http://www.mkahn.com/2010/09/configuring-dns-on-mac-os-x-10-6-snow-leopard-serve r-for-hosting/ to reset the server set
1. Stop DNS Service in Server Admin
2. Close Server Admin
3. Obtain 10.6 DNS Default files (below)
4. Overwrite the DNS files with DNS Default files:
/etc/dns/loggingOptions.conf.apple
/etc/dns/options.conf.apple
/etc/dns/publicView.conf.apple
/var/named/named.ca/etc/named.conf
/var/named/named.local
/var/named/localhost.zone
5. Restart your server
All machines have 1ms ping responses within the network including this snow leopard server that I am trying to setup. There is another test web server that return pages instantly within this network so I doubt it is a network issue, but a DNS issue.

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

Can you help me solve my Leopard Server VPN madness?

Hello all,
I've been having a devil of a time getting Leopard Server's VPN service to work "properly". None of this is mission critical, as it's simply on a home system I'm using as a nat/dns/dhcp/firewall/mail/web server for my Comcast line (with a static IP). But, it is frustrating, because I currently have a 10.4.11 Server fulfilling the same roll. So it seems like Leopard should be able to be made to work. I'm gonna go step by step here with my install process in the hopes that if I'm doing something wrong someone will be kind enough to catch it. Thanks for bearing with me.
I've installed Leopard Server 10.5 (Mirror door G4, FYI) with the built-in ethernet connected to my Comcast router (with a static external IP). Immediately after 10.5 installs I restart and update everything to 10.5.2, then I install a Sonnet Gigabit NIC, it's drivers, and assign it 192.168.3.1, where it will live as my internal router, server, etc. I turn on DNS and setup an internal ".lan" zone that resolves to 192.168.3.1. Pop into Terminal and confirm that rDNS is in fact working, it is. And check that "changeip -checkhostname" resolves itself correctly (to the external IP).
Next, turn on the NAT service and run the gateway setup assistant. After a reboot I quickly check that my internal clients with static IPs (192.168.3.10, .20, etc) are working and pulling DNS OK, they are. Jump into the Firewall, and for the moment just open it wide up by accepting all connections. At various times during testing I've configured the firewall to exactly match my 10.4 Server firewall, but for the time being I can just leave it open. I create a Firewall group to cover my 192.168.3.x internal network, and another to handle 192.168.3.60/29 to handle the VPN service I'll setup in a sec. Jump over to the DHCP service where by default gateway setup creates a 192.168.1.x DHCP zone. I delete that and create a new 192.168.3.x zone covering .50-.59. Turn DHCP on and confirm it's working, good, it is.
Now, here is where the VPN fun begins. The last service I turn on is the VPN service (I've alternatively tried letting Gateway Setup activate it, and just doing it myself, with this same result). I configure it to accept L2TP at 192.168.3.60 - .63. Like I said this is a home server, so I don't need a lot of VPN connections. Finally, when I test the VPN from a 10.5.2 Client (MacBook coming in off a neighbors open wireless network with a 10.0.0.x string) I am able to connect, and I can see/ping/mount/share screen on the server. I can also ping the attached VPN client at 192.168.3.60 from the server. However, I cannot ping or see (In ARD) any other machines on the internal network from the attached VPN client. Likewise from one of the internal systems, say my Mac mini at 192.168.3.10 I cannot ping the attached VPN client at 192.168.3.60. Out of curiosity I've tried doing a rDNS lookup while attached to the VPN and the client isn't able to resolve any of the internal DNS entries.
So, what gives? As I've mentioned I have exactly this same setup working just fine with Tiger Server. Same NAT, same Firewall, same DNS, and same L2TP VPN setup. For the life of me though, I cannot get attached VPN clients to see the internal network when I put Leopard Server in place. Clearly the internal DNS isn't working for attached VPN clients, although I'm not certain if that is a cause or a symptom. I've setup a network routing definition for the internal private network, which didn't help. I also tried setting up PPTP instead of L2TP, and had the same problem.
Is anyone having similar problems with Leopard Server's VPN service? If not, could someone hit me with the clue stick and set me right? As I said, in the grand scheme of things this isn't a big deal for me. But, it's just frustrating that I can get so close to updating my home server and just fall short.
Thanks!

Your post actually contains the Key to solve the problem and there is not really a big need for going all the way to use the Property List Editor to fork around /etc/ipfilter/ipaddressgroups.plist.
There has been much written on this problem but basically you see that most is trial and error and this does include myself and my findings in this post, too, but I think I can further narrow down on what CAUSES this problem and how to fix it.
First off, we are talking a combination of using NAT (Network Address Translation - bridging an Internet connection on an external network card over to an internal network card), Firewall (which is needed in OS X to be have NAT working because the Firewall "helps" NAT by doing its job, DHCP (for providing dynamic IP addresses to clients on the internal network, don't confuse, DHCP is not providing this service to the VPN clients, that is done by the VPN server), and - last but not least - VPN to provide access to not only to the server but to any machine on the internal network over the outside network card (aka, giving remote clients a chance to connect to the local network over the public Internet in a save and nice way).
OK. The short story: you can do it ALL in Mac OS X 10.5's Server Admin tool. If it fails it is nearly always the Firewall!
You can check if this is the case for your setup by temporarily opening the Firewall up to not block any traffic: in Server Admin, click on Firewall -> Settings -> Services -> Edit Service for: any and click "Allow all trafic from "any"", save it (and to be 100% sure, stop and restart the firewall. If your clients can NOW connect at least to the server, it was the firewall. Now don't forget to switch off allowing all traffic from any, or you will be left with an open doors server ready for anybody to explore
Now what goes wrong in the first place? It appears that the GSA (Gateway Setup Assistant) that is "hidden away" in the NAT settings does something awfully wrong. It will set up all the address groups in the firewall: the any group will remain as it is usually, another one defining the internal network, and a one called VPN-net for VPN.
What it DOES do wrong here (I am no firewall expert, this is purely trial and error, so please anybody do explain!) is to give the VPN-net exactly the same address range as the internal network. And here seems to be the overall problem.
When Twintails wrote to add 192.168.3.60/27 as address range for VPN, I realized what he/she did. Writing 192.168.3.60/27 effectively narrows down the address range starting at 192.168.3.33 up to 192.168.3.62. There are millions of subnetmask calculators out on the net, give it a try e.g. here: http://www.subnet-calculator.com/
So, I looked for what range of address will actually be given out by the VPN server to VPN clients upon connections. Of course you need to make sure that this address range is NOT given out by your DHCP server.
In my setup, the server is 192.168.1.1, the DHCP server provides addresses from 192.168.1.10 up to 192.168.1.127 (I start with 10 because I have some static addresses for special purposes from 192.168.1.2 to 192.168.1.9. So, this means, anything above 192.168.1.127 is potentially "free" for my VPN connections.
Next I used the subnetmask calculator to find a narrow address group that matched my purposes. I found 192.168.1.192/26 which effectively gives me a range from 192.168.1.192 to 192.168.1.255 (which is in fact more then I have clients connecting from externally!).
I went to the Server Admin Tool, and clicked Firewall -> Settings -> Address Group and edited the VPN-net one. First I deleted what was in "Addresses in group" and entered from scratch 192.168.1.192/26. Next - just to make certain because basically this is what Twintails had in his/her post by saying to add a name String with exactly the same information - I overwrote VPN-net by 192.168.1.192/26 and saved. (I THINK that this last step might not really be needed, but I haven't tried).
Next click Save (basically it should already work, but I always want to be extra sure, so I stoped and immediately thereafter started the firewall again to be 100% certain all new rules are now active.
And now: it works! Clients can access the server AND the entire local network from remote using VPN.
One last comment: I have the feeling that (although less safe and less advanced technologicall) PPTP works much better for us then L2TP. So I have switched off L2TP support altogether because it simply NEVER really worked. We are using Mac OS X 10.4 and 10.5 to connect to the 10.5 server using this setup.

Thank you, Pterobyte: You restored my faith in Leopard Server!

I set up a new installation of Leopard Server 10.5.6 and accepted the base configuration. I wanted to test a mail server setup on VMware Fusion 2.0.2. No issues during the installation but once I started the mail services and setup my first user account, I kept getting IMAP errors in the logs.
After much searching and trying this and that, I found a post with Pterobyte's answer as seen below...I tried his recommendations and suddenly mail worked. My question is this, why would Leopard require this manual configuration/changing permissions when it clearly isn't stated in any of the manuals for mail services or anywhere else for that matter?
Lesson learned? You bet! Seeing is believing and the "It's so easy a caveman can do it" isn't quite the case with Leopard's postfix implementation. I wish Apple would fix the easy mode stuff so that it really does work as advertised. Again, I didn't alter the base installation. Love to get your feedback folks. I still don't know what went wrong but I re-installed the server 3 times and observed the same behavior.
Pterobyte's Recommendations:
Try:
sudo chown -R _cyrus:mail /var/spool/imap
sudo chown -R _cyrus:mail /var/imap
Next check if the user has the necessary access privileges in Server Admin -> "Servername" -> Settings -> Access
Then issue:
sudo postsuper -r ALL

Hmm - My test-leo-server did NOT have to have any permissions changes done - the default values from Apple was correct.
So the question is why your specific installation was bad?
As a curiosity - would these permissions be corrected by running a "Disk Utility: Repair Permissions"?
PS.: I always use the "Combo updates" when they exist, not sure if that's relevant for this secific problem…

Configure Joomla on Leopard Server

Similar Messages

Maybe you are looking for