Question 1: Will the fastest network connection be selected between the client and AppleShare IP 5.0 server? Or will it always try TCP/IP when both TCP/IP and AppleTalk are available?
Answer: The AppleShare IP 5.0 file server will default to an AFP over TCP/IP connection unless not available. This is considered the fastest connection. The client can force an AppleTalk connection by using the method described in the AppleShare IP 5.0 AppleShare Client FAQ .
Question 2: How does the AppleShare client know how to connect to the server using IP?
Answer: The AppleShare IP 5.0 server sends its IP address to the client in an Appletalk packet when it's selected in the client's Chooser. The AppleShare client then knows to select the TCP/IP protocol for connection.
Question 3: Does AppleShare IP 5.0 now support sharing volumes larger than 4GB?
Answer: Yes. When used in conjunction with AppleShare Client v3.7 from the Mac OS client, server volume sizes are read correctly up to 4 GB. If the volume is actually larger than 4 GB, the volume size information shown will reflect the remaining available disk space.
For example, if the volume is 9GB and 5.5GB of disk space is used - the Mac OS client will see 3.5GB as available. In turn, if the volume is 10GB and 5.5GB of disk space is used - the Mac OS client will only see 4GB as available.
AppleShare Client prior to version 3.7 can only read up to 2GB for volume size. Same rule above applies for reading volume sizes.
Question 4: Can I change the AppleShare server's port? I changed the PORT resources to a range of ports made available to me by the network administrator. When I try to log into the AppleShare server via the Chooser, a 'server not responding' message is displayed.
Answer: The AppleShare client looks for the AppleTalk over TCP/IP port number to be 548. The AppleShare client won't be able to connect to the server if this is changed. There are two ways you can connect to an AppleShare server whose PORT resource has been changed.
2. Change the default AppleShare port number from the Mac OS client by altering the 'DATB' resource (ID=1407) to match that of the server's new AFP port number.
Question 5: Will my Windows clients be able to use AFP over IP as well?
Answer: Cooperative Printing Solutions (makers of COPSTalk) and Miramar have announced products update that will include support for AFP over TCP . Please contact the vendors for more information.
Other AppleShare IP 5.0 FAQ's can be found in the following articles: