Password checking problem - mixed R8/R6 environment

We have dozens of users who are getting an error when accessing our application server- “account is locked”. To fix this, we have to clear the password digest on our admin server and push the nab to the apps server.

Admin/hub server is 8.0.2 FP2

Mail servers are a mix of 8.0.2 FP2 and 6.5.6 FP3.

Admin4 is same release level as the server it resides on. Names.nsf is R8 version.

Since we migrated all applications to new servers(hardware) which run 6.5.6 FP3, users are getting the ‘account locked’ errors. We go days without the error, then we get 10-20 users in one day.

Password checking is enabled on all servers and for all users.

Clearing the password digest works, but we need to know why this is happening. I saw some old entries in the R6 forum referring to issues with R5-R6 mix, and am wondering if the same problems persist in R6-R8 environments.

Help :-))

Subject: cryptic

In the past months I saw similar pw-locks here (using 8.5.1, 8.0.2, 7.02FP2 and 6.5.5 Servers). Policy forces to change password, sometimes two installations (local and terminal server) for one user. So it may be one id is used a few days/weeks after changing pw, so message “id locked” comes up, no server access. Changing the password local (matching the newest one) seems to work, but id-file becomes not updated. Next login you have to enter the old pw. Clearing pw-check etc. in person document mostly works. But one time it didn’t. Took the id-file from terminal server session and logged in with that on a VMware station with local Notes on it. Then changed pw there and put back to terminal server.I’m just confused what’s up with that. Never saw it until the first server was up on 8.x.