![[Return to Library]](../books.gif)
![[Contents]](../toc.gif)
![[Previous Topic]](../prev.gif)
![[Bottom of Topic]](../bot.gif)
![[Next Topic]](../next.gif)
![[Index]](../index.gif)
This section contains important information about the AFS Light component of AFS for Windows, version 3.6. AFS Light provides access to the AFS filespace from a PC running Windows 95 or Windows 98, enabling users to manage files and directories in AFS. AFS Light accesses the AFS filespace via an AFS Client machine that is configured as an AFS Light Gateway.
Your system must meet the following hardware, software, and administrative privilege requirements to install AFS Light.
The hardware requirements for installing AFS Light are:
The software requirements for installing AFS Light are:
| Note: | The AFS Light Gateway must be enabled on a Windows NT machine running the AFS Client, version 3.5 or version 3.6. AFS Light accesses AFS through the AFS Light Gateway. See Accessing AFS via the AFS Light Gateway for more information. |
No administrative privileges are required to install and configure AFS Light.
This section highlights important general information about the AFS Light component of AFS for Windows, version 3.6.
AFS Light accesses the AFS filespace through an AFS Light Gateway. In order to use AFS Light, you must have at least one machine in the same domain as the AFS Light machine running the AFS Client for Windows, version 3.5 or the AFS Client for Windows, version 3.6.
In order for an AFS Light user to access a cell, an entry for the cell must exist in both the AFS Light cell database (afsdcell.ini file) and the AFS Light Gateway cell database (afsdcell.ini file).
AFS Light must be able to resolve the name of the gateway machine in order to communicate with the gateway machine. The name of the gateway machine is the gateway's NetBIOS service name, in the form mach-afs, where mach is the host computer name up to a maximum of 11 characters. Name resolution can be achieved by adding the gateway's NetBIOS service name to the client's LMHOSTS file or to the appropriate DNS or WINS servers. If the AFS Light machine and its AFS Light Gateway machine reside on the same subnet, then name resolution succeeds automatically via a NetBIOS broadcast.
Once configured as an AFS Light Gateway, your AFS Client machine must be able to authenticate AFS Light users in a Windows context. This authentication can be achieved via a domain user account or via synchronized machine user accounts. A domain user account is a user account in a Windows domain. A machine user account is a user account that is valid only on a particular host machine.
When the AFS Light Gateway is configured into a Windows domain, an AFS Light user must log onto either a domain user account in the domain to which the gateway belongs or a machine user account with the same username and password as that of a domain user account in the gateway domain.
If machine user accounts are employed, then these accounts must be synchronized on the AFS Light Gateway and AFS Light machines. A user must log onto an AFS Light machine with the same username and password as that of a machine user account that is defined on the AFS Light Gateway machine.
The use of domain user accounts is recommended to simplify administration.
To run AFS Light on a Windows 95 machine, you must install the Windows Sockets 2 update if it is not yet installed. This update is available for download from the Microsoft Web site.
When installed on a Windows 98 system, AFS Light includes administration-oriented command suites such as bos, kas, vos, and pts. Execute the commands within these suites from the Windows Command Prompt. The command suites are not available when AFS Light is installed on a Windows 95 system.
The AFS for Windows software must be installed in a directory whose path contains only ANSI characters, for example the default directory C:\Program Files.
AFS Light for Windows occasionally creates temporary files. To control where such files are created, set your environment variable (TMP or TEMP) to the fully qualified path of the preferred temporary directory. If you do not specify a temporary directory, then any temporary files are created in the current working directory of the process that creates the files.
AFS provides national language support for the AFS Light graphical user interface (GUI) tools and documentation, including support for bidirectional scripts (Hebrew, Arabic, etc.). The language strings installed are determined by your machine's system default locale, as specified in the Control Panel's Regional Settings Properties dialog box. If no language strings exist for the current locale, then English language strings are installed by default.
| Note: | The system default locale for a machine can be different than the user locale (specified by a user) on the machine. However, the language strings installed with AFS for Windows are always determined by the system default locale. |
When an AFS user password is changed from a Windows system, the kpwvalid program is not used to check the quality of the new password. (On UNIX systems, if a kpwvalid program exists in the same directory as the kpasswd program, the kpwvalid program checks the quality of every new user password.)
This section briefly describes the known limitations and restrictions in the AFS Light component of AFS for Windows, version 3.6.
The Simplified Chinese version of Microsoft Windows 98 does not support encryption, which is needed to transmit AFS passwords from AFS Light to the AFS Light Gateway. In order for AFS Light users to obtain AFS tokens when using the Simplified Chinese version of Microsoft Windows 98, encryption in AFS must be disabled.
To disable encryption in AFS, add the following line to your Windows Autoexec.bat file:
set AFS_RPC_ENCRYPT=OFF
Note that disabling encryption introduces a potential security risk because AFS passwords are transmitted to the AFS Client Gateway in an unencrypted form when tokens are obtained.
Symbolic links to directories are treated as directories, and symbolic links to files appear as files in Windows 98 and Windows 95 systems. Neither appear as symbolic links.
Currently, you cannot use the Windows interface (the Windows Explorer, for example) to delete symbolic links or create symbolic links in the AFS filespace. If you attempt to delete a directory that is a symbolic link using the Windows interface, the directory's contents are deleted. The directory itself is not deleted. If you attempt to delete a file that is a symbolic link using the Windows interface, the link is removed, rather than the target file.
To create and delete symbolic links to AFS files and directories, use the symlink.exe program that is provided with AFS for Windows, version 3.6. Execute symlink commands from your Windows NT Command Prompt.
![[Top of Topic]](../top.gif)