ARA 1.0 Client Enabler: Read Me

This article includes the contents of the Read Me for ARA 1.0 Client Enabler software for Apple Remote Access 2.0.1 Servers which is posted on the Apple Support Online web site, Apple Software Updates page.
1.0 Client Enabler for Apple Remote Access 2.0.1 Servers

These enablers are designed for Apple Remote Access 2.0.1 MultiPort and Personal Servers. They allow those servers to accept calls for ARA 1.0 clients. They do not provide bug fixes of other enhancements. You do not need to use the enablers if no version 1.0 clients require access to your version 2.0.1 Personal or MultiPort server.

The enablers work by modifying certain of your ARA 2.0.1 server files, changing their version number to 2.0.1RevB. No changes need be made to either 1.0 or 2.0 clients. To install the enablers, simply run the appropriate enabler application on the server machine. If you want to provide 1.0 client access on a version 2.0 server, you must first install the ARA 2.0.1 upgrade before running the enabler application.

These enablers are for the nonlocalized (English-language) version only.

LIMITATIONS

MultiPort 2.0.1RevB - CLIENT 1.0 INCOMPATIBILITIES

Here is a list of the 2.0 security features that have no counterpart in 1.0 clients:

When a 1.0 client attempts to connect to a server that has 2.0-only security features in place that apply to the client's ARA account, the connection attempt is refused by the server. The client receives the following message in a dialog box:

"The connect attempt failed. Remote Access on the computer you are calling refused to connect."

The server records the following two messages in the activity log:

"Connection attempt refused."
"Caller's ARA version insufficient for security or password settings."

Note: For all of the security features just listed, if a 1.0 call is denied access and is followed by a 2.0 call to the same account, the security is handled in the standard 2.0 way. For example, say that the user's password has expired and he or she is refused access when calling in with 1.0. The next time the user calls in with 2.0, he or she will be presented with the normal password-expired dialog box.

In addition, if dial-in-and-transfer and callback-only ports are being used on the 2.0.1 MultiPort server, 1.0 clients may encounter the "The connect attempt failed╔" error message if their accounts are not set up properly for callback. The administrator should verify that a callback number is entered and checked for each 1.0 client that uses a dial-in-and-transfer port.

WARNINGS
Run the enabler application from a disk on your system and not from another system on a network. A system crash may result if you try to launch the application from a remote system.

INSTALLATION
Two enabler applications are supplied on this disk: one for the MultiPort Server (ARA MP 1.0 client enabler), and the other for the Personal Client/Server (ARA PS 1.0 client enabler). Before you launch the application appropriate for your server, you may want to back up the files that will be modified. Backup is not necessary if you have the original ARA installation floppy disks handy. If you do want to go back to the original version of the server, do not use the Installer on the disks. Instead, simply copy the files back to the Extensions folder.

On the Personal Client/Server, two files in the Extensions folder will be affected by the enabler. Their names as originally installed are:
Link Tool Manager

On the MultiPort Server, four files in the Extensions folder will be affected:
Link Tool Manager

When the enabler application runs, it will prompt you with standard file dialog boxes for the names and locations of the files to be modified.

When the enabler application exits, restart the system.
Published Date: Feb 19, 2012