Windows 10 Share not accessible from Ubuntu 16.04 LTS

Solution 1:

Sounds like you are on the right track. If the problem is related to SMB1 the following will resolve your issue.

First make a copy of smb.conf

cp /etc/samba/smb.conf /etc/samba/smb.conf.orig

After making the copy

sudo gedit /etc/samba/smb.conf

Feel free to use vi/vim/nano if you do not prefer gedit

In the file, add the following in the [global] section

client min protocol = SMB2
client max protocol = SMB3

After saving the edits to the file. Restart SMB

sudo service smbd restart

If this does not work please include errors.

Solution 2:

Ok, sorry for coming back so late to this. The fix basically is this:

sudo mount -o vers=3.0,username=<your_username>,uid=<your_user_id>,gid=<your_group_id>,forceuid,forcegid, //<ip_address>/<path_to_share> /<mount>/<point>/<local_system>

Note that I have skipped the "-t(--type)" option this time, since if this option is not specified "mount" will try and guess what system to use, and with all honesty, given the amount of reading I had already done on what was going on with Windows 10 sharing protocols, I chose to let "mount" do its magic for me. ;-)

Here for an extract of the "mount man page":

"If no -t option is given, or if the auto type is specified, mount will try to guess the desired type. Mount uses the blkid library for guessing the filesystem type; if that does not turn up anything that looks familiar, mount will try to read the file /etc/filesystems, or, if that does not exist, /proc/filesystems. All of the filesys‐tem types listed there will be tried, except for those that are labeled "nodev" (e.g., devpts, proc and nfs). If /etc/filesystems ends in a line with a single *, mount will read /proc/filesystems afterwards. While trying, all filesystem types will be mounted with the mount option silent."

Also, since "mount" could only be run as root, but other programs writing to this mount point aren't run as root, you will need to specify the user and group which you want to grant writing privileges(ownership) to the mount location, hence the use of: uid=<your_user_id>,gid=<your_group_id>,forceuid,forcegid,.

Done! @xguru, Thanks for the help!:)