If you are having difficulty installing iWorks 09 from the DVD, then this is what I went through to finally get it to work.

• Bought iWorks 09 from the Apple store, and they sent the software on a DVD (how retro!).
• Tried to install the software, but each time I was asked for a serial number or to install from the DVD.
• No serial number could be found on box, inside box, on disc etc. Confusion reigned.
• Figured as a trial version of iWorks was installed that perhaps my Mac was also confused.
• Removed the application from the Applications directory and removed any iWorks cache files from Library/Caches directory.
• Reinstalled and this time it crashed when loading… sigh.
• After a long search, I found a full list of what I need to delete to make sure no trace of iWorks exist (below).
• Restarted Mac, reinstalled and registered, I’m now good to go.

/Macintosh HD/Applications/iWork '09 (folder)
/Macintosh HD/Library/Receipts/iWork09* (any file in this folder that refers to iWork)
/Macintosh HD/Library/Preferences/com.apple.iWork09.plist
/Macintosh HD/Library/Preferences/com.apple.iWork09.Installer.plist
/Macintosh HD/Library/Application Support/iWork '09 (folder)
/Macintosh HD/Library/Application Support/iWork (folder--if present)
/username/Library/Application Support/iWork (folder)
/username/Library/Preferences/ByHost/com.apple.iWork.Pages.NUMBER.plist
/username/Library/Preferences/ByHost/com.apple.iWork.Keynote.NUMBER.plist
/username/Library/Preferences/ByHost/com.apple.iWork.Numbers.NUMBER.plist
/username/Library/Preferences/ByHost/com.apple.iWork.NUMBER.plist
/username/Library/Preferences/com.apple.iWork.Pages.plist
/username/Library/Preferences/com.apple.iWork.Keynote.plist
/username/Library/Preferences/com.apple.iWork.Numbers.plist
/username/Library/Preferences/com.apple.iWork.plist

[NOTE:: Not sure if it's relevant, but I used terminal to delete these files as I didn't trust Mac Finder at this stage!]

The hosts file is a plain text file that the operating system uses to link host names to IP addresses. When you are developing in a sandbox environment, you can place host names in this file to direct your browser to the IP address of your sandbox.

On your Mac OSX (10.2 or later), you can find your host file by typing…
sudo nano /private/etc/hosts

You will then need to enter your IP address and hostname…
192.168.0.1 www.magp.ie

Save the hosts file and flush the DNS.
dscacheutil -flushcache

Handy Tip: You can make aliases to save you remembering those commands, like so…
alias hosts='sudo nano /private/etc/hosts'
alias flushdns='dscacheutil -flushcache'

On a Windows box, you can find the hosts file at the path;
%systemroot%\system32\drivers\etc\hosts

Again you simply enter the IP address and host name you are using and save.
On Windows 7 and probably Vista (never had the pleasure), you will need to be an administrator to save any changes to this file. To get round this, you can simply right click on the file and change the file permissions to allow anyone to edit it (which is what I did) or you can open notepad as an administrator before opening the hosts file.

Not sure its necessary but to flush the windows DNS, you open a command prompt and type…
ipconfig /flushdns
If you are on a Windows 7/vista box, you may need to open the command prompt as an administrator.

By the way, to open an application on Windows as an administrator, you right click on the application and select the ‘Run as Administrator’.

Once you have your new private OpenSSH key, copy it to your Mac.

Open terminal, and go to your root… usually does this automatically, but type cd ~/ just in case.

Create a .ssh directory if it does not already exist and copy the private key in here.

You may need to check that the key has the right permissions, type chmod -R g0-rx ~/.ssh

Enter your ssh command, ssh username@serverhostname.com and hit enter, you should get now have a SSH tunnel to your server.

HANDY TIP: use the vvv flag to debug the ssh command  (looks odd but thats 3 v’s by the way!).

So type ssh username@serverhostname.com -vvv to receive a load of debug info that can be really useful in determining where you are screwing up.

Also I found this guide useful.