Mac OS X Server 1.x: About Apple File Services

This document contains important information about using Remote Server Administration to administer Apple file services.

This document was installed by Mac OS X Server in /System/Documentation/ReadMe. For a list of other release notes see Article 30925: "Mac OS X Server: Release Notes"
Note: This article pertains to Mac OS X Server versions 1.x, which were released prior to May 2001.

Browser compatibility issues

Issues with using Remote Server Administration

Issues with Apple file services

Do not give your server the same name as any other AppleShare or Apple file services server on the same zone of the network. Remote Administration does not warn you if you do. However, users trying to log in to the servers may be unable to log in to the server they want to use. Check the server error log (AppleFileError) for information about this problem.

You can't change access privileges for removable media. You can share folders on the removable media, but files are read-only for everyone.

If you define more than a few hundred sharepoints on the server, some sharepoint names will not appear in the client's Chooser.

Folders created by guest users are owned by "Unprivileged user" (nobody). To reassign privileges for these folders, log in to the server computer Administrator (root).

Local host information for your server computer may not be saved in the local NetInfo domain if you use Setup Assistant to choose a connection to a NetInfo parent server then turn off the connection, for example by using the Network settings panel, and you have configured DNS manually without any DNS server addresses being specified and TCP/IP to get the host name and default router automatically using Bootp. If NetInfo domain does not contain the local host name, Apple file services will not start and any applications that use the local host name will fail. If this happens, open Setup Assistant and make sure you do not have your network services configured in this way.

If Apple file services does not start when you start up your server computer or when you turn on the service using Remote Administration, check the server error log (AppleFileError) for information about startup errors.

Issue with AppleTalk configuration

If AppleTalk isn't configured correctly, it will fail when you start your Mac OS X Server but you will not receive a message about the problem. If this occurs, AppleShare clients will not be able to locate the server in the Chooser and Macintosh Manager clients will not be able to log in to the server.

Note: Because Apple file services can use TCP, Remote Administration will show that the server is running and NetBoot client computers will be able to start up

If you experience these problems, be sure AppleTalk is configured correctly using the Setup Assistant and Network Settings control panel.

If you configure more than one port on your server computer to use AppleTalk, each port must be connected to a network with an AppleTalk router. If your server computer is acting as the router, make sure it is configured correctly and does not conflict with other AppleTalk routers on the network.

Issue with the AppleShare client software

If AppleShare client computers have Mac OS 8.5 or later and AppleShare client version 3.8.1 installed, files may be corrupted in some cases when users copy files to server volumes. To prevent this, install AppleShare 3.8.2 on all the computers installed with Mac OS 8.5 or later. AppleShare 3.8.2 is provided with the Mac OS X Server software.

Published Date: Feb 18, 2012