Troubleshoot a CIFS connection
The remoting functionality for XL Deploy and XL Release uses the Overthere framework to manipulate files and execute commands on remote hosts. CIFS, Telnet, and WinRM are supported for connectivity to Microsoft Windows hosts. This topic describes configuration errors that can occur when using XL Deploy or XL Release with the CIFS protocol.
The JCIFS library, which the Remoting plugin uses to connect to CIFS shares, will try to query the Windows domain controller to resolve the hostname in SMB URLs. JCIFS will send packets over port 139 (one of the [NetBIOS over TCP/IP] ports) to query the DFS. If that port is blocked by a firewall, JCIFS will only fall back to using regular hostname resolution after a timeout has occurred.
Set the following Java system property to prevent JCIFS from sending DFS query packets:
See this article on the JCIFS mailing list for a more detailed explanation.
If the problem cannot be solved by changing the network topology, try increasing the JCIFS timeout values documented in the JCIFS documentation. Another system property named
jcifs.smb.client.connTimeout may be useful. See JCIFS homepage for details.
To get more debug information from JCIFS, set the system property
jcifs.util.loglevel to 3.
This error can occur when connecting to a host with an IP address that resolves to more than one name. For information about resolving this error, refer to Microsoft Knowledge Base article #281308.