I hope you can help me with a small issue that is kinda driving me crazy.
I'm running debian wheezy on a virtual machine and trying to mount some shares from the win8.1 host.
The lines I put in the /etc/fstab a
Code:
//192.168.0.10/dir1 /home/user/dir1 cifs credentials=/root/.secret.pwd,uid=1000,gid=1000,file_mode=0777,dir_mode=0777,iocharset=utf8,sec=ntlm 0 0 //192.160.0.10/dir2 /home/user/dir2 cifs credentials=/root/.secret.pwd,uid=1000,gid=1000,file_mode=0777,dir_mode=0777,iocharset=utf8,sec=ntlm 0 0 //192.160.0.10/dir3 /home/user/dir3 cifs credentials=/root/.secret.pwd,uid=1000,gid=1000,file_mode=0777,dir_mode=0777,iocharset=utf8,sec=ntlm 0 0
The first share gets mounted correctly, but not the other two.
This is the output I get when sudo-ing a mount -a:
Code:
mount error(115): Operation now in progress Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) mount error(115): Operation now in progress Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
and this is what /var/log/syslog shows:
Code:
Mar 24 12:56:12 hostname kernel: [ 1887.029043] CIFS VFS: Error connecting to socket. Aborting operation Mar 24 12:56:12 hostname kernel: [ 1887.030013] CIFS VFS: cifs_mount failed w/return code = -115 Mar 24 12:56:22 hostname kernel: [ 1897.052130] CIFS VFS: Error connecting to socket. Aborting operation Mar 24 12:56:22 hostname kernel: [ 1897.053885] CIFS VFS: cifs_mount failed w/return code = -115
The same happens at boot time.
Now, the crazy thing is that if I run manually a:
Code:
sudo mount //192.168.0.10/dir2 /home/user/dir2 -t cifs -o credentials=/root/.secret.pwd,uid=1000,gid=1000
it works perfectly.
Now, I'm no power user, but I thought I'd be able to manage a couple of simple cifs shares...but then again I guess not
So, my questions so far a
1. how the heck do I make that work?
2. why is it not working? Might be the security? Should I choose perhaps ntlmv2? I read a bit around but I don't know this kind of security mechanisms, so...
3. why on earth is the first mount working just like a charm and not the other two?
You know what? I'm trying now to remove the sec option from the fstab, and see how that works out.
In the meantime, if anyone could lend a hand I'd appreciate it very much