Search help pages:

 

Apresa Backup Diagnostic

SMB versions

Debian 8 combined with older Apresa versions : Apresa supports SMB v.1 (newer SMB versions only available on the command line)
Debian 8 and 9 combined a recent Apresa versions : Apresa supports SMB v.2.0 (SMB v.1 and v.3 only available on command line)
Debian 10: the highest possible SMB version greater or equal to 2.1 is negotiated (other versions available on command line)

SMB protocol versions that are understood by the mount.cifs command on Debian 10:

• 1.0 – The classic CIFS/SMBv1 protocol.
• 2.0 – The SMBv2.002 protocol. This was initially introduced in Windows Vista Service Pack 1, and Windows Server 2008. Note that the initial release version of Windows Vista spoke a slightly different dialect (2.000) that is not supported.
• 2.1 – The SMBv2.1 protocol that was introduced in Microsoft Windows 7 and Windows Server 2008R2.
• 3.0 – The SMBv3.0 protocol that was introduced in Microsoft Windows 8 and Windows Server 2012.
• 3.1.1 or 3.11 – The SMBv3.1.1 protocol that was introduced in Microsoft Windows Server 2016.

Not all features of each version are available.

Ports used (for firewall configuration)

Apresa uses “Samba”. Samba uses the following ports:
UDP/137 – used by nmbd
UDP/138 – used by nmbd
TCP/139 – used by smbd
TCP/445 – used by smbd

The last one is important as many older firewall setups may not be aware of it, given that this port was only added to the protocol later.

Known error conditions

Current Apresa versions will not connect to SMB version 1.0. There are known security issues with SMB version 1.0.

mount error: could not resolve address for XXXX: Name or service not known
– The name could not be resolved, use IP address instead

Unable to find suitable address.
– The IP address is incorrect or unreachable

mount error(2): No such file or directory
– The subdirectory is incorrect.

mount error(6): No such device or address
– The share name does not exist

mount error(13): Permission denied
– Incorrect user name or password

mount error(20): Not a directory
– The main directory is incorrect

mount error(112): Host is down
– SMB versions might be incompatible

Protocol negotiation failed: NT_STATUS_CONNECTION_RESET
– SMB versions might be incompatible

E(16) Mount is denied because the NTFS volume is already exclusively opened.
– The disk is already mounted. Unmount it first, or point to the existing mount point, using the option “Directory (mounted)”

To test from the command line (Linux)

1) To prepair for the test (once)

sudo mkdir /mnt/backuptest

2) To actually test:

sudo mount //SERVERIP/SHARE/DIR /mnt/backuptest -o username=USER

(It will prompt for the password.)
or if domain needs to be specified:

sudo mount //SERVERIP/SHARE/DIR /mnt/backuptest -o username=USER -o domain=DOMAIN

Addition parameters (such as the SMB version to use) can be added to the command line:

sudo mount //SERVERIP/SHARE/DIR /mnt/backuptest -o username=USER -o vers=3.11

Replace things in UPPERCASE by their data.
If there is no message displayed after this command, then it was probably successful. Otherwise, an error message should be displayed, indicating the error.

3) If the mount was successful, you can view the contents of the network directory with the following command:

ls /mnt/backuptest

4) To stop the test, disconnect from the server as follows:

sudo umount /mnt/backuptest
 
 

Visit the Vidicode Help Index or search the help pages: