With 15.04 (running inside VirtualBox), I used the technique descibed here and it worked fine.
//servername/sharename /media/windowsshare cifs username=msusername,password=mspassword,iocharset=utf8,sec=ntlm 0 0
Now, in 15.10 (still inside the same VirtualBox setup), this does not work anymore. I get an error message at boot and the shares are not mounted. They can however be mounted manually with 'sudo mount -a'.
The error messages :
[ 22.497984] CIFS VFS: Error connecting to socket. Aborting operation.
[ 22.498336] CIFS VFS: vifs_mount failed w/return code = -101
This suggest a network error but I do not see why, except perhaps because this is running within VirtualBox? But again, the same method worked before.
Then I tried adding the 'x-systemd.automount' flag like I saw in this post:
//servername/sharename /media/windowsshare cifs username=msusername,password=mspassword,iocharset=utf8,sec=ntlm,x-systemd.automount 0 0
I still get the error messages at startup but surprise! ... it sort of works. The share is indeed mounted on the correct mount point and I can acesss it fine. However, on the Gnome desktop, where I have specified that I want to see the mounted volumes using the tweek tool, I see my shares twice but with 2 different types of icons: Click to see screenshot. When I do not use the 'x-systemd.automount' and do 'sudo mount -a' manually, only the lower kinds of icons appear.
I also tried various other combinations of additional flags (like using a credentials file or setting the 'gid=xxxx,uid=xxxx' flags) but it does not change anything.
Does anyone knows a way to fix this ?
noauto,x-systemd.automount,x-systemd.device-timeout=3
thats how it works withsystemd
and the problem with two icons is just a bug in current desktop environment