Yes, I have set the global parameter in smb.conf. And it did cause the smbclient call to work without adding the max-protocol tag (-m), so this was successful:
smbclient -U domain\\user //HOSTNAME/ShareName -c "dir"But unfortunately it has no effect on Filesys::SmbClient and my Perl-script. It appears that it still uses SMB1 (same error message as before). I am very puzzled over this behaviour.
In reply to Re^2: Unable to establish SMB2 connection using Filesys::SmbClient
by Netras
in thread Unable to establish SMB2 connection using Filesys::SmbClient
by Netras
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |