[jcifs] NTLM Type 3 Message Never Sent

[Eric Glass]

Check the NtlmMinClientSec and NtlmMinServerSec registry settings on the
client:

http://technet2.microsoft.com/windowsserver/en/library/42986e7d-3468-4000-aed0-2fe1bc94548d1033.mspx?mfr=true


Eric

On 6/11/07, FrankenCoder <jmgray314 at hotmail.com> wrote:
>
>
> Interesting thought; that hadn't occurred to me. But I verified that the
> IIS
> service is stopped on the server, and Tomcat is serving things from port
> 8123. Does Tomcat have some kind of internal filtering mechanism that
> might
> be re-mis-directing things?
>
> My instinct is that the type 2 response being sent back to IE contains
> some
> invalid or unexpected format/info, but have no evidence for that. It is a
> bit mystifiying.
>
>
> Michael B Allen wrote:
> >
> > Perhaps it is being intercepted by another handler (e.g. IIS with IWA
> > turned on)?
> >
> > On Mon, 11 Jun 2007 07:19:57 -0700 (PDT)
> > FrankenCoder <jmgray314 at hotmail.com> wrote:
> >
> >>
> >> Hello all,
> >>
> >> I am trying to set up a basic jcifs single-sign on process and cannot
> get
> >> IE
> >> to complete the NTLM handshake. The http traffic and logs show that the
> >> NTLM
> >> call/response is functioning but the last request from IE is never
> >> invoked;
> >> the type 3 message is never sent. Has anyone ever seen this before?
> With
> >> firefox on the same system, the user is prompted and able to login, so
> >> the
> >> mechanism appears to be in place, but IE just fails with a "The page
> >> cannot
> >> be displayed" message.
> >>
> >> Any thoughts would be greatly appreciated.
> >> Thank you
> >>
> >> Here is my setup:
> >>
> >> Tomcat 4.1.36
> >> jdk 1.4.2_11
> >> jcifs 1.2.13
> >>
> >>
> >>
> >>
> >>     <filter>
> >>         <filter-name>NtlmHttpFilter</filter-name>
> >>         <filter-class>jcifs.http.SSONtlmHttpFilter</filter-class>
> >>
> >>         <init-param>
> >>             <param-name>jcifs.netbios.wins</param-name>
> >>             <param-value>10.33.8.29,10.33.8.31</param-value>
> >>         </init-param>
> >>
> >>         <init-param>
> >>             <param-name>jcifs.smb.client.domain</param-name>
> >>             <param-value>ABC</param-value>
> >>         </init-param>
> >>
> >>         <init-param>
> >>             <param-name>jcifs.smb.client.username</param-name>
> >>             <param-value>TESTUSER</param-value>
> >>         </init-param>
> >>
> >>         <init-param>
> >>             <param-name>jcifs.smb.client.password</param-name>
> >>             <param-value>...</param-value>
> >>         </init-param>
> >>
> >>         <init-param>
> >>             <param-name>jcifs.encoding</param-name>
> >>             <param-value>ASCII</param-value>
> >>             </init-param>
> >>
> >>         <init-param>
> >>             <param-name>jcifs.util.loglevel</param-name>
> >>             <param-value>10</param-value>
> >>         </init-param>
> >>     </filter>
> >>
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/NTLM-Type-3-Message-Never-Sent-tf3901852.html#a11061496
> >> Sent from the Samba - jcifs mailing list archive at Nabble.com.
> >>
> >
> >
> > --
> > Michael B Allen
> > PHP Active Directory Kerberos SSO
> > http://www.ioplex.com/
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/NTLM-Type-3-Message-Never-Sent-tf3901852.html#a11063462
> Sent from the Samba - jcifs mailing list archive at Nabble.com.
>
>
-------------- next part --------------
HTML attachment scrubbed and removed