39468: Acronis Files Connect: Mac OS X 10.5 (Leopard) AFP issues

use Google Translate

Operating Systems: 

Last update: 13-07-2017


A number of issues have been found with the Mac OS X Leopard 10.5 AFP client. Unfortunately the majority of the issues are bugs in the Leopard client that affect connections to all AFP servers including Mac OS X servers and Acronis Files Connect (formerly ExtremeZ-IP). These client side issues were generally resolved by Apple in later versions of Mac OS X. All Acronis Files Connect specific issues are resolved in the latest versions of Acronis Files Connect. The remaining Mac OS X client issues have been filed as bugs with Apple. Details about the specific issues we discovered can be found below.


Below is the list of the known issues with the Leopard AFP client.

New behavior in Leopard

  • Cleartext passwords - Cleartext passwords are no longer enabled by default. This was done deliberately in Leopard because cleartext is insecure and is a huge security hole. Permitting cleartext passwords allows anyone to post a bogus AFP server that only supports cleartext UAM to harvest passwords. Cleartext password support can be re-enabled if someone absolutely has to have it but it is strongly discouraged.

Outstanding Issues found with Leopard client connecting to any AFP server

  • Home Directories - Some Active Directory users with AFP home directories hang at the login screen with a Leopard client but those same users have no problems when they use a Tiger client.
  • AFP Volume Search - The Leopard client only displays a subset of the files returned by the server. As a result, no search from a Leopard client to an AFP server other than Leopard server can be considered reliable.
  • List view - In a Finder window that is set to a list view, the "Kind" column only intermittently displays the Kind of a file. A refresh of the window usually causes the Kind to display properly.
  • Leopard Sidebar logins - Connecting to a server using the new Leopard Sidebar authenticates differently than using the Connect to Server menu. With the Connect to Server window, if you mount a volume using an Active Directory account, a Kerberos ticket will be auto created. If you use the Leopard Sidebar, a Kerberos ticket will not be auto created. This means that if the server is set to only allow Kerberos logins, mounting a server will fail. Finally the Sidebar seems to default to using IPv4 addresses whereas the Connect to Server window and Zidget™ default to IPv6 addresses.
  • AFP Messages - In Mac OS X 10.5.0–10.5.6, 2 minutes after mounting a volume a Leopard client stops accepting messages sent from the server. This corresponds with the crash of Leopard's check_afp process. After this process crashes no more broadcast messages are displayed on the client. Apple resolved this problem in Mac OS X 10.5.7, released May 12, 2009.
  • Permissions cannot be changed - A Leopard client cannot change permissions on a file that is on an AFP volume using the Get Info window.
  • Search failures from 10.5.6 clients - Clients issuing search requests against the root of an AFP volume will fail to find any search results. This problem only affects clients running Mac OS version 10.5.6, and with any AFP server that does not support Network Spotlight searches: Acronis Files Connect, Mac OS X Server versions 10.4.x and Mac OS X Server versions 10.5.x where Spotlight support has been disabled. More information can be found in "Related Articles" below.

Outstanding Leopard printing issues

  • PPD changes - The location of some printing related files have changed on Leopard, which can cause printers that were originally created on Tiger to fail after a Leopard upgrade. For example Hewlett-Packard printers may fail to print because they cannot find the hppostprocessing filter specified in the PPD. A workaround for this issue can be found on the Using HP PPDs with Leopard and Tiger KB article.
  • Unicode Printer Names - Leopard doesn't display the URL of a print queue in GUI if it contains Unicode characters. Nevertheless the queue will work fine.
  • Print Accounting -The user now has to manually select the Print Accounting pane in the print dialog box. This is a result of a change that Apple made which we cannot workaround.