Westwind Computing
 Sales Information
 Customer Feedback
Westwind Computing
[New to Westwind?]  [Customers]  [News & Information] 


AppleShare Slow Copy

AppleShare IP
  Type of Product:

Issue: Slow performance copying files

Solution: Make sure the AppleShare clinet software is current.

From Apple Tech Note #60067 - Mac OS X Server: Troubleshooting Apple File Services

If users say the server is slow:
- Make sure version 3.8.2 or later of the AppleShare client software is installed on users' computers.
- Make sure users connect to the server computer by using TCP/IP.

Question 16: How can I make sure that my AppleShare Client machine mounts my server at startup using TCP/IP?

Answer: Make sure that the "Load Only When Needed" option is unchecked in the TCP/IP Control Panel Options window.  Discard the "AppleShare Prep" file in the System folder's preferences folder. Log into the server via the Chooser again in order to recreate your startup mounts over TCP/IP. If neither of the above work, try turning on Virtual Memory.  Open Transport may not have loaded TCP/IP due to lack of memory.

Question 17: How does the AppleShare Client software decide to use AFP over TCP/IP when connecting to a server?

Answer: The AppleShare client first sends a message over to the server using AppleTalk to find out if it can use TCP/IP (this command also returns the IP address of the server). The client then uses this information to establish a connection to the server over TCP/IP. Since the client obtains the IP address directly from the server, there may be problems setting up proxy services for AFP over TCP.

From Apple Tech Note #60104 - Mac OS X Server: AppleShare Client 3.8.2 Read Me

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.

Known incompatibilities and limitations

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

My Notes:

Under the TCP/IP control panel in Mac OS 9 (and possibly earlier), you'll need to switch "user mode" to "advanced", by hitting command-U. Then press the new "Options" button, and on that panel is the dreaded "Load Only When Needed" checkbox. Turn this OFF.

With "AppleShare Client Setup" for Mac OS 7+, you can actually for using TCP/IP for transfers on the client side, which is basically always a good thing (all file accesses will be faster, from either AppleShare IP or Mac OS X Server). You can get this software from: http://asu.info.apple.com/swupdates.nsf/artnum/n10119 -- look under the "Network" panel for "Notify use if TCP connect fails", and check it. Then, if your users ever get the warning panel, you know something is misconfigured, rather than having them suffer through a slow network.

This Document Prepared By Michael on 8/2/99

Home | Specials | Products | Education | About Us | Services | Training | Support | Reference | Events | How-to
   Copyright © 2000-2004 Westwind Computing