Modify

Opened 4 years ago

Closed 3 years ago

Last modified 22 months ago

#10365 closed defect (duplicate)

CIFS mount error | CIFS VFS: Error -2 during NTLM authentication

Reported by: anonymous Owned by: developers
Priority: high Milestone: Barrier Breaker 14.07
Component: packages Version: Trunk
Keywords: cifs, Cc:

Description

Can't mount CIFS.

There is dmesg log:

CIFS VFS: default security mechanism requested.  The default security mechanism will be upgraded from ntlm to ntlmv2 in kernel release 2.6.41
CIFS VFS: mdfour: Crypto md4 allocation error -2

CIFS VFS: Error -2 during NTLM authentication
CIFS VFS: Send error in SessSetup = -2
CIFS VFS: mdfour: Crypto md4 allocation error -2

CIFS VFS: Error -2 during NTLM authentication
CIFS VFS: Send error in SessSetup = -2
CIFS VFS: cifs_mount failed w/return code = -2
CIFS VFS: mdfour: Crypto md4 allocation error -2

Mount error:

root@AirNET:~# mount  //SINGULARITY/test /mnt/share -o user=Share,password=serve
r,file_mod=0777,dir_mode=0777,nounix,noserverino,hard,intr
mount error 2 = No such file or directory
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)

Installed kmod pakages:

root@AirNET:~# opkg list-installed | grep kmod
kmod-ath - 2.6.39.4+2011-10-05-1
kmod-ath9k - 2.6.39.4+2011-10-05-1
kmod-ath9k-common - 2.6.39.4+2011-10-05-1
kmod-button-hotplug - 2.6.39.4-3
kmod-cfg80211 - 2.6.39.4+2011-10-05-1
kmod-crc-ccitt - 2.6.39.4-1
kmod-crc16 - 2.6.39.4-1
kmod-crypto-aes - 2.6.39.4-1
kmod-crypto-arc4 - 2.6.39.4-1
kmod-crypto-core - 2.6.39.4-1
kmod-crypto-hash - 2.6.39.4-1
kmod-crypto-hmac - 2.6.39.4-1
kmod-crypto-manager - 2.6.39.4-1
kmod-crypto-md5 - 2.6.39.4-1
kmod-crypto-misc - 2.6.39.4-1
kmod-fs-cifs - 2.6.39.4-1
kmod-fs-ext4 - 2.6.39.4-1
kmod-input-core - 2.6.39.4-1
kmod-input-gpio-keys-polled - 2.6.39.4-1
kmod-input-polldev - 2.6.39.4-1
kmod-ipt-conntrack - 2.6.39.4-1
kmod-ipt-core - 2.6.39.4-1
kmod-ipt-nat - 2.6.39.4-1
kmod-ipt-nathelper - 2.6.39.4-1
kmod-leds-gpio - 2.6.39.4-1
kmod-ledtrig-usbdev - 2.6.39.4-1
kmod-loop - 2.6.39.4-1
kmod-mac80211 - 2.6.39.4+2011-10-05-1
kmod-nls-base - 2.6.39.4-1
kmod-nls-utf8 - 2.6.39.4-1
kmod-ppp - 2.6.39.4-1
kmod-pppoe - 2.6.39.4-1
kmod-usb-core - 2.6.39.4-1
kmod-usb-ohci - 2.6.39.4-1
kmod-usb2 - 2.6.39.4-1

Also installed cifsmount.

In backfire 10.03 RC6 all works fine..

Attachments (0)

Change History (8)

comment:1 Changed 4 years ago by jow

You need to install kmod-crypto-md4. If it is not available yet you have to wait for an updated build.

comment:2 Changed 4 years ago by nico

  • Resolution set to duplicate
  • Status changed from new to closed

See #10055

comment:3 Changed 3 years ago by John Thomas <openwrt-devel-2012@…>

