KB Home | Users cannot log in to PaperCut web interface
If users cannot log in to the PaperCut web interface, the administrator should check the PaperCut application log for errors that could be causing the problem. If errors are occurring they should help in understanding why logons are failing.
One common error that occurs on when running PaperCut on Windows systems, is the following error:
AcceptSecurityContext failed with 80090304. Please check this user's machine logon restrictions.
This error can be caused because the user logging in was restricted so they could only “Log on to” some machines on the network. If the server running PaperCut was not in that list, then the logon would fail.
To check/fix this:
Open the “Active Directory Users and Computers” tool
Select the user that gave you the error, right-click and select Properties.
Select the “Account” tab.
Click the “Log On to” button (see below)
By default all users can log in to all computers. But if you have the “This user can only log in to the following computers” option enabled, make sure that the PaperCut server is in the list. It is safe to add the PaperCut server to this list, because you can always restrict local login access to that server using group policy.
Next click on the “Logon Hours…”. Verify the user is allowed to log on at all times.
NOTE: If you have multiple domains, you must check these settings for users on all your domains.
Changing this for the users with the problem will resolve the logon issue.
Customers have from time-to-time reported a range of similar issues, often using your favorite search engine and the error code will give you an indication as where the problem may be.
AcceptSecurityContext failed with 80090311. Please check this user’s machine logon restrictions.
Please confirm the Windows ‘Netlogon’ service is running.
Other customers have reported that disjoining the server from the domain and re-adding it fixed this issue.
keywords: authentication, invalid username and password
This release contains an updated Java version which no longer supports 32-bit workstations. If you have any 32-bit users launching the User Client or Release Station from a network share, see this Knowledge Base article for more information.