[jcifs] JCIFS 1.2.1 java.net.UnknownHostException: Failed to negotiate with a suitable domain controller - PROBLEM SOLVED

[Michael B Allen]

On Fri, 12 Aug 2005 11:53:18 -0400
"Krueger Ken J  IT312" <ken.krueger at siemens.com> wrote:

> All,
> 
> We were able to identify the cause of and two solutions to this problem:
> 
> Both machines have multiple network interfaces installed as Mike suspected, including wireless network adapters.  On mine (machine #1), jcifs could correctly identify when to use the appropriate network adapter.  On the other (machine #2), jcifs could not, and it would struggle to use the wireless network adapter when it could just go to the LAN -- eventually timing out or throwing a "Failed to negotiate with a suitable domain controller for ..." exception.
> 
> We identified two solutions for machine #2.  1) Disable the wireless network.  2)  Keep the wireless network turned on but specifiy the local ip address of the network adapter we wanted to use.  In our case:
> 
> <init-param>
> 	<param-name>jcifs.smb.client.laddr</param-name>
> 	<param-value>192.168.1.4</param-value>
> </init-param>
> 
> Both work.  Since we want our solution to work everywhere, we're just going to disable the wireless network on #2 until we can figure out a more elegant solution.
> 
> If anyone knows of a more elegant solution, we'd love to hear about it!  Thanks to all for your responses.

This actually has nothing to do with jCIFS really. If you create a
raw network socket in Java it binds whatever interface it thinks is
primary. There's no real "solution" to this because Java cannot know
what interface you intend to use.

Mike