similar to: [Fwd: Re: Macro expansion in valid users = line?]

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

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

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

I've got samba-3.0.0-beta3-rc1 running, and am trying to connect to a Windows 2000 domain using security = ADS After following the instructions in the Samba-HOWTO-Collection, I've got kinit working, and am able to browse the Windows 2000 machines shares with smbclient //win2kmixed/c\$ -k without a password. However, if I try to connect to the machine, either through network neighborhood

-----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 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 Joining a mixed 2000 domain worked correctly for Samba 3.0.2a. After upgrading to either samba 3.0.9 or 3.0.10, the net ads join command completes successfully, and wbinfo -u returns a list of users, but any attempt to actually authenticate those users fails with NT_STATUS_PIPE_NOT_AVAILABLE. wbinfo -t also does not work, and produces the log file

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is this command secure? net ads password boba@MIXEDDOMAIN.LOCAL -UAdministrator@MIXEDDOMAIN.LOCAL You must supply an administrator username/password I don't want to put my administrator password on the command line; but it won't prompt me for it. Is there another way to use this functionality? Also, my administrator password cannot be typed

Thanks Jerry. My fear was the latter... -- Christopher Barry Manager of Information Systems InfiniCon Systems http://www.infiniconsys.com office: 610.233.4747 direct: 610.233.4870 cell: 267.879.8321 -----Original Message----- From: Gerald (Jerry) Carter [mailto:jerry@samba.org] Sent: Monday, January 27, 2003 2:31 PM To: Barry, Christopher Cc: Samba (E-mail) Subject: Re: [Samba] FW: Microsoft

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Couple of comments that might help things run smoother on the list. * Please post the Samba release or CVS branch runngin on your server where reporting an issue (or asking a question). This removes the first round trip of email. * I've posted some mailing etiquette rules (provided by Jonathan Johnson) on

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 8 Apr 2003, werner maes wrote: > Can you tell me where to find the change that is necessary to enable dfs > on xp clients in samba 2.2.8? Has this fix been introduced in the latest > 2.2.8a? Here's the patch to fix msdfs & WinXP clients. This was not included in 2.2.8a (only security fixes there), but is already checked

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tom, Try this patch. I lost your original message but this should fix the problem with 'logon path = \\%L\profile\%U\%a' confusing WinXP with Win2K. cheers, jerry ---------------------------------------------------------------------- Hewlett-Packard ------------------------- http://www.hp.com SAMBA Team

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 For those interested in trust relationships on Samba PDC's: Here's a patch to fix a silly bug when running winbindd on a Samba PDC and logging onto a windows client in the Samba domain as a trusted user. This fixes problems browing from one client or server to another in the domains. I thought this was going to be harder to fix or else we

Setting 'winbind use default domain = no' and adjusting my share access to use the DOMAIN+ prefix fixed the problem. There must be some portions of samba which are not friendly with this option, yet. The main reason why I like this option being, when ADS user's login to my server via ssh they can use the username alone, instead of prepending 'DOMAIN+' -----Original

Mr. Carter, I just tried the most current CVS head and IT DOES NOT FIX the problem. Can you guys look into this? Like I stated earlier, 2.2.7a works perfectly but I need to upgrade samba for security fixes, etc.. Thanks. Michael D. Brown Sr. Network Administrator Mesa Associates, Inc. 256.772.7025 >>> "Gerald (Jerry) Carter" <jerry@samba.org> Thursday, April 17, 2003

Hehe. Sorry about the caps and did not mean any ill intentions. 10-4 on the roll-up for security. Running RedHat 8.0 It is odd because if I go over 80 or so users in a group, samba will not authenticate but if you stay under that number, it works just fine. Getent groups/shadow sees the user in the correct group. Authentication to RH works fine as well. I have other LDAP enabled

Thanks for the response, Jerry. Is there a way for me to verify this is happening? Winbindd has been running for a few days now, and I just did a netstat and the only connections to a DC are to the off-site one, the PDC. Thanks. Sven -----Original Message----- From: Gerald (Jerry) Carter [mailto:jerry@samba.org] Sent: Thursday, May 22, 2003 10:19 PM To: SRuth@LANDAM.com Cc:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 31 Jan 2003, Robert M. Martel wrote: > I've followed the steps as listed in the manual. Log onto a > windows 2000 client as a user listed as a printer admin. Load the > printer driver and make the changes to reflect installed options on the > printer. Just as listed in section 6.2.2 of the "how-to" manual >

Fantastic! On Monday I'll give it a try! -----Original Message----- From: Tim Jordan [mailto:timothy_jordan@labor.state.ak.us] Sent: Fri 12/12/2003 20:56 To: Tom Dickson; m.c.hudson@open.ac.uk; admina@labor.ak.us Cc: fernandor@sescam.jccm.es; jerry@samba.org; samba@samba.org Subject: Re: [Samba] Windows 2000 and krb5 tickets...SOLVED Browsing is working from my W2K and XP

Heres is the output of truss /usr/local/samba/bin/nmbd execve("/usr/local/samba/bin/nmbd", 0xEFFFFCA0, 0xEFFFFCAC) argc = 2 open("/dev/zero", O_RDONLY) = 3 mmap(0x00000000, 8192, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0xEF7C0000 open("/usr/lib/libsocket.so.1", O_RDONLY) = 4 fstat(4, 0xEFFFF83C) = 0