[jcifs] NtlmHttpFilter differences 1.1.0 vs. 1.2.0 - FAILED VALIDATE DC

Brian Moran brianmo at yahoo.com
Tue Jun 28 20:49:20 GMT 2005

I am trying jcifs 1.1.0 vs. jcifs 1.2.0, for the NTLM
authentication filter... 1.1.0 works, 1.2.0 doesn't. 

The configuration is as follows:
Domain Server: "CORP" - Windows 2003 Server, SP1.
Mixed mode.
Container: Jetty 5.1.4
web.xml set up with NtlmHttpFilter to "guard" the demo
in web.xml:
jcifs.smb.client.domain is set to CORP
jcifs.netbios.wins is set to the IP address of the DC 
jcifs.util.loglevel 10
jcifs.smb.client.domainController set to the hostname
of the domain controller (srv2)

When jetty and the 1.1.0 jar is used, I get prompted
for credentials (after the default set fail as they
should), and can successfully authenticated against
the Domain; using 1.2.0 (doing nothing other than
dropping the 1.2.0 jar in, removing 1.1.0 jar), I get
a "Failed validate DC: CORP<1C>/--ip-address-of-corp--

I guess I can compare the code of 1.1.0 vs. 1.2.0 to
see what changed, but perhaps someone else has run
into this?


More information about the jcifs mailing list