Cause | Accounts for users that were created before Active Directory was installed are automatically generated by placing them in the 'Users' folder after installing Active Directory. However, the generated accounts do not manage the Active Directory Authentication keys required by SSO-H. Also, as a user logon name is not set, the Active Directory Authentication System of SSO-H cannot be used for authentication because user data cannot be retrieved, even if a key is generated. |
Remedy | Follow the procedure below to change the settings. Start the Active Directory management tool, "Active Directory Users and Computers." Right-click the user that failed to be authenticated. Select [Properties] from the pop-up menu that appears. Select the [Account] tab → enter a name in [User logon name] → click [OK]. Right-click the user name you changed. Select [Reset Password] from the pop-up menu that appears. Enter a new password in the [Reset Password] dialog box → click [OK]. |
Cause 1 | A host whose name cannot be resolved is set in the SRV record retrieved with automatic domain retrieval. |
Remedy | Perform the following on the DNS server to enable name resolution for the specified host. Specify forwarding settings. Add an A record. Specify secondary settings. |
Cause 2 | The specified DNS server cannot be found or communication with the server failed. |
Remedy | Confirm the network settings to see that the machine can communicate with the DNS server set on the machine, and adjust them if it cannot. |
Cause 3 | A network delay time is set. |
Remedy | Adjust the network delay time. |
Cause 1 | Name resolution cannot be performed for the domain name specified as the login destination. |
Remedy | Confirm the network settings to see that name resolution can be performed for the domain name specified as the login destination, and adjust them if it cannot. |
Cause 2 | The specified DNS server cannot be found or communication with the server failed. |
Remedy | Confirm the network settings to see that the machine can communicate with the DNS server set on the machine, and adjust them if it cannot. |
Cause 3 | Multiple domain controllers exist for managing the specified domain. In this case, authentication process may take some time to find the one to log in. |
Remedy | Confirm the domain controllers, and adjust them, if necessary. |