[jcifs] Re: HTTP Authentication failing

[Richard Caper]

This particular case looks to be failing to connect to the target
server on a lower level than jCIFS.  Can you telnet from the Tomcat
server to 192.168.20.101 on port 139 (i.e. "telnet 192.168.20.101
139")?  It looks to be a basic connectivity issue here (not sure about
the previous errors).  I believe the newer versions of jCIFS use
whichever of 139 and 445 is available (which may be why you are
getting different errors with 1.2.0).

> I set (within the http filter section of web.xml) the following:
> 
> >   <filter>
> >     <filter-name>NtlmHttpFilter</filter-name>
> >     <filter-class>jcifs.http.NtlmHttpFilter</filter-class>
> >     <init-param>
> >         <param-name>jcifs.http.domainController</param-name>
> >         <param-value>192.168.20.101</param-value>
> >     </init-param>
> >     <init-param>
> >         <param-name>jcifs.smb.client.domain</param-name>
> >         <param-value>mydomain</param-value>
> >     </init-param>
> >     <init-param>
> >         <param-name>jcifs.smb.client.username</param-name>
> >         <param-value>validusername</param-value>
> >     </init-param>
> >     <init-param>
> >         <param-name>jcifs.smb.client.password</param-name>
> >         <param-value>validpassword</param-value>
> >     </init-param>
> >   </filter>
> >   <filter-mapping>
> >     <filter-name>NtlmHttpFilter</filter-name>
> >     <url-pattern>/*</url-pattern>
> >   </filter-mapping>
> 
> The browser then comes back with
> jcifs.smb.SmbException: Failed to negotiate
> jcifs.smb.SmbException: Timeout trying to open socket
> java.net.ConnectException: Connection Refused: connect
>    at java.net.PlainSocketImpl.socketConnect(Native Method)
> 
> Note: This fails for all users (Not just the first)
> 
> I agree that there is something screwy with our environment - We just can't
> pinpoint it! As you can also guess, my knowledge in this area is limited!
> 
> Thanks for your patience!
> Paul
> 
> 
> 
> 
> 
> 
>