jcifs-ng will be a proper choice for many users. 
There are a lot of SMB devices in the world.
Some of them only work with the old jcifs library.
If you want to support many SMB devices, CodeLibs jcifs library will be helpful.
For example, since [Fess](https://github.com/codelibs/fess) needs to support many SMB devices, it uses this library.

        "The network name cannot be found.",
        "Not enough storage is available to process this command.",
        "The media is write protected.",
        "The device is not ready.",
        "A device attached to the system is not functioning.",
        "A device attached to the system is not functioning.",
        "The process cannot access the file because it is being used by another process.",

 * server. Rather than represent each with it's own <code>Exception</code>
 * class, this class represents all of them. For many of the popular
 * error codes, constants and text messages like "The device is not ready"
 * are provided.
 * <p>
 * The jCIFS client maps DOS error codes to NTSTATUS codes. This means that
 * the user may recieve a different error from a legacy server than that of

     * represents is a printer.
     */
    static final int TYPE_PRINTER = 0x20;
    /**
     * Returned by {@link jcifs.SmbResource#getType()} if the resource this <tt>SmbFile</tt>
     * represents is a communications device.
     */
    static final int TYPE_COMM = 0x40;

    /* open flags */

    static final int O_RDONLY = 0x01;
    static final int O_WRONLY = 0x02;
    static final int O_RDWR = 0x03;

        "Not enough storage is available to process this command.", "The media is write protected.", "The device is not ready.",
        "A device attached to the system is not functioning.", "A device attached to the system is not functioning.",
        "The process cannot access the file because it is being used by another process.",

    static final int CONSTRAINT_DELEGATIION_TYPE = 0xB;
    static final int CLIENT_UPN_TYPE = 0xC;
    static final int CLIENT_CLAIMS_TYPE = 0xD;
    static final int DEVICE_INFO_TYPE = 0xE;
    static final int DEVICE_CLAIMS_TYPE = 0xF;

    static final int LOGON_EXTRA_SIDS = 0x20;
    static final int LOGON_RESOURCE_GROUPS = 0x200;

    static final int MD5_KRB_SALT = 17;

    public static final int NT_STATUS_INVALID_HANDLE = 0xC0000008;
    public static final int NT_STATUS_INVALID_PARAMETER = 0xC000000d;
    public static final int NT_STATUS_NO_SUCH_DEVICE = 0xC000000e;
    public static final int NT_STATUS_NO_SUCH_FILE = 0xC000000f;
    public static final int NT_STATUS_END_OF_FILE = 0xC0000011;
    public static final int NT_STATUS_MORE_PROCESSING_REQUIRED = 0xC0000016;

     * represents is a printer.
     */
    public static final int TYPE_PRINTER = 0x20;
    /**
     * Returned by {@link #getType()} if the resource this <tt>SmbFile</tt>
     * represents is a communications device.
     */
    public static final int TYPE_COMM = 0x40;


    private String canon;            // Initially null; set by getUncPath; dir must end with '/'
    private String share;            // Can be null

 * server. Rather than represent each with it's own <code>Exception</code>
 * class, this class represents all of them. For many of the popular
 * error codes, constants and text messages like "The device is not ready"
 * are provided.
 * <p>
 * The jCIFS client maps DOS error codes to NTSTATUS codes. This means that
 * the user may receive a different error from a legacy server than that of

        case 0x10B: // NT_STATUS_NOTIFY_CLEANUP:
        case NtStatus.NT_STATUS_NOTIFY_ENUM_DIR:
            break;
        case 0xC00000BB: // NT_STATUS_NOT_SUPPORTED
        case 0xC0000010: // NT_STATUS_INVALID_DEVICE_REQUEST
            throw new SmbUnsupportedOperationException();
        case NtStatus.NT_STATUS_PATH_NOT_COVERED:
            if ( ! ( req instanceof RequestWithPath ) ) {