Just wanted to post a solution to an issue i had. hope it helps someone.
after recently updating to 5.1 i could not connect a network share to my server , it kept saying "mount error(112): Host is down" but i knew it was not. anyway the problem was due to the share i was connecting to is an outdated nas share with no firmware updates available
to get around the problem i had to force it to use version 1.0 of smb as latest kernel seems to default to 3.0 (see below) to do this add vers=1.0
for example
//nas-drive/share/backup /mnt/backup/ cifs vers=1.0, username=xxx,password=xxx,domain=10.10.1.250 0 0
it then connected successfully (security issues aside )
CIFS defaults to SMB3.0
Due to recent publicity about security vulnerabilities in the much older CIFS dialect, move the default dialect to the widely accepted (and quite secure) SMB3.0 dialect from the old default of the CIFS dialect. Both Microsoft and CERT now strongly recommend not using the older CIFS dialect (SMB Security Best Practices "recommends disabling SMBv1"). SMB3 is both secure and widely available: in Windows 8 and later, Samba and Macs. Users can still choose to explicitly mount with the less secure dialect (for old servers) by choosing "vers=1.0" on the cifs mount
hope this helps someone
after recently updating to 5.1 i could not connect a network share to my server , it kept saying "mount error(112): Host is down" but i knew it was not. anyway the problem was due to the share i was connecting to is an outdated nas share with no firmware updates available
to get around the problem i had to force it to use version 1.0 of smb as latest kernel seems to default to 3.0 (see below) to do this add vers=1.0
for example
//nas-drive/share/backup /mnt/backup/ cifs vers=1.0, username=xxx,password=xxx,domain=10.10.1.250 0 0
it then connected successfully (security issues aside
)CIFS defaults to SMB3.0
Due to recent publicity about security vulnerabilities in the much older CIFS dialect, move the default dialect to the widely accepted (and quite secure) SMB3.0 dialect from the old default of the CIFS dialect. Both Microsoft and CERT now strongly recommend not using the older CIFS dialect (SMB Security Best Practices "recommends disabling SMBv1"). SMB3 is both secure and widely available: in Windows 8 and later, Samba and Macs. Users can still choose to explicitly mount with the less secure dialect (for old servers) by choosing "vers=1.0" on the cifs mount
hope this helps someone
Last edited: