Re: cifs problem with kernel 3.1

[Camaleón <noelamac@gmail.com>]

On Tue, 17 Jan 2012 10:19:21 +0200, Johann Spies wrote:

> Thanks to Camelón and Martin for replying.
> 
>> Is there anything in dmesg about this?
> 
> Yes.  More information:
> 
> Using the IP addressess does not help in mounting.
> 
> Mounting by hand (mount.cifs ... ) ended with the same result.
> 
> Dmesg:
> [  860.895104] CIFS VFS: cifs_mount failed w/return code = -13 
> [  881.452158] CIFS VFS: Send error in SessSetup = -13

Is accessing the share by means of the "smb://" protocol working? 
Can you even access/listing the shares with "smbclient"?

> When I add sec=ntlmv2 to the mount options I get
> 
> 
> [  593.130361] CIFS VFS: signing required but server lacks support 
> [  593.130472] CIFS VFS: cifs_mount failed w/return code = -95
> 
> 
> When I change /etc/fstab from
> //stbstaff.stb.sun.ac.za/dept/let/senis /home/js/mnt/senis cifs credentials=/etc/credentials,user,uid=1000,gid=1000 0     0
> 
> to
> 
> //stbstaff.stb.sun.ac.za/dept /home/js/mnt/senis cifs credentials=/etc/credentials,user,uid=1000,gid=1000 0     0
> 
> it mounts but I cannot use it as I do not have access rights to that
> directory.  Even as root I cannot access subfolders.
> 
> Also when I do this I get:
> 
> 
> [ 1256.850000] CIFS VFS: Autodisabling the use of server inode numbers
> on \\146.232.129.137\dept. This server doesn't seem to support them
> properly. Hardlinks will not be recognized on this mount. Consider
> mounting with the "noserverino" option to silence this message.
> 
> To me it seems like a bug somewhere.


It could be... True is that I have not experienced any problem in 
wheezy when accessing to windows shares :-?

Greetings,

-- 
Camaleón