Mac OS X Server 1.x: AppleShare Client 3.8.2 Read Me

Note: This article pertains to Mac OS X Server versions 1.x, which were released prior to May 2001.

Introduction

AppleShare 3.8.2 is the latest version of AppleShare client software. This document provides important information about using the AppleShare client software.

Requirements for using the software

• System software version 7.6 or later
• Open Transport version 1.1.2 or later

To use AutoRemounter on a PowerBook with AppleShare client version 3.8.2 on systems earlier than Mac OS 8.5, you should use AutoRemounter version 1.3, which is available in Mac OS 8.1. If you are using Mac OS 8.5, open the Energy Saver control panel and click Advanced Settings, then select the network connections options you want to use.

The version of the AppleShare client software you use depends on the version of the system software you have installed on your computer:

• For Mac OS 7.5.1 or earlier, use AppleShare Workstation version 3.5.
• For Mac OS 7.5.1 up to (but not including) version 7.5.3, use AppleShare Workstation version 3.6.5.
• For Mac OS 7.5.3 up to (but not including) version 7.6, use AppleShare client version 3.7.4.
• For Mac OS 7.6 and later, use AppleShare client version 3.8.2.

Installing the AppleShare client software

To install the AppleShare client software, double-click the Installer and follow the onscreen instructions.

The AppleShare Client Installer places the AppleShare Chooser extension in the Extensions folder (in the System Folder) appropriate for the localized version of the Mac OS installed on your computer.

If you want to connect to AppleShare servers using TCP/IP, make sure that the TCP/IP control panel is set up correctly.

Changes with AppleShare client software version 3.8.2

• Improves performance when connecting to a Mac OS X Server computer.
• AutoRemounter now recognizes the most recent PowerBooks.
• The client software works correctly with AutoRemounter version 1.3.
• Dialog boxes are centered correctly if you have more than one monitor.
• Aliases to servers mounted using an AppleTalk connection will not switch to a TCP/IP connection. If you want a server alias to open a TCP/IP connection, you must mount the server using TCP/IP then create an alias.
• You can now cancel when you attempt to log in to a server.
• The client software now provides a transport independent UAM (User Authentication Module) interface. This allows UAM plug-in modules to connect to servers using AFP over TCP/IP. Contact your UAM vendor for a new version of your UAM that works with this interface. Existing UAMs will still work.

Using the new features of the AppleShare client software

The AppleShare client software now automatically connects to a server using TCP if a user chooses an AppleShare IP file server that is set up for TCP connections. If you want to use AppleTalk to make the connection, press the Option key and double-click the name of an AppleShare IP file server in the Chooser.

When you want to use TCP to connect to an AppleShare IP file server that does not appear in the "Select a file server" list in the Chooser, click the Server IP Address button. When you click the Server IP Address button, a dialog box appears in which you can type the DNS name (such as shasta.acme.com) or the IP address (such as 172.16.156.52) of the AppleShare IP file server .

If the AppleShare IP file server is on a computer behind a firewall, you can connect to it by adding a colon (:) and the TCP port number (the default is 548) to the IP address or DNS name.

Known incompatibilities and limitations

