Yes... err... 42... I'm confused.http://cuddletech.com/?p=23
In some distro or better... not in freebsd you can use the -v flag in ls -v instead of getfacl. And there is also a -A flag in chmod.
Have been searching for this now and then but I can't get my search queries right. My question goes ...
From my findings you only have user, group and everyone.
It doesn't matter how many user or groups you add from you windows client (right click on the share -> properties -> security..) ..
Dos adjustment will have no impact what so ever.. or mimic the behaviour they will be having in real windows environment. They show up in getfacl but that's far as it goes.
true or false ?
But how can I hide the folders from view for users that is not allowed into the share?
Of course it will, something else is wrong.First off, this post alone doesnt tell you all the steps needed to log in.....what username and password do i connect to the share with? the "domain" will default to the client hostname so the user and password created on Freenas will NOT work. I have tried with the freenas hostname, the ip, the workgroup...NONE work
tl;dr - they are incompatible and you should not try that under penalty of losing any hair you might still have on your head. And your data, too.Second, why do I need to set it to "Windows" permissions? The data set I want to share is already shared via NFS and has many *nix users connected to it? Does setting to "Windows" permissions break NFS / Linux machines?
There's nothing to it. Users log in and can see shares they have read permissions for. Just setup proper permissions for your scenario.Third, what about how I do NOT want the owner of the data set to be the user I am trying to connect to SMB? I am the admin, i have the root account, i want to be the owner, but I want other (multiple) windows machines to be able to connect with unique log ins...i could NOT repeat your tutorial and connect 2 users to the same dataset (not with the instructions provided).
What instructions do you want? All steps are either "fill in forms" or "change permissions like you would for a local file on Windows or a Windows server.Fourth, short of the one quip about not "turning the knob" that disables a users password, you provided ZERO instruction on ANY of the steps you gave. Not even so much as a "Hey make sure your screens look like mine and have the settings set that I have in the pictures (which is what I tried to do, but it didnt work). A
There are all kinds of scenarios. Obviously, the warning doesn't apply to clean configurations.Fifth, at the end you say "mucking around with permissions"...where? on the freenas box? On the windows client that i CANNOT get connected? Why / how would a user who is following a how to setup SMB shares from freenas logically have been even ABLE to mess with perms...presumably the readers of your post are in need of assistance to get SMB working.
What? Link please. This is, quite obviously, based on FreeNAS 9.x. The FreeNAS 10 interface has nothing to do with this (though the steps are mostly analogous).I am sorry to be taking my frustration out on you, but I have posted far and wide about this and have gotten no help and to come across this post at the top of "SMB on FreeNAS 10"
That's not a great way to start.This is by far the vaguest "tutorial" ever.
You are correct. Sometimes you need to specify <hostname of samba server>\<username> (or at least make sure that the client's domain name isn't being prepended to the username). For instance, if you want to use a local user account on a domain-joined freenas server.First off, this post alone doesnt tell you all the steps needed to log in.....what username and password do i connect to the share with? the "domain" will default to the client hostname so the user and password created on Freenas will NOT work. I have tried with the freenas hostname, the ip, the workgroup...NONE work
the goal of my example was to show a reliable method to set default permissions. Those items are off-topic. I cover some in posts in my forum signature.Second, why do I need to set it to "Windows" permissions? The data set I want to share is already shared via NFS and has many *nix users connected to it? Does setting to "Windows" permissions break NFS / Linux machines?
manipulate the permissions like any windows server. Add acl entry for the group the other users are members of.Third, what about how I do NOT want the owner of the data set to be the user I am trying to connect to SMB? I am the admin, i have the root account, i want to be the owner, but I want other (multiple) windows machines to be able to connect with unique log ins...i could NOT repeat your tutorial and connect 2 users to the same dataset (not with the instructions provided).
that quip was probably added at a later date out of frustration because there was a checkbox in the User creation GUI to disable password authentication for the user. Someone wrote up a tutorial advising to check this box, which of course will prevent a user from being able to authenticate.Fourth, short of the one quip about not "turning the knob" that disables a users password, you provided ZERO instruction on ANY of the steps you gave. Not even so much as a "Hey make sure your screens look like mine and have the settings set that I have in the pictures (which is what I tried to do, but it didnt work). Also on this topic, a worthwhile set of instructions gives brief explanation for doing something, so that the reader actually learns as they go. You give no reasoning for what you want us to do.
Fifth, at the end you say "mucking around with permissions"...where? on the freenas box? On the windows client that i CANNOT get connected?
Once you set default permissions on the share, you will be able to access it. It is impossible to list all the ways a person can misconfigure a client, server, or network.Why / how would a user who is following a how to setup SMB shares from freenas logically have been even ABLE to mess with perms...presumably the readers of your post are in need of assistance to get SMB working.
It sounds like you need to start a thread and provide lots of info about what you're doing and provide config details and logs. Samba isn't broken.I will say, i suppose I am just stupid, but I have been an IT Professional for 10+ years now and have setup countless windows and *nix servers (and have even run several freenas instances) but i have followed article after article and read through so much documentation only to be told that what I am doing is accurate but to find that it doesnt work is the most frustrating thing there is. I have redone my entire network bottom up, I have gone from FreeNAS 9.10 stable to 10 nightlies, to 10 beta 2, to 9.10 stable again, and am currently at 10 Beta 2 (since the behavior / failure with SMB is identical between all versions I have tried).
Okay... If you're actually interested in getting help, start a new thread.I am sorry to be taking my frustration out on you, but I have posted far and wide about this and have gotten no help and to come across this post at the top of "SMB on FreeNAS 10" just was the last straw...this utterly empty (and not version 10) tutorial is one of the most worthless I have seen.....I do not expect anyone to help me but I wanted to share so the author knows just how uninformative their tutorial is. I am not sure how others followed this and had any success, but I suspect that there are vastly more users that find this, try it, and turn away in disgust because of its failure rate.
To the extent that Macs have a stable, sane, and standards-compliant SMB client.... yes, it will work.Will this tutorial work in similar fashion with Macs and Windoze PCs in the same network?