Questions answered in this article:
-
Is Open Transport required on the Macintosh client?
-
Can I force an AppleTalk connection to an AppleShare IP 5.0 server?
-
Does the AppleShare Client v3.7 resolve the performance problem of earlier clients such as System Software v.7.5.3 Finder's asynchronous calls?
-
Is there a Windows AppleTalk client included with AppleShare IP 5.0?
-
Can I use a remote server alias from a Mac OS client to connect to my AppleShare IP 5.0 server?
Question 1: Is Open Transport required on the Macintosh client?
Answer: Yes. Open Transport 1.1.2 is required.
Question 2: Can I force an AppleTalk connection to an AppleShare IP 5.0 server?
Answer: Yes. Hold down the "option" key as you select the server name in the Chooser window.
Question 3: Does the AppleShare Client v3.7 resolve the performance problem of earlier clients such as System Software v.7.5.3 Finder's asynchronous calls?
Answer: Yes. The ReadMe file for AppleShare Client v3.7 details all such software improvements.
Question 4: Is there a Windows AppleTalk client included with AppleShare IP 5.0?
Answer: Yes. AppleShare Client for Windows 3.x and COPSTalk for Windows 95 are included on the Companion CD.
Question 5: Can I use a remote server alias from a Mac OS client to connect to my AppleShare IP 5.0 server?
Answer: Yes. However, the following suggestions may help ensure that the connection works properly.
- Lock the remote server's alias using the Get Info window. This ensures that the connection information is stored correctly for dial-up procedure. If you don't do this, you may lose this information and may not be able to access the remote server properly.
- Make sure that the remote server connection is not timing out before it mounts on the computer desktop. You can change the timeout length by editing the 'DATB' 1410 resource in the AppleShare file located in the Extensions folder. Apple's ping timeout has been set to 20 seconds. The timeout is measured in ticks and currently set to 1200 ticks. 60 ticks = 1 second.
Note: You assume all risks involved in editing Mac OS resources. Apple, Inc. is not responsible for any problems that can occur.
Other AppleShare IP 5.0 FAQ's can be found in the following articles: