I was trying kerberized CIFS access with a cluster
Although smbclient -k worked fine with it, mount.cifs failed with the following error
[root@client01 ~]# mount -t cifs //192.168.121.41/failover /mnt -osec=krb5,user=userr -vv
mount.cifs kernel mount options: unc=//192.168.121.41\failover,ver=1,rw,sec=krb5,user=userr,ip=192.168.121.41
mount error(126): Required key not available
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Thought maybe it needs a ticket before mount so acquired a ticket as well
[root@client01 ~]# klist
Ticket cache: FILE:/tmp/krb5cc_0
Default principal:
testuser@LUVSHINES.COM
Valid starting Expires Service principal
06/17/10 15:10:59 06/18/10 15:10:42 krbtgt/LUVSHINES.COM@LUVSHINES.COM
06/17/10 15:14:06 06/18/10 15:10:42 host/tiger@LUVSHINES.COM
But the command failed with the same error. The server had the principles added with short name
[root@tiger.mac01 ~]# klist -kte | grep tiger | grep cifs
3 05/12/10 23:36:13 cifs/tiger@LUVSHINES.COM (DES with HMAC/sha1)
3 05/12/10 23:36:13 cifs/tiger@LUVSHINES.COM (DES cbc mode with RSA-MD5)
3 05/12/10 23:36:13 cifs/tiger@LUVSHINES.COM (Triple DES cbc mode with HMAC/sha1)
Any suggestions ??