[jcifs] JCIFS http filter problem with DC on Win 2003

Anton Dekusar adekusar at gmail.com
Fri Apr 21 14:06:16 GMT 2006

I had the same issues. But it appeared more quicker.
The final solution was to reject jcifs library, pull out classes that
represent messages from the library and make socket programming by myself.
This could be non ideal solution, but it works everytime i want it.

On 4/21/06, Inge Solvoll <inge.tapestry at gmail.com> wrote:
> I'm having stability issues with NtlmHttpFilter. The authentication works
> transparently most times for most users, but for some of them, no
> "NtlmHttpAuth" attribute is set in the session after NtlmHttpFilter has
> performed its work. On these occations, "manual" logins don't work either
> for these users, they get an exception (SmbException: Access is denied) when
> they try to manually type their username and password in the browser popup.
> A user can achieve successful logins one day, and then fail the next day.
> Any ideas? I'll try to get some more details if needed.
> I've tried some of the ideas in the FAQ:
> - Provide username/password for preauthentication
> - change the jcifs.smb.client.ssnLimit to 1.
> My setup:
> JBoss 4 on Windows 2003
> Domain controller on Windows 2003
> IE6 clients
> <filter>
>     <filter-name>NtlmHttpFilter</filter-name>
>     <filter-class>mypackage.common.filters.NtlmHttpFilter</filter-class>
> <!--  Overrides jcifs NtlmHttpFilter -->
>     <init-param>
>         <param-name>jcifs.smb.client.domain</param-name>
>         <param-value>mydomain.com</param-value>
>     </init-param>
>     <init-param>
>         <param-name>jcifs.http.domainController</param-name>
>         <param-value></param-value>
>     </init-param>
> </filter>
-------------- next part --------------
HTML attachment scrubbed and removed

More information about the jcifs mailing list