• If you have problems using AppleShare client software version 3.8 to connect to an AppleShare IP file server, use MacTCP Ping (available from Apple Computer) to make sure that you can ping the server computer. If you can't ping the server computer, there is a connectivity problem. Check the network cables and the configuration of the TCP/IP control panel.
• If a computer has Mac OS version 8.1 or earlier installed and a user connects to a volume on an AppleShare IP server using TCP/IP, AppleTalk must be active on the user's computer to make an alias to that volume.
• In AppleShare IP version 5.0, the Web & File Server uses a set of access privileges based on combinations of the original access privileges (See Files, See Folders, and Make Changes). The new privileges are Read Only, Read & Write, Write Only, and None. When you connect to an AppleShare IP file server volume and choose Sharing from the Finder's File menu, the dialog box that appears displays the original AppleShare access privileges. If you use the dialog box to change a folder's privileges to a combination of privileges that is invalid for the AppleShare IP file server, the file server automatically applies the most secure access privileges that approximate the privileges you selected. If you close the dialog box and choose Sharing again, the selected privileges may be different than those you selected. In Mac OS 8.0, the Sharing dialog box uses the AppleShare IP access privileges.
• Some older versions of HyperCard XCMDs that mount AppleShare volumes are incompatible with this version of the AppleShare client software.
• Microsoft Office Manager causes the AppleShare client version 3.7 to crash when you try to connect to an AppleShare file server. To correct this problem, install Office Manager Updater, available from Microsoft.
• Versions of the Novell NetWare User Authentication Modules prior to version 5.11 are incompatible with AppleShare client version 3.7 and later. Contact Novell for an update of the modules.
• Utilities that mount disk images from AppleShare file servers may have problems with the AppleShare client version 3.8.2. If you have problems, contact the developer for a new version of the utility. Apple Disk Copy version 6.3.1 or later is compatible with the new version of the AppleShare client software and is the only application for mounting disk images that Apple supports.
• Server management applications that mount AppleShare volumes may have problems with the AppleShare client version 3.8.2. Contact the developer for an update of the application.
• If there are volumes set to mount at startup and the server administrator disables the "Enable users to save password for automatic log on" checkbox in Web & File Admin, you will be unable to change the startup mounting settings for those volumes. If this happens, throw away the AppleShare Prep file in the Preferences folder (in the System Folder) and use the Chooser to reselect the server volumes you wish to mount at startup.
• To allow mounting volumes when you start up your computer using a TCP/IP connection, be sure to delete the AppleShare Prep file in the Preferences folder, and use the Chooser to reselect the volumes you wish to mount at startup. Doing this saves the TCP address of the server in the AppleShare Prep file.
• If you are having problems mounting volumes when you start up your computer using a TCP/IP connection, try setting TCP/IP to always load. If that doesn't work, try turning on virtual memory using the Memory control panel.
• If you mount a volume automatically at startup and the server software is a version prior to version 5.0, on upgrading the server to version 5.0 or later you should throw away the AppleShare Prep file and use the Chooser to reselect the server volumes you wish to mount at startup. This will prevent problems with server volumes mounting twice.
• If you are receiving "Server not responding" errors when connecting to the server using TCP over PPP, use the AppleShare Client Setup utility (available on the Apple Support Web site at www.apple.com/support) to increase the TCP Lookup timeout from 20 seconds to the time it takes the PPP link to connect plus 20 seconds.
• If the Chooser waits 2 minutes when you connect to a server using TCP, use the AppleShare Client Setup utility (available on the Apple Support Web site at www.apple.com/support/) to reduce the TCP Connect Timeout from 120 seconds to 20 seconds. Reducing the TCP Connect Timeout may make connecting to AppleShare servers over the Internet impossible.
• If you have TCP/IP set to use PPP to connect to a server and you open an alias to an AppleShare IP server (or any other server that supports AFP over TCP/IP), the AppleShare client software will try to connect using TCP/IP first before using AppleTalk. If you do not want this to happen, you can use the the AppleShare Client Setup utility (available on the Apple Support Web site at www.apple.com/support/) to disable TCP/IP support in the AppleShare client.
• If you have an alias to a server that supports AFP over TCP/IP, and the server is behind a firewall that doesn't allow pings to go through, you will not be able to connect via the alias unless you use the AppleShare Client Setup utility (available on the Apple Support Web site at www.apple.com/support/) to disable address verification via pings.
• If you have a Global Village 56k Flex Modem card and you are using PPP version 1.0.1 to connect to your Internet service provider (ISP) using TCP/IP, you need to disable the modem software's menu bar status indicators or open PPP to connect to your ISP yourself, before using the Chooser to connect to an AppleShare file server over TCP/IP.
• If the Chooser hangs after you click the OK button in the volume dialog box, try disabling the Apple Menu Options control panel.
• If you open a TCP/IP connection to a server that is behind a firewall or other device that performs network address translation, aliases to volumes on that server may not work because the IP address that the server sends to the client software may not be an address the client can use to connect to the server.