![]() > But for some domains, who have their own ips, a user who previously used only hist username without the part, switch to the %domain. While those products then resend the correct credentials, the failed login attempts produce Failure-level Log records and may increase the "failed logins" counter too quickly, so the account becomes "temporarily locked". > Note: Some Microsoft products send incorrect credentials when they detect that the server supports the NTLM SASL method. > CommuniGate is aware of this as they note in in the documentation. > Not really sure why Outlook 2007 doesn't like NTLM. > We too tried replacing with % without success. > If you turn up the POP3 logs to all information, you will see it try NTLM, fail, then try another method. Its game over for the account until the temporary block list timer expires. But all the failures soon reach the threshold for blocking account logins and the account gets added to the temporary block list. > Outlook 2007 tries NTLM first and fails with "incorrect username or password." Outlook 2007 will then move on to try a different method, DIGEST-MD5 in our case. > I ran into this last week with Outlook 2007 and POP3. > Users->Domain Settings (for your domain)->Login Methods. Note: Some Microsoft products send incorrect credentials when they detect that the server supports the NTLM SASL method. Not really sure why Outlook 2007 doesn't like NTLM.ĬommuniGate is aware of this as they note in in the documentation. We too tried replacing with % without success. If you turn up the POP3 logs to all information, you will see it try NTLM, fail, then try another method. Outlook 2007 tries NTLM first and fails with "incorrect username or password." Outlook 2007 will then move on to try a different method, DIGEST-MD5 in our case. I ran into this last week with Outlook 2007 and POP3. Users->Domain Settings (for your domain)->Login Methods. > the authentication/login username fixed it. > We had users being blocked due to password error. > hits this limit, the user is locked out. As soon as the users count of failed passwords > have failed the login and +1 to the password error. > the user doesn't exist so therefore it considers the to > user without the then it assumes user is in the main domain. That is why your logs are showing failed, router > credentials for Outlook, it has to try user as the login > stupid part is, it doesn't matter if you put into the logon We had a large number of POP3 clients in our companies.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |