$ smbclient -L 172.16.16.1 --user=USER%PWD Sharename Type Comment --------- ---- ------- G Disk H Disk I Disk IPC$ IPC IPC Service (samba server) SMB1 disabled -- no workgroup available $ sudo mount -t cifs -ouser=USER,pass=PWD //172.16.16.1/H /mnt/H mount error(22): Invalid argument Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
Have you not done any updates since you installed? Possibly all you need is the latest kernel:
https://bugzilla.opensuse.org/show_bug.cgi?id=1206935
Just in case this thread is relevant to you
Try specifying “vers=2.0” or “vers=3.02” in the mount command and report back.
1 Like
“-overs=2.0” makes it all happy. (The router with the share doesn’t support 3.x.)
sudo mount -t cifs -ouser=shareusr -opass=**** -overs=2.0 //172.16.16.1/H /mnt/H
(The router doing the share thinks everybody likes drive letters, so I can’t give it a name.)
The other piece of information that’s relevant is that my Tp-Link router (AXE5400 Tri-Band Wi-Fi 6E Router) is very old: 2019 whereas SMB2.1 hadn’t been around long enough – only 9 years by then. High speed tech churn bites again. 
This worked (the router insists on “drive letter” exports):
//router/G /mnt/G cifs rw,vers=2.0,credentials=/etc/creds/router,uid=ME 0 0
//router/H /mnt/H cifs rw,vers=2.0,credentials=/etc/creds/router,uid=ME 0 0
//router/I /mnt/I cifs rw,vers=2.0,credentials=/etc/creds/router,uid=ME 0 0
Good, then you were impacted as with the older thread I assisted with.
Yes, more of a samba client issue I think.
Exactly. The Samba client should be negotiating over which protocol to use instead of demanding that I know, a priori, what to use. I’m okay with SMB1.0 being deprecated, but 2.0 should get detected – even if 2.1 came along in 2008. OS/X handles it just fine. Oh, well…