In the past week or so, an update to my Tumbleweed has resulted in me no longer being able to mount CIFS columns from a Windows server (a company server, not my own). I now get this in the system log: [ 2203.773170] FS-Cache: Netfs 'cifs' registered for caching [ 2203.783492] Key type cifs.spnego registered [ 2203.783495] Key type cifs.idmap registered [ 2203.784007] CIFS: Attempting to mount //serammmarst01-a.XXX.ramboll-group.global.network/data2 [ 2214.047746] CIFS VFS: Error connecting to socket. Aborting operation. [ 2214.047774] CIFS VFS: cifs_mount failed w/return code = -2 No idea why. I do not think that the server has changed. And if it has, some IT guy in some cupboard is the only one who knows and he's not telling. So I am starting with the assumption that something has changed in Tumbleweed. I have tried with ver=1 and var=3. The command is: mount -t cifs //serammmarst01-a.XXX.ramboll-group.global.network/data6 /media/mma-sql-1/data6 -o soft,vers=3.0,credentials=/etc/cifs.creds.ramse,workgroup=RAMBOLL,rw,noauto,uid=roger This also fails when systemd automount tries to mount it. But if the mount command does not work. The /etc/cifs.creds.ramse file is correct and unchanged from when it worked. It makes no difference if I put the items in that file on the command line. The error is the same. I have tried ver= 1.0, 3, 3,0, 3,1,1 and default. No difference. I tried adding -vvv to the mount command to get more debugging. But that did not work. Anyone else see a recent change in behavior? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org