This section provides several ways to simplify your administration tasks and customize how Macintosh workstations interact with the network.
AFP lets you configure a guest user account through iManager.
In iManager, click the Roles and Tasks button.
For more information, see the NetIQ iManager Administration Guide.
Click Users > Create User.
Specify a user name and a last name for the user.
Specify the context for the user.
Click OK to save the changes.
The guest user is now created.
After creation of the guest user, query for the user by using the User > Modify User task in iManager.
Remove the ability for the user to change the password by clicking Restrictions, then deselect Allow User to Change Password.
Enable the Guest account by adding the full eDirectory context of the guest object to the context search file.
Click File Protocols > AFP.
Select the Allow Guest Login option and specify the name of the guest user by using the instructions in Section 6.3.1, Security and Rights
Reload the AFP server to make the Guest button available on the login screen.
To reload the AFP server through iManager, see Section 6.2, Selecting a Server to Manage.
Information about volumes is stored in the /etc/opt/novell/afptcpd/afpvols.conf file.
To edit the afpvols.conf file and store volume information:
Use a text editor to open the afpvols.conf file.
On separate lines, enter the current name of the volume and the new name of the volume, separated by a space. For example:
server1.Volume1 AFPVol1
server1.Volume2 AFPVol2
Unload and reload the AFP server by using the rcnovell-afptcpd reload command, or use iManager to reload the server.
The AFP server configuration parameters are stored in the /etc/opt/novell/afptcpd/afptcpd.conf file. After you install the AFP server, this configuration file has all the parameters, commented with their default values.
The following sample shows a typical afptcpd.conf file:
# Authentication module to use.
# It is advisable not to use - cleartext - as the option # for this. The possible options currently are: # cleartext, random random key exchange), two-way (two way random # key exchange),DHX (Diffie-Hellman exchange 2).
#
# AUTH_UAM <name>
AUTH_UAM DHX
#
# Minimum Number of threads that the daemon must always
# have waiting for work, notwithstanding the complimentary
# parameter - Maximum Number of threads (described next)
# This can not be more than MAX_THREADS parameter.
#
# MIN_THREADS <num>#
MIN_THREADS 3