[jcifs] Occasionally NTLM Filter fails...Please Help.
jbaker at javasystemsolutions.com
Wed May 20 11:15:23 GMT 2009
At the weekend I started a thread on the username/password problem - I
couldn't get to the bottom of it, but posted some new evidence where I could
start Tomcat and use FF, leading to successful authentication, leading to IE
working. If I tried accessing the protected resource with IE first, it
failed. I couldn't decide if this was the NtlmFilter or something deeper in
jcifs - the NtlmFilter really doesn't do an awful lot, so I was wondering if
this was a deeper problem. I concluded the pre-authentication code could be
to blame, and I thought that was not NtlmFilter specific.
On Wednesday 20 May 2009 12:08:35 you wrote:
> Hi Andrew,
> With below parameter I receive occasional credential pop windows (even
> after entering correct credentials it does not authenticate and NO the the
> account is not locked out but after 3 successive failures it locks out as
> per policy) and errors in logs (just to let you know these pop ups are
> coming up only after a recent DC refresh carried out on the site) -
> (Note - I know that I should also use jcifs.smb.client.username and
> jcifs.smb.client.password but without these parameters no issues are
> observed in other sites we support. We have plans to use these param as
> well in future but this param not being used is not the root cause here)
> With below parameters I do not see the errors -
> Below are the errors thrown in logs after successive successful
> authentication -
>false,errorCode=Logon failure: unknown user name or bad
>e,nativeOs=,nativeLanMan=,primaryDomain=] NtlmHttpFilter: <Domain
> Name>\d6ane0: 0xC000006D:
> jcifs.smb.SmbAuthException: Logon failure: unknown user name or bad
> treeConnect: unc=\\<Domain Name>\IPC$,service=?????
> sessionSetup: accountName=d6ane0,primaryDomain=<Domain Name>
> Please help.
More information about the jcifs