Configuration FAQ

Where To ?

Home Page

Components
NTAccess.User
NTAccess.Groups
NTAccess.RAS
NTAccess.Permissions
NTAccess.Performance
Zaks.POP3
Zaks.Directory
Zaks.URLBuilder
Zaks.Trace
Zaks.Collection
Zaks.Shares

Documents
Configuration FAQ
Java-COM for ASP
Useful Links

Configuration FAQ
Introduction
Below are some notes, on configuration issues that i have collected, this will hopefully help you tie down any problems you currently have.

NTAccess.Permissions

NT Service Pack 4. If you have this installed then after NTAccess.permissions has changed the permissions on a directory, Windows Explorer may complain of an improper ACL. The ACL is fine, however what Windows Explorer defines as a proper ACL has changed. This is fixed in v1.3

NTAccess.User & NTAccess.Groups

If you intend to access user details or group information from the PDC, then the account running the ASP script must be domain account. This may mean changing your IUSR_xxxx account to one belonging to the domain rather than the local machine.
UserLogon in NTAccess.User, if you intend to use this to log onto the PDC with an administrative account (say to add a new user), it will appear to work, but when AddUser is called, it may fail. I am still trying to locate this one, sometimes it will work, others it fails. On some systems this appears to be caused by having the Netware Client32 Installed. Also there is a HotFix available for IIS4.0, to fix a problem where IIS can run as the wrong account, (See Microsoft Knowledge Base Article Q147222). This should be fixed in v1.41
Calls to the UserLogon function return an error "An attempt was made to reference a token that does not exist." This normally means you have configured ASP to run as an isolated process, which means ASP is now being controlled by the IWAM_ComputerName account rather than the System account. The IWAM_ComputerName account has less privileges than the system account, and this is causing the error. This can be fixed by giving the IWAM_ComputerName account the "Act as part of the O.S." privilege in User Manager. The same issue applies if you are trying to use this function from outside of ASP (say in Visual Basic, or Cold Fusion).
User properties in NTAccess.User, using the component, the restrictions placed upon user account names are those enforced by the Windows API, however User Manager has further restrictions on top of these. This means it is possible to add a new account which will cause User Manager to report errors. If co-operation with User Manager is required for your installation, it is advised that you enforce the User Manager limits before adding users with the component.