[jcifs] SOLVED: jcifs-1.2.5 fails on bad domain controller; does not try others

Oliver Schoett os at sdm.de
Fri Dec 30 10:59:33 GMT 2005

Oliver Schoett wrote:
> Oliver Schoett wrote:
>> In message <20050315133739.7a33637d.mba2000 at ioplex.com> dated Tue, 15 
>> Mar 2005 13:37:39 -0500, Michael B Allen writes:
>>> CIFS should handle this automatically. When jcifs rotates to a new
>>> DC it tries to negotiate with it to see if it's "good". If it isn't it
>>> removes it from the list. This process should not "hang".
>> However, the 1.2.5 NtlmHttpFilter still fails when the first DC in 
>> the list returned from WINS is bad (stack trace at the end). 
>> Apparently, it does *not* proceed to the other DCs in the list, as 
>> suggested above.
> I should add that the error message in the browser (talking to an OC4J 
> server with jcifs 1.2.5) is the following:
> 500 Internal Server Error
> 500 Internal Server Error
> java.net.UnknownHostException: Failed to negotiate with a suitable 
> domain controller for ******
Sorry, the customer configuration had the setting


This means that only the first entry in the DC list is tried and 
precisely explains the observed behaviour; there is no problem.


Oliver Schoett

More information about the jcifs mailing list