[ 292.190000] CIFS VFS: could not allocate crypto hmacsha256
[ 292.190000]
[ 292.200000] CIFS VFS: could not setup hash structures rc -2
[ 292.200000] CIFS VFS: cifs_mount failed w/return code = -2
[ 1251.360000] CIFS VFS: could not allocate crypto hmacsha256
[ 1251.360000]
[ 1251.370000] CIFS VFS: could not setup hash structures rc -2
[ 1251.380000] CIFS VFS: cifs_mount failed w/return code = -2
[ 1357.320000] CIFS VFS: could not allocate crypto hmacsha256
[ 1357.320000]
[ 1357.320000] CIFS VFS: could not setup hash structures rc -2
[ 1357.330000] CIFS VFS: cifs_mount failed w/return code = -2
[ 1371.270000] CIFS VFS: could not allocate crypto hmacsha256
[ 1371.270000]
[ 1371.280000] CIFS VFS: could not setup hash structures rc -2
[ 1371.280000] CIFS VFS: cifs_mount failed w/return code = -2
[ 1590.490000] CIFS VFS: No username specified
[ 1590.500000] CIFS VFS: could not allocate crypto hmacsha256
[ 1590.500000]
[ 1590.500000] CIFS VFS: could not setup hash structures rc -2
[ 1590.510000] CIFS VFS: cifs_mount failed w/return code = -2
[ 1956.210000] CIFS VFS: No username specified
[ 1956.220000] CIFS VFS: could not allocate crypto hmacsha256
[ 1956.220000]
[ 1956.220000] CIFS VFS: could not setup hash structures rc -2
[ 1956.230000] CIFS VFS: cifs_mount failed w/return code = -2
[ 2290.120000] CIFS VFS: No username specified
[ 2290.130000] CIFS VFS: could not allocate crypto hmacsha256
[ 2290.130000]
[ 2290.140000] CIFS VFS: could not setup hash structures rc -2
[ 2290.150000] CIFS VFS: cifs_mount failed w/return code = -2
[ 2298.970000] CIFS VFS: could not allocate crypto hmacsha256
[ 2298.970000]
[ 2298.980000] CIFS VFS: could not setup hash structures rc -2
[ 2298.990000] CIFS VFS: cifs_mount failed w/return code = -2

comment:4 Changed 3 years ago by John Thomas <openwrt-devel-2012@…>

sorry, did not see the prior closing and noting of duplicate. I am not sure how to delete my comment. Sorry

comment:5 Changed 3 years ago by John Thomas <openwrt-devel-2012@…>

  • Resolution duplicate deleted
  • Status changed from closed to reopened

kmod-crypto-md4 is already installed, see below. Could the kernel update be the issue as mount.cifs works fine on 3.6.

http://kernelnewbies.org/LinuxChanges notes the following about 3.7.1:
The CIFS networking filesystem has added support for the version 2 of the SMB protocol. The SMB2 protocol is the successor to the popular CIFS and SMB network file sharing protocols, and is the native file sharing mechanism for Windows operating systems since it was introduced in Windows Vista in 2006. SMB2 enablement will eventually allow users better performance, security and features, than would not be possible with previous protocols.

root@wifi01:~# opkg list | grep kmod-cry
kmod-crypto-aes - 3.7.1-1
kmod-crypto-arc4 - 3.7.1-1
kmod-crypto-des - 3.7.1-1
kmod-crypto-ecb - 3.7.1-1
kmod-crypto-hash - 3.7.1-1
kmod-crypto-hmac - 3.7.1-1
kmod-crypto-md4 - 3.7.1-1
kmod-crypto-md5 - 3.7.1-1
kmod-crypto-misc - 3.7.1-1
kmod-crypto-sha1 - 3.7.1-1

comment:6 Changed 3 years ago by John Thomas <openwrt-devel-2012@…>

please close, I think we have two tickets now. Sorry, noob here.

comment:7 Changed 3 years ago by nbd

  • Resolution set to duplicate
  • Status changed from reopened to closed

comment:8 Changed 22 months ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.