AppleShare IP 6: File Service FAQ

Questions answered in this article:

1. Will the fastest network connection be selected between the client and AppleShare IP Server? Or will it always try TCP/IP when both TCP/IP and AppleTalk are available?
2. How does the AppleShare client know how to connect to the Server using TCP/IP?
3. Does AppleShare IP now support sharing volumes larger than 4GB?
4. Can I change the AppleShare Server's port?
5. Will my Windows clients be able to use AFP (Apple File Protocol) over TCP/IP as well?
6. Will my Windows SMB clients be able to use AppleTalk to access the AppleShare IP 6 server?
7. AppleShare IP 6 now provides support for SMB clients. Can I install PC software from the AppleShare IP server?
8. Can I access the AppleShare IP 6 server over multiple SMB subnets?
9. Why can't I see the files on the AppleShare IP server from my Win95/98 client?
10. Can Windows clients change their User password?
11. What is the Network Trash Folder?

Question 1: Will the fastest network connection be selected between the client and AppleShare IP Server? Or will it always try TCP/IP when both TCP/IP and AppleTalk are available?

Answer: The AppleShare IP file server will default to an AFP over TCP/IP connection unless it is unavailable. AFP over TCP/IP is considered the fastest connection. The client can force an AppleTalk connection as mentioned in the AppleShare 3.7 Client FAQ.

Question 2: How does the AppleShare client know how to connect to the Server using TCP/IP?

Answer: The AppleShare IP 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 now support sharing volumes larger than 4GB?

Answer: Yes. When used in conjunction with AppleShare Client v3.7 for the Macintosh client, server volume sizes are read correctly up to 4GB. If the volume is actually larger than 4GB, the volume size information shown will reflect the remaining available disk space up to 4GB. Note that this is a limitation of the MacOS system software and not AppleShare IP.

For example, if the volume is 9GB and 5.5GB of disk space is used--the Macintosh client will see 3.5GB as available. In turn, if the volume is 10GB and 5.5GB of disk space is used--the Macintosh client will only see 4GB as available, because server volume sizes are read correctly up to 4GB.

Question 4: Can I change the AppleShare Server's port?

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.

• Use the Chooser's "Server IP Address..." button to manually specify the IP address of the Server, followed by a colon and the new port number.
  For example: www.yourdomain.com:xxxx
• Change the default AppleShare port number from the Macintosh client by using a resource editor (such as ResEdit*) to alter the 'DATB' resource (ID=1407) to match that of the server's new AFP port number.

Note: The client won't be able to connect to another AppleShare IP 6 Server whose port number has not been altered, unless you manually connect via Chooser's "Server IP Address..." button and explicitly specify the port number after the "colon" notation.

Question 5: Will my Windows clients be able to use AFP (Apple File Protocol) over TCP/IP as well?

Answer: Cooperative Printing Solutions (makers of COPSTalk) and Miramar have announced product updates that will include support for AFP over TCP. Please contact these vendors for more information.

For AppleShare IP 6, set up Window File Sharing (SMB) in the Web & File Server Admin.

Question 6: Will my Windows SMB clients be able to use AppleTalk to access the AppleShare IP 6 server?

Answer: No.

Question 7: AppleShare IP 6 now provides support for SMB clients. Can I install PC software from the AppleShare IP server?

Answer: Yes, but please note the following conditional requirements:

• Hybrid Mac/PC CDs can be shared, but not all PC files will be visible. Network installs of PC software on a hybrid CD may not work.
• A PC application installer partitioned on multiple floppy disks needs to be copied and collected in one folder. Each floppy disk's content has to be in its own sub-folder inside the main folder. Share the main folder and notify clients to install the software in this manner.
• An alert may come while installing a Windows application from AppleShare IP server. It is "Can not find <drive>:\\<installer filename>. Window needs this file to run." If the name of the folder containing the installer program is more than 8 characters in length (i.e. APPLICATION INSTALLER), change it to one containing 8 characters or less (such as INSTALL).
• Some installer programs may also require that you spell out the drive and directory path to the folder. Please consult your application's installation instructions for information on how map a drive.

Question 8: Can I access the AppleShare IP 6 server over multiple SMB subnets?

Answer: A Windows NT server has to be set up to provide this multiple subnet access.

Question 9: Why can't I see the files on the AppleShare IP server from my Win95/98 client?

Answer: Windows clients should Refresh from the View menu any server folder window whose access privileges have changed since their last login into the AppleShare IP server.

Question 10: Can Windows clients change their User password?

Answer: No. The Windows client may not receive the dialog box asking the password to be changed. Do not check the box "Require new password on next log" for a new SMB User in the Web & File Server Admin.

Question 11: What is the Network Trash Folder?

Answer: The network trash folder serves the same purpose as the invisible Trash Folder at the root of a local volume. The client Finder uses it when a user puts something into the trash from a shared volume. You will have one network trash folder at the root of every sharepoint. Within that folder will be a file called Trash Can Usage Map which is used by the Finder on the client computer to claim a Trash Can #x folder to use as the trash can for the server volume.

When a client throws away a file on a remote volume the Finder tries to get a lock on the first byte of the Trash Can Usage Map. If that byte is locked, it tries to get a lock on the second byte and so on. When it gets the lock it "claims" the corresponding Trash Can folder. It then moves the file to be thrown away into its Trash Can folder. When the User selects Empty Trash, the Finder will empty its Trash Can Folder. If the client computer breaks the connection via crashing or being disconnected, the Trash Can folder will not be emptied. However when a client Finder claims a Trash Can folder, it will delete anything that was in the folder previously.

Warning: The instructions in this article refer to using ResEdit to alter your system software. Apple, Inc., is not liable for any damage done to your software through the use of ResEdit to alter the software.

This article provides information about a non-Apple product. Apple, Inc. is not responsible for its content. Please contact the vendor for additional information.

The following article can help you search for a particular vendor's address and phone number:

• Article 17159: "Locating Vendor Information"