[jcifs] negotiation error
Alvin
apotti at umich.edu
Fri Aug 12 22:51:07 GMT 2005
Hello,
I updated to the latest version of JCIFS and I keep getting this error
intermittently (95% I have no problems):
java.net.UnknownHostException: Failed to negotiate with a suitable domain
controller for ***
jcifs.smb.SmbSession.getChallengeForDomain(SmbSession.java:124)
jcifs.http.NtlmHttpFilter.negotiate(NtlmHttpFilter.java:150)
jcifs.http.NtlmHttpFilter.doFilter(NtlmHttpFilter.java:114)
I'm using JCIFS through Tomcat and the filter paramters are as follows:
<filter>
<filter-name>NtlmHttpFilter</filter-name>
<filter-class>jcifs.http.NtlmHttpFilter</filter-class>
<init-param>
<param-name>jcifs.smb.client.domain</param-name>
<param-value>***</param-value>
</init-param>
<init-param>
<param-name>jcifs.netbios.wins</param-name>
<param-value>***.***.***.***</param-value>
</init-param>
<init-param>
<param-name>jcifs.smb.client.username</param-name>
<param-value>username</param-value>
</init-param>
<init-param>
<param-name>jcifs.smb.client.password</param-name>
<param-value>password</param-value>
</init-param>
</filter>
with the appropriate values being filled in. It's not a typo or misnamed
resource or unknown host, since it fails only 5% of the time (usually it works
flawlessly). The problem is exacerbated if there is a heavier load. Is there
another parameter or flag that could help with this problem?
Alvin
More information about the jcifs
mailing list