similar to: Rev #2 of the 3.02.3c patch

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, I've upload the preliminary patch against 3.0.23b that will become 3.0.23c so people can do full testing against what we hope to be the release code. Note that the reported version in the patch is 3.0.23c-gwc-1 to prevent confusion from the final 3.0.23c release. You can download the gzipped patch file from

Gerry, all: HELP! On mandriva, I compiled samba from source and got it running, but I cannot connect from windows. (see my post from earlier "[Samba] Compiling and Configuring Samba for Mandrival") I think this relates to the group/SID changes discussed in the release notes. However, I'm not smart enough to figure it out. The tarball compiled and installed fine. It

Yesterday evening I upgraded my FreeBSD 5.5-RELEASE Server from Samba 3.0.22 to 3.0.23. This gave me a LOT of work today... :-( This is what I found so far: My Samba-Server is member of a large ADS-Domain. After the upgrade, file based Usermapping didn't work anymore... better: it worked TWICE. (I once opened a PR for that a few years ago :-). So, with LogLevel 3:

POSTED TO THE LIST W/O ATTACHMENTS -------- Jerry, I am sending this to you directly because it contains the tcpdump information in addition to the samba logs just in case there is sensitive information contained in the files. What is happening is that samba 3.0.25c, after first running smoothly, is becoming very "chatty" across our LAN. I don't know why, but with no files or

-----Original Message----- From: M. D. Parker [mailto:mike.parker@ga.com] Sent: Thursday, August 10, 2006 9:02 AM To: 'samba@lists.samba.org' Subject: HELP -- Problem with access list on samba 3.0.23b but not on 3.0.20c PDC I am using samba with NO windbind and a configuration file that has worked for years stopped working at 3.0.23b. The affect was that my [netlogon] area was not being

I'm compiling samba-3.0.23b as I write this. However, after studying the documentation, I have some serious concerns about installing it. The WHATSNEW file says that the method of mapping unix-native uids and gids to SIDs has changed since 3.0.22. As I read this, this would imply that upgrading Samba will cause much breakage because domain users will no longer be able to access files they

I portupgraded my working 3.0.23b PDC on FreeBSD 5.5 to 3.0.23c and found that all workstations could not login. The log file reads: get_md4pw: Workstation PC01$: no account in domain I ran pdbedit -L, and it returned nothing. I use tdbsam backend; all user accounts show up fine with 3.0.23b. Now they are missing. I deinstalled 3.0.23c and switched back to 3.0.23b. Everything is then back

Mates, The saga continues, but THANK GOD 'make revert' WORKS. Here is my problem. I am trying to compile 3.0.7 from source and install it on my Mandrake 7.2 box. The gcc compiler is 2.95.3. Here is what I have done: [stop samba] # ./configure --prefix=/usr --with-smbmount # make # make install # /etc/rc.d/init.d/smb start Here is what I get: [root@Nemesis david]# tail

Hello all, I'm running samba3 as domain controller. I have upgraded samba from 3.0.22 to 3.0.23b and faced an issue with groups display: samba does not see any groups. "net rpc group -U Administrator" returns empty set. usrmgr.exe does not show any groups also. Groups are present in ldap, nss_ldap works fine: # id asv uid=2005(asv) gid=513(Domain Users) groups=513(Domain Users),

Mates, What would cause smbclient not to list my printer share?? (mandrake 7.2, 2.2.19 kernel) [david@Nemesis david]$ smbclient -U% -L localhost Domain=[RB_LAW] OS=[Unix] Server=[Samba 3.0.7] Sharename Type Comment --------- ---- ------- guillory Disk David Guillory Bertin Disk Darren Bertin Rankin

I installed a PDC some days ago for some 15 users/PCs (w98,2000,xp), with samba 3.0.23b-1 and valid users wasn't working. I'm going to update to 3.0.23c which solves that problem. I'm using smbpasswd passdb backend. In /etc/group I have only two groups. I don't understand very well the changes related to primaryGroupSID and RID commented in previous posts. Please, is it

Hello all, I am not sure if this is a bug or a feature of the newly released Samba 3.0.23c. I had this samba.conf working fully ok for smbd 3.0.23b : [global] map to guest = Bad User guest account = nobody disable netbios = Yes lanman auth = No unix charset = ISO8859-15 display charset = ISO8859-15 printing = bsd workgroup = OAAD

Have been running samba successfully authenticating to a windows 2003 domain since 3.0.1. Starting in 3.0.23 and 3.0.23b I can't do a "net ads join" on a HPUX itanium server running 11.23 ia64. I can kinit just fine w/ this userid. Samba was built with gcc 4.1.1. See below: root@serv00 # kinit jjurich_wa Password for jjurich_wa@DIVMS.UIOWA.EDU: root@serv00 #

I have several groups in /etc/groups on my samba server. I upgraded to samba 3.0.23b and then users couldn't connect to any shares they were groups on in /etc/groups (shares used valid users = @groupname) but could connect to shares where valid users = their_username. I did some reading and saw the group mapping change at

Mates, I have configured samba 100 times, but this time, I'm doing something increadibly stupid that I just cannot see. Please HELP! I'm about to jump...... Background, Old samba sever (nemesis) being replaced with new one (bonza). Both are up and operating. All networking is OK, Name resolution is fine, etc. The problem is that all users can see all the shares on the

hello when I try to install samba 3.0.23b I get this error error: Failed dependencies: perl(Unicode::MapUTF8) is needed by samba-3.0.23b-1 is this perl module required since 3.0.23b? and why? can you use 3.0.23b without it? werner Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm

Hey everyone, I'm preparing for a transition in which I'll be moving everything (PDC, WINS server, big file shares) off an old Linux server running Samba 2.2.7 onto a much newer Linux system running Samba 3.0.22. In the process, I'll be switching from smbpasswd (only thing supported under Samba 2.x, if I understand correctly) to ldapsam on Samba 3.x. I want to keep the same domain

Hi All, Just upgraded a test box to 3.0.23b and discovered some changes that cause a panic. I had an smb.conf with passdb backend = tbdsam guest The guest bit now causes panic action. log.smbd complains ... "No builtin nor plugin backend for tdbsam guest found" Either the build options have changed or the guest operative has issues. Works OK without guest, but it's been

I portupgraded my samba domain server and domain member to 3.0.23b from 3.0.23 and found that the domain member was not accessible from workstations. The error message: \\HOSTNAME is not accessible. There are currently no logon servers available to service the logon request. In the log.winbindd of the domain member, I found: [2006/08/23 22:52:00, 0] nsswitch/winbindd.c:request_len_recv(517)

I have aix with 3.0.21c samba with the following smb.conf: [global] workgroup = MYDOMAIN realm = MYDOMAIN.COM server string = User management Server security = ADS password server = ad.mydomain.com idmap backend = rid:MYDOMAIN=100000-200000 allow trusted domains = No log level = 0 log file = /usr/local/samba/var/log.%m