similar to: Update on group access controls failing w/Win2k3 SP1?

It might help if you view the default directory ACLs using the getfacl utility. These are what will be inherited by stuff created in the lower directories. I would ask yourself if you actually need ACLs at all. The Samba share permissions are pretty thorough and life is far easier without ACLs as you can clearly see what permissions are in use and backups are not an issue. ACLs can quickly

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ~ /usr/bin/net ads join -Udennisb dennisb password: [2004/11/02 17:31:56, 0] libads/ldap.c:ads_add_machine_acct(1006) ~ Host account for if-srv-hos1 already exists - modifying old account [2004/11/02 17:31:56, 0] libads/ldap.c:ads_join_realm(1342) ~ ads_add_machine_acct: No such object ads_join_realm: No such object Also: net user | wc -l reports

I've gotten samba working with ACLs over an XFS filesystem. Everything works pretty well with knowledge of the workarounds (cannot remove group everyone, etc.) The only major problem I have is that ACLs don't inherit correctly. The default in Windows 2000 is to have a sub folder inherit the permissions of the folder it is in on creation. By default, the Samba share's folders don't

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Would it not be possible to make the archive bit map to a Posix extended ACL instead of to the execute bit? - -Tom -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBWDuj2dxAfYNwANIRAvmnAJ4r1Q/2X7YyPKgGWbnnB3pv6WKDjwCgn+Vd 8USnnc35+uAa2GxUmejlDBc= =Bu48 -----END PGP

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sorry about that: enigmail got over excited! - -------- Original Message -------- Subject: Re: [Samba] Macro expansion in valid users = line? Date: Thu, 04 Sep 2003 13:15:42 -0700 From: Tom Dickson <tdickson@inostor.com> To: Gerald (Jerry) Carter <jerry@samba.org> CC: samba mailing list <samba@lists.samba.org> References:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Perhaps using a MS-DFS share would be more useful in this case? This would allow three real shares: \\server\accounting \\server\personal \\server\public which would appear as \\server\users\accounting \\server\users\personal \\server\users\public. See http://samba.org/~jht/HOWTO/Samba-HOWTO-Collection.pdf for more information on MS-DFS - -Tom

Running the command: wbinfo -aDOMAINNAME+Administrator%password works, in fact, all of the wbinfo commands report data as they should. However, when I try to connect to a share on the SMB server, I get the following error message in the logs: [2003/04/21 08:28:59, 0] smbd/password.c:connect_to_domain_password_server(1328) connect_to_domain_password_server: machine DWP rejected the tconX on

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 What is the standard procedure for making edits of smb.conf take hold? For example, what I'm seeing is a share that has given R/W access to a user named Tom, when I change Tom to read only, he is still able to write to that share until I stop Samba and restart it. The documentation seems to refer to a 1 minute reread of smb.conf, but I don't

stock samba 3.0.21a works just fine, I generated an rpm from samba source, and everything works just fine! the enterprisesamba packages are what is broken. -----Original Message----- From: samba-bounces+bsmoke=lapo.state.ar.us@lists.samba.org [mailto:samba-bounces+bsmoke=lapo.state.ar.us@lists.samba.org] On Behalf Of Barry Smoke Sent: Tuesday, January 10, 2006 2:38 PM To: samba@lists.samba.org

Well, it looks like we are stuck... I can't figure out what to do next. ads_connect: Program lacks support for encryption type here's the whole story: We've been using winbind successfully for over a year now, rhel3 variants(scientific linux 3), some run rhel3's default samba, others use the packages from http://enterprisesamba.com/ we started out using the NT4 compatability

Samba doesn't allow connections from usernames that have & in them. For example, using 2.2.5 and winbind with security = DOMAIN password server = win2kmixed workgroup = MIXEDDOMAIN all my users can login, (for example MIXEDDOMAIN+aho, MIXEDDOMAIN+tdickson), but my users named "&" and "bobalso&" (which should be MIXEDDOMAIN+& and MIXEDDOMAIN+bobalso&)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This patch is against samba-3.0.0beta3 (tested), but will also apply correctly to 3.0.0 (release) It makes wbinfo ask for a password if there is no password on the command line. So: wbinfo --set-auth-user=Administrator Will make it prompt Password: This is to make it easier to script wbinfo for nas appliances using expect to allow passwords with

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is there a tentative release date for 3.0.1 yet? I'd like to go live with an official release as opposed to hand patching all the little fixes I've seen on the mailing list (i.e., sorry about that; here's a patch, will be in 3.0.1). Thank you for all your work! - -Tom Dickson InoStor, Inc. http://www.inostor.com -----BEGIN PGP

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 After upgrading from 3.0.2 to 3.0.3 in a Windows 2000 Native Domain environment, 9x clients can't connect and wbinfo -t doesn't work: bash-2.05a# wbinfo -t checking the trust secret via RPC calls failed error code was NT_STATUS_PIPE_NOT_AVAILABLE (0xc00000ac) Could not check secret Downgrading to 3.0.2 fixes this. I can get log files, but

Hi all This one has me baffled - leading me to beleive it could be a bug similar to https://bugzilla.samba.org/show_bug.cgi?id=2695 I am running samba 3.0.20b on debian unstable and am having problems with some users not resolving properly using winbind. wbinfo -u shows all users on the system, no problem wbinfo -a user%password works for any user getent passwd shows most but not all users

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We had 3.0.2a which worked fine. If you tried to open a file that the ACLs wouldn't let you, you'd get access denied. We had follow symlinks=no in smb.conf Now with 3.0.8, and no other changes, we get a message about "The file has moved or otherwise gone away," instead of access denied. And we get this in the log file: [2004/11/16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We have a samba 3.0.14a server connected via NT4 to an ADS domain, and after a few hours of access, winbind stops autheticating, and gives errors like this: [2005/07/29 09:32:33, 1] nsswitch/winbindd_group.c:fill_grent_mem(133) ~ could not lookup membership for group rid S-1-5-21-1957994488-1409082233-725345543-512 in domain MERCYHOME (error:

Hello, We have multiple clients that are connecting to our rsync daemon, sending a small file, and then disconnecting. This works well, but rsync forks each time there is a connection. Is it possible to get a "pool" of waiting daemons, similar to how apache runs? -tom -------------- next part -------------- An HTML attachment was scrubbed... URL:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've winbindd running on Samba 3.0.11, and everything seems basically correct, however, when I run getent group, the group DOMAIN+domain users has no members listed. But if I do id CORP+nastest I get this: uid=10112(CORP+nastest) gid=10011(CORP+domain users) groups=10011(CORP+domain users) even though getent is showing: CORP+domain

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 After 2GB of transfer, files stop being written by Samba. I keep getting Jun 12 11:29:37 nasserver smbd[8715]: [2005/06/12 11:29:37, 0] locking/posix.c:posix_fcntl_lock(656) Jun 12 11:29:37 nasserver smbd[8715]: posix_fcntl_lock: WARNING: lock request at offset 558761983, length 1 returned Jun 12 11:29:37 nasserver smbd[8715]: [2005/06/12 11:29:37,