Windows Authentication

A TWAIN operation occurred during authentication.

• Make sure no other user is logged in to the machine, and then try again.

Failed to encrypt a password.

• A password error occurred.

  Make sure the password is entered correctly.

• Either [DES] or [AES] is selected for "Driver Encryption Key: Encryption Strength".

  You can make access by specifying the driver encryption key.

• A driver encryption key error occurred.

  Make sure that the encryption key is correctly specified on the driver.

The user attempted authentication from an application on the "System Settings" screen, while only the administrator has authentication privileges.

• Only the administrator has login privileges on this screen.

• Log in as a general user from the application's login screen.

An authentication error occurred because the user name contains a space, colon (:), or quotation mark (").

• Create the account again if the account name contains any of these prohibited characters.

• If the account name was entered wrongly, enter it correctly and log in again.

An authentication error occurred because the Address Book is being used at another location.

• Wait a few minutes, and then try again.

The account is locked because the number of allowed authentication attempts has reached its limit.

• Ask the user administrator to unlock the account.

Kerberos authentication failed because the server is not functioning correctly.

• Make sure that the server is functioning properly.

Due to significant numbers of authentication attempts, all resources are busy.

• Wait a few minutes, and then try again.

The SSL settings on the authentication server and the machine do not match.

• Make sure the SSL settings on the authentication server and the machine match.

The user entered sAMAccountName in the user name to log in.

• If a user enters sAMAccountName as the login user name, ldap_bind fails in a parent/subdomain environment. Use UserPrincipleName for the login name instead.

An authentication error occurred because the user name contains a space, colon (:), or quotation mark (").

• Create the account again if the account name contains any of these prohibited characters.

• If the account name was entered wrongly, enter it correctly and log on again.

Authentication cannot be completed because of significant numbers of authentication attempts.

• Wait a few minutes, and then try again.

• If the situation does not improve, make sure that an authentication attack is not occurring.

• Notify the administrator of the screen message by e-mail, and check the system log for authentication attack potentials.

The UserPrincipleName (user@domainname.xxx.com) form is being used for the login user name.

• The user group cannot be obtained if the UserPrincipleName (user@domainname.xxx.com) form is used.

• Use "sAMAccountName(user)" to log in, because this account allows you to obtain the user group.

Current settings do not allow group retrieval.

• Make sure the user group's group scope is set to "Global Group" and the group type is set to "Security" in group properties.

• Make sure the account has been added to user group.

• Make sure the user group name registered on the machine and the group name on the DC (domain controller) are exactly the same. The DC is case-sensitive.

• Make sure that "Use Auth. Info at Login" has been specified in "Auth. Info" in the user account registered on the machine.

• If there are more than one DCs, make sure that a confidential relationship has been configured between DCs.

The domain name cannot be resolved.

• Make sure that DNS/WINS is specified in the domain name in "Interface Settings".

Cannot connect to the authentication server.

• Make sure that connection to the authentication server is possible.

• Use the "Ping Command" in "Interface Settings" to check the connection.

A login name or password error occurred.

• Make sure that the user is registered on the server.

• Use a registered login user name and password.

A domain name error occurred.

• Make sure that the Windows authentication domain name is specified correctly.

Cannot resolve the domain name.

• Specify the IP address in the domain name and confirm that authentication is successful.

  If authentication was successful:

  • If the top-level domain name is specified in the domain name (such as domainname.xxx.com), make sure that DNS is specified in "Interface Settings".

  • If a NetBIOS domain name is specified in domain name (such as DOMAINNAME), make sure that WINS is specified in "Interface Settings".

  If authentication was unsuccessful:

  • Make sure that Restrict LM/NTLM is not set in either "Domain Controller Security Policy" or "Domain Security Policy".

  • Make sure that the ports for the domain control firewall and the firewall on the machine to the domain control connection path are open.

• Under Windows 7/8/8.1, if the Windows firewall is activated, create a firewall rule in the Windows firewall's "Advanced settings" to authorize ports 137 and 139.

• Under Windows XP, if the Windows firewall is activated, open the properties for "Network Connections", and then click "Settings" on the "Advanced" tab. On the "Exceptions" tab, specify ports 137 and 139 as exceptions.

• In the Properties window for "Network Connections", open TCP/IP properties. Then click detail settings, WINS, and then check the "Enable NetBIOS over TCP/IP" box and set number 137 to "Open".

Kerberos authentication failed.

• Kerberos authentication settings are not correctly configured.

  Make sure the realm name, KDC (Key Distribution Center) name, and corresponding domain name are specified correctly.

• The KDC and machine timing do not match.

  Authentication will fail if the difference between the KDC and machine timing is more than 5 minutes. Make sure the timing matches.

• Kerberos authentication will fail if the realm name is specified in lower-case letters. Make sure the realm name is specified in upper-case letters.

• Kerberos authentication will fail if automatic retrieval for KDC fails.

  Ask your service representative to make sure the KDC retrieval settings are set to "automatic retrieval".

  If automatic retrieval is not functioning properly, switch to manual retrieval.

Authentication timed out because the server did not respond.

• Check the network configuration, or settings on the authenticating server.

The authentication server login name is the same as a user name already registered on the machine. (Names are identified by the unique attribute specified in LDAP authentication settings.)

• Delete the old, duplicated name, or change the login name.

• If the authentication server has just been changed, delete the old name on the server.

Authentication failed because the user name contains words that cannot be used by general users.

• Do not use "other", "admin", "supervisor" or "HIDE*" in general user accounts.

An authentication error occurred because the Address Book is being used at another location.

• Wait a few minutes, and then try again.

Authentication failed because no more users can be registered. (The number of users registered in the Address Book has reached its maximum.)

• Ask the user administrator to delete unused user accounts in the Address Book.

An authentication error occurred because the Address Book is being used at another location.

• Wait a few minutes, and then try again.

Automatic user registration on the server failed when an access from the client using the Central Address Book Management function was authenticated.

• Check the network connection between the client and the server.

• Users cannot be registered while the address book on the server is being edited.