on 3-26-2008 12:15 PM Anne Wilson spake the following: > On Wednesday 26 March 2008 18:59:41 Les Mikesell wrote: >> Anne Wilson wrote: >>> Like John, I fought long and hard to get user share working. I read >>> Everything I could, including buying Samba3 by Example. In the end I >>> admitted defeat and went back to shares. >> If you really want a public share with no authentication at all, share >> mode is probably the best approach. If everyone that should have access >> is logged into a windows domain anyway, you can transparently accept >> this authentication and either keep their user id (as for a home >> directory share) or force it or their group id into something that gives >> common r/w access to a share. You can also do the latter with explicit >> logins against uses in the smbpasswd file. >> > This is becoming a real hijack, which I didn't intend. However, > > All users that are intended to be able to share have a user account on the > samba server. All users have samba passwords matching their login passwords, > whether in windows or linux. I couldn't even get their home directories to > show using 'user' mode. > > Anne > It is possible, because I am doing it. I have share=user and have home directories viewable by the user and the admin (me). I have various departmental shares that each department can access and no one else (but the admin -- again me). Even shares that aren't browsable, so no one even knows they are there if not given access. And I have several public shares, some read-write, some read only with install files and such. USers that try to access a share they have no permission to get the logon box, but it will never actually auth because their rights don't allow it. -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't!!!! -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 250 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos/attachments/20080326/81c51c10/attachment-0004.sig>