similar to: Winbind Cache not updating

-----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

-----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 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

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 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

-----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:

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

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&)

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

-----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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is there anything special that has to be done to migrate this config? Right now we're using Samba 3.0 with the old NT4 authentication through winbind, the same method that samba 2.2.8 used. If we want to recompile samba and upgrade to the new ADS support, will winbind correctly continue to use the same Windows Username to Linux UID mapping so

With Samba 3.0 in PDC mode, I see no groups in the "Add..." windows under windows 2000 security dialog. The users are present, but no groups are listed. Samba 2.2.8 would display Unix groups (in fact it would display them all.) I can't find any information as to whether or not the smbgroups is what I need to use. Am I missing something simple? My smb.conf: [global]

Hello, Is it possible to put %U or %S in the valid users line? I'm trying: valid users = %D+%U for a certain homedir setup (automagically creates if non-existent), but the level 10 logs show that it always tries: checking |MIXEDDOMAIN+dl| against |%D+%U|, and does not expand the macro. This is with Samba-3.0.0rc2 (happens with beta3 also.) Same thing happens with %U or %S. It worked in

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 knorr smbd[5439]: [2003/10/31 10:27:02, 0] lib/util_sock.c:get_socket_addr(919) knorr smbd[5439]: getpeername failed. Error was Transport endpoint is not connected knorr smbd[5439]: [2003/10/31 10:27:02, 0] lib/util_sock.c:write_socket_data(388) knorr smbd[5439]: write_socket_data: write failure. Error = Connection reset by peer knorr smbd[5439]:

&nbsp;Hi! &nbsp;&nbsp;&nbsp;I&nbsp;want&nbsp;to make windows work&nbsp; with native graphics card on xen with no iommu (no vt-d) support. With many googling, I&nbsp;find that xen with Neocleuse 1:1 No-IOMMU passthough patches maybe can meet my requestment. &nbsp;&nbsp; I download and compile a copy of direct-io.hg source, and pass my graphics card to hvm

Hello, I am getting this error when Win XP machines print to my SAMBA server. I think it is a compile issue, if so how do I recompile or get it in place. I used RPM to 'install' SAMBA. Anyone have any suggestions? I am using SAMBA 2.2.6a with CUPS 1.1.8 on Caldera OpenLINUX 3.1.1 Error: Jan 24 11:15:34 heatconlinux smbd[4787]: [2003/01/24 11:15:34, 0]

i'm currently running samba 2.2.8a as a domain member server to an NT4Server.... no problems will be upgrading the PDC to a W2K server next week... there isn't a need to use LDAP with Samba with W2KServer is there ? I can still go with my current setup can I ?

I think samba is cool. I'm trying to understand the relationship between these 3 options: Realm = MYGROUP.COM Security = ADS Workgroup = MYGROUP And my samba file server is a member of AD My server is W3K Nothing seemed to work until I specified the realm Do I also NEED the workgroup parameter ? Shouldn't the workgroup and realm parameters exclusive from each other ? -aaron