[jcifs] Re: JCIFS 1.2.3 HTTPFilter problems with ie

[Richard Caper]

See:

http://lists.samba.org/archive/jcifs/2003-September/002500.html

IIS will intercept the NTLM header and process it before it ever gets
to the filter.  If you just need NTLM authentication and are using
IIS, you should be able to have IIS perform the authentication and
remove the filter entirely.

On 9/8/05, Fernando Hartmann <fh at sadig.com> wrote:
>         I noticed that the problem is happening when I use IIS (5 or 6) as the
> Web Server (Isapi Redirect), when I connect direct to Tomcat the
> authentication works for the two browsers (IE and FF), but over the IIS
> only the FF works !
>         There are somebody using NTLMFilter over IIS that works ?
> 
> 
> 
> 
> 
> Fernando Hartmann wrote:
> >
> >     Thanks for your response, but why the authentication works with the
> > FireFox client ?
> >     I tried with Tomcat 4.1 and 5.0 and the same happens.
> >
> >
> >
> > Michael B Allen wrote:
> >
> >> On Mon, 05 Sep 2005 14:39:24 -0300
> >> Fernando Hartmann <fh at sadig.com> wrote:
> >>
> >>
> >>>     Hello, I'm trying to use JCIFS but there are something strange
> >>> happening, when I' connect with FireFox 1.0.6 the authentication
> >>> works well, but when I use IE 6.0.2900 XP SP2, I only receive a blank
> >>> screen. I use the same user on the browser, and both are running on
> >>> the same machine.
> >>>     Any idea !
> >>>
> >>> When I try to logon with IE:
> >>>
> >>>
> >>> New data read: Transport1[vesuvio.sadig.net/10.1.1.3:445]
> >>> 00000: FF 53 4D 42 72 00 00 00 00 98 03 C0 00 00 00 00
> >>> |ÿSMBr......À....|
> >>> 00010: 00 00 00 00 00 00 00 00 00 00 76 EA 00 00 01 00
> >>> |..........vê....|
> >>>
> >>> byteCount=36 but readBytesWireFormat returned 18
> >>> 05/09/2005 13:54:48 org.apache.jk.common.ChannelSocket processConnection
> >>> INFO: connection timeout reached
> >>> java.net.SocketException: Connection reset
> >>>     at java.net.SocketInputStream.read(SocketInputStream.java:168)
> >>>     at jcifs.util.transport.Transport.readn(Transport.java:29)
> >>>     at jcifs.smb.SmbTransport.peekKey(SmbTransport.java:328)
> >>>     at jcifs.util.transport.Transport.loop(Transport.java:89)
> >>>     at jcifs.util.transport.Transport.run(Transport.java:229)
> >>>     at java.lang.Thread.run(Thread.java:534)
> >>
> >>
> >>
> >> This is a low level socket error. It looks like jCIFS can read an
> >> SMB response from the domainController. Perhaps the custom Socket
> >> implementation of your container isn't quite up to spec.
> >>
> >> Mike
> >>
> >>
> >
> >
> 
>