User Guide

15
Instructions for the Setup Worksheet
These instructions explain the settings in the worksheet that begins on page 6.
Network services
Before installing a standard or workgroup configuration of Leopard Server, prepare network services:
 AirPort Base Station or other Internet router has a secure password and doesn’t use a default IP subnet
If you have an AirPort Base Station, configure it to use a secure password instead of the preset
administration password, which is public.
If you have an AirPort Base Station or other Internet router, and your server will provide VPN service
to users through their own base stations or Internet routers, your server and users’ computers need
to be on different IP subnets. You can avoid duplicate IP subnets by changing all the devices on your
server’s local network to use an IP subnet other than the ones commonly used by default on base
stations and most other Internet routers: 10.0.1, 192.168.0, and 192.168.1. You can simply change the
third number to something between 2 and 254, for example 10.0.9, 10.0.222, 192.168.15, or 192.168.111.
You can also use 172.16.0 through 172.31.255. In all cases, use subnet mask 255.255.255.0.
Change the IP addresses of the base station or router, its DHCP service, your server, and all other
devices on your server’s local network to begin with the three numbers of the new IP subnet you
choose. To change an AirPort Base Station’s IP address and DHCP service, use AirPort Utility (in
/Applications/Utilities/). For instructions, open AirPort Utility and then use the Help menu. For
information about configuring another router’s IP address and DHCP service, see its documentation.
 Server has a meaningful DNS name
Work with your ISP or the information technology department in your organization to assign
your server a meaningful DNS name. The server’s DNS name is the basis for the addresses of all
services that users get from the server, such as email, iChat, iCal, wiki, file sharing, blog, webmail,
and VPN. For example, if the server’s DNS name is myserver.example.com, users have email and
iChat addresses like [e-mail], and the server’s website is at
http://myserver.example.com.
 DNS server resolves server’s IP address and DNS name
If your ISP or organization provides DNS service, it needs to resolve your server’s fully qualified
DNS name to its IP address. This DNS service must also resolve your server’s IP address to its
DNS name; this is called a reverse lookup.
If you don’t want to use your server’s fully qualified DNS name for users’ email addresses, the
DNS service must also include an MX record for your server. For example, if your server’s DNS
name is myserver.example.com and you want to have email addresses like [e-mail],
the DNS service needs an MX record for your server.
If DNS service isn’t configured for your server when you set up Mac OS X Server, Server Assistant
configures your server to provide DNS service for your local network. This local DNS service has a
record for the server, and it uses the DNS name and IP address you enter during setup.
 DHCP server assigns static IP address to target server
Configure your DHCP service to assign a static IP address to your server based on its Ethernet ID
(or MAC address). If your DHCP service provider can’t do this, you can enter the server’s IP address
manually when you set up the server. Also configure your DHCP service to supply the addresses
of the Internet router and DNS name servers for your network.
 Internet connection is working
Your network’s Internet connection is working if other computers on the network can connect to
the Internet. Server Assistant will check the status of your server’s Internet connection.