If you have upgraded the client from an older version, check the following registry key and ensure that the value it contains is in lowercase. None of the recommended solutions fixes my problem. Prior to making a bug report, we always suggest doing a clean reinstallation of the client, especially if the failure occurred following an upgrade of the client. Delete the directory tree containing the AFS client installation. When a user logs in to one machine in my Windows NT domain, AFS drive mappings work, but when they log in to a different machine in the same domain, the drive mappings fail.
Windows drive mappings follow a user from machine to machine within a domain.
The command completed successfully. Therefore, in a domain situation, it is best to use login scripts with variables, rather than allowing individuals to determine their own drive mappings. The command completed successfully. Users do not receive a token when they log in, although integrated login is configured properly. The AFS client depends upon the presence of network services.