similar to: Samba 3.0.12pre1 Available for Download

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is a preview release of the Samba 3.0.12 code base and is provided for testing only. This release is *not* intended for production servers. However, there have been several bug fixes and new features added since 3.0.11 that we feel are important to make available to the Samba community for wider testing. Common bugs fixed in 3.0.12pre1

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [Manny] "They think I'm a cop! I'm not a cop! I've just had too much coffee!" ==================== Release Announcement ==================== This is the latest stable release of Samba. This is the version that production Samba servers should be running for all current bug-fixes. Please read the following important changes in

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [Manny] "They think I'm a cop! I'm not a cop! I've just had too much coffee!" ==================== Release Announcement ==================== This is the latest stable release of Samba. This is the version that production Samba servers should be running for all current bug-fixes. Please read the following important changes in

Hi there, Back from leave, so here goes the debug: Best regards, Bruno Guerreiro P.S. Sorry for the large attachment. -----Original Message----- From: Gerald (Jerry) Carter [mailto:jerry@samba.org] Sent: s?bado, 19 de Fevereiro de 2005 4:09 To: Bruno Guerreiro Subject: RE: [Samba] Limit user groups -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 18 Feb 2005, Bruno Guerreiro wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 FYI.... This is a last minute reminder that the Samba XP conference will be next week, May 2 - 4, at the Hotel Freizeit in G?ttingen - Germany. More information about the conference itself can be found at http://www.sambaxp.org/. The technical sessions are listed at http://www.sambaxp.org/index.php?id=25. IMO (and I'm not on the program

OK !! What I should configure in smb.conf in order to use pam_ldap ?? Tanks again !! ---------------------------------------------------------------------------------------- Ruy de Oliveira - Analista de Suporte Mercantil do Brasil S/A Fone: (31) 3489-5960 - Fax: (31) 3489-5001 "Gerald (Jerry) Carter" <jerry@samba.org> 03/02/2005 14:24 Para:

http://us4.samba.org/samba/docs/SambaIntro.html Through his E'mail contacts, Andrew discovered that NetBIOS and SMB were actually (though nominally) documented. With this new information at his fingertips he set to work again, but soon ran into another problem. He was contacted by a company claiming trademark on the name that he had chosen for his server software. Rather than cause a fuss,

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Heads up everyone: Due to the win98 explorer bug (https://bugzilla.samba.org/bug/2501), we will be release 3.0.13 on Thursday morning, March 24 (GMT-6). So if you have any outstanding bugs in the 3.0.12 that we should know about, let us know now. Please file any defect reports at https://bugzilla.samba.org/. Thanks. cheers, jerry

I'm not an expert on that, but did you tried the following settings on smb.conf for your share : admin users = NTDOMAIN+Administrator valid users = ..... I think this is necessary to use ACL with samba and ntdomain... -----Urspr?ngliche Nachricht----- Von: Gerald (Jerry) Carter [mailto:jerry@samba.org] Gesendet: Montag, 28. Februar 2005 16:43 An: Juer Lee Cc: samba@lists.samba.org Betreff:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Heads up.... If anyone has had problems with winbindd not being able to locate any domain controllers after upgrading to 3.0.11 *and* you have 'disable netbios = yes' in smb.conf, please test this preliminary patch (winbind_find_dc.patch). It's pretty rough currently but needs some more widespread testing. You can download it from :

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Patch URL: http://samba.org/~jerry/patches/usrmgr_groups_v1.patch This one fixes issues when setting group information via usrmgr.exe and 'passdb backend = ldapsam'. The symptom in the logs is the dreaded "smbldap_open: cannot access LDAP when not root.." error. Also refer to https://bugzilla.samba.org/show_bug.cgi?id=3047

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 As promised, here's some quick docs on how to use the privilege model included Samba 3.0.11pre2. http://samba.org/~jerry/Samba-Rights-HOWTO cheers, jerry ===================================================================== Alleviating the pain of Windows(tm) ------- http://www.samba.org GnuPG Key -----

Hello I see, that "enable asu support = no: is available and I can point ADMIN$ wherever I want. I just want ask if this setting will not have any other impact to my current services (Samba installation is ADS membership). Can you provide more detailed explanation of "enable asu support = no" impact ? Thank you ! With best regards Martynas -----Original Message----- From:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Due to the varied responses that we received with the 'phantom jobs in the windows print queue listing' bug, I'm encouraging people to test 3.0.11pre2 and let me know if you still see the bug after ensuring that the $(lockdir)/printing/*tdb files have been removed. Thanks. cheers, jerry

Thanks for looking Jerry... Andrew Bartlett suggested trying spneg=no, and I'm going to test that later today... Here's the URL of my original question: http://lists.samba.org/archive/samba/2005-April/103115.html To further clarify, I've spoken to the vendor of the software that's making the connections to the server (Sterling Commerce Connect:Direct) that they intentionally

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, Here is an update regarding our current plans for the next 3.0 stable release. We have a substantial amount of changes coming into the 3.0 tree now. * New Asynchronous version of winbindd * New rpc server pipes * Support for printer migration using MS tools ~ (printmig.exe) including reading/writing binary ~ registry files. * new net

Dear all: Is it possible to set Samba share (and the files under the share) from = Samba using setfacl? I want to set up a common directory for certain = group of people to read, write and execute it (user::rwx group::rwx). I = assigned user1 as the owner of all the files under this common directory = and here is the thing: when user2(or any other users in the same group) accessed any of the =

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, I'm uploading a simple package of Samba 3.0.20 for Solaris 9 Sparc to samba.org. The configure options are ./configure --prefix=/opt/samba \ --with-acl-support \ --with-included-popt \ --localstatedir=/var/lib/samba \ --with-piddir=/var/run \ --with-logfilebase=/var/log/samba \ --with-privatedir=/etc/samba/private \

hy jerry that's what i needed. seems to work. thinking about to go with this version in production on friday, old 2.2.x version get's some performance problems. i'll test for 2 days (with low load). let you know if we have further problems. (Our infrastructur on tru64, 500 users mapped down to arround 20 samba users) who get the documents from smb-share. one last question, is it

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is a release candidate of the Samba 3.0.11 code base and is provided for testing only. While close to the final stable release, this snapshot is *not* intended for production servers. If all goes well, this this version will become the final 3.0.11 stable release (with possible minor changes). Common bugs fixed in 3.0.11rc1 include: ~ o