[SOLVED] Problem accessing share from Ubuntu

[Heath]

I've been playing with a trial box until I can buy my new drives. Everything is going great with one little problem. My Windows and Android based clients connect to the NAS shares splendidly. My Ubuntu Linux client, however, doesn't seem to play nice.

I've read this thread. And I've read this and this as well as numerous other threads here and blog postings elsewhere. The problem described by the creator of this thread describes my problem, but his solution doesn't apply to me.

I'm using Local Users and have created the users in N4F. Each user's primary group is "Family" and their home directory is mapped to a directory with the same name as the user. In addition to a folder for each user, there's also a "Public" folder for all users to have access to. This seems to be a pretty common type of setup.

CIFS/SMB is enabled (that and ssh are the only services enabled). Map To Guest is set to "Never." I have three shares. One for user home folders using variables, one for the public share, and one hidden share giving access to everything for a particular user account. Enable Guest Access is disabled for all of them and Inherit permissions is unchecked.

Path: %H
Name: %U
Comment: User Home Folders
Browseable: Yes
Guest: No

Path: /mnt/Demo-Pool/Public/
Name: Public
Comment: Content for Everyone
Browseable: Yes
Guest: No

Path: /mnt/Demo-Pool
Name: root
Comment: root
Browseable: No
Guest: No

When I connect with Windows clients (Win8 and XP have been tested), I am prompted for credentials. Every user tested can authenticate and has access to exactly what I want them to have access to - their home directory and the Public directory. My special "all-seeing" user can see everything. I use ES File Explorer on Android and when I configure the server connection which includes credentials, I again see just want I want that user to see.

With Ubuntu, when I connect to the NAS, I am not prompted for credentials and I see two directories. The Public directory that everybody has access to, and a directory labeled "ftp." This happens regardless of the connection method - either using Nautilus to browse the Network and connecting to the NAS; clicking "GO" then "Location" and entering "smb://<ip of nas>/<share>"; etc. If I try to open the Public directory, then I'm asked for credentials. Good credentials lets me into the directory. If I try to open the FTP directory, I'm asked for credentials, but then get "Unable to mount location."

But, if I click Go -> Location and enter "smb://<ip of nas>/root" then I am never prompted for credentials I have access to everything.

I do have a user on the NAS that has the same username as my Ubuntu user, but the password is different. I've tried it with the same password, but that didn't change anything. This is not the "all-seeing" user. That username does not exist on the Ubuntu machine.

I'm sure the problem is my ignorance, but... Help?

[Heath]

Nobody? I've been fighting this, but just can't figure it out. I've tried it with Ubuntu 10.04 and 13.04 and the behavior is the same in both versions.

[raulfg3]

I see simmilar problems with UBUNTU in other forums, so perhaps can be a UBUNTU problem not a N4F problem:

http://forums.openmediavault.org/viewto ... f=3&t=3685

[Heath]

After a lot more reading, research, and tinkering, I finally resolved it. I had to make a couple changes to N4F and change the way I was accessing the shares from Ubuntu.

First, in N4F, I created a group for each user with the group name being the same as the username. Then created a "public" group for all users to be in. For instance, my user "heath" is in the group "heath" as primary and "public" as secondary. Then, I had to use WinSCP to change the owner and group on each user's folder to that user. It would be nice if there was a tool within the N4F web interface to do that.

In Ubuntu, I had been trying to access the shares from Nautilus (the graphical file browser akin to Windows Explorer). This just didn't work regardless of the method within Nautilus I used. I had to edit the fstab file. To make a long story short, I basically just followed this guide: http://ubuntuforums.org/showthread.php?t=288534

Everything is working great now, but having to use the terminal to change file permissions and edit configuration files and such like this is one reason I say Ubuntu specifically and Linux in general is "almost" ready for prime time, but it's not quite there yet.