|Powered by QM on a Rpi server|
KnowledgeBase 00004: Unable to Login on Windows
Users logging in to QM over a network, including looped back to the same system, are subject to username and password authentication by Windows. There are several reasons why such logins can fail. This article describes the causes, diagnostics and fixes for login problems. Except where specific versions of Windows are referenced, information in this article should be applicable to all Windows variants.
Users running Windows XP-Home can set up their system to operate without needing entry of authentication details to use the console. Users entering the system via a network connection, however, must pass through user authentication and hence must have a valid user name and password that is known to Windows. This can be set up using the User Accounts area of the Windows Control Panel.
If your system is using domain based logins, the user name entered when logging
in to QM must be of the form
As a first step in resolving permissions related problems, ensure that all users have full access to the QMSYS account directory and all of its substructures. More precise permission settings can be implemented in accordance with the details in the System Administration section of the QM Reference Manual.
Windows has many security policy settings that impact system security. To find these:
Some key policy settings to check in the User Rights Assignment area are:
User authentication in QM is handled by the QMSvc service. Failure to login will log a diagnostic message in the qmsvc.log file in the QMSYS account directory. This message shows the IP address of the incoming connection and the Windows error number. The error code reported by Windows is not very explicit, often nothing more than "login failed" (error code 1326). This is possibly because providing detailed diagnostic codes might assist in cracking passwords. More detailed diagnostics can be obtained by enabling auditing of failed logins. To do this:
When a login failure occurs: