similar to: Force group gid

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, I've uploaded the *final* 3.0.23c roll up patch to http://samba.org/~jerry/patches/patch-3.0.23b-3.0.23c-gwc-2.diffs.gz. I've already cut the 3.0.23c tarballs so unless there is a major problem, this will be the final change set. Please report *any* bugs that you find. I'd like to wrap this one up and do the public 3.0.23c

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:

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

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

Hi list, Using Samba 3.0.22 on a Debian box. Samba is using security = ADS and is a member server. Winbind, kerberos works as expected. BUT If I look at the security tab in windows I always see the Everyone entry. I think this is because the POSIX "other" entry in the FS on the debian box, correct? Can I remove it? If so how? Thanks, Henrik

Hi All, I havent heard a response back to my previous posts so I am now trying from a "broader" topic. What I have is the following: A 2 Form Factor Token Authentication system similar to RSA SecureID A Linux SAMBA 3.0.14a-Debian I've got the two systems authenticating against each other with RADIUS via PAM support. When I tell SAMBA to use this PAM support as well, I see the

-----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 also seeing the following in my syslog when I try and map from a Windows machine to one of my samba shares: Aug 24 07:35:49 mustang smbd[19059]: [2006/08/24 07:35:49, 0] lib/util_sock.c:write_data(562) Aug 24 07:35:49 mustang smbd[19059]: write_data: write failure in writing to client 10.0.0.14. Error Connection reset by peer Aug 24 07:35:49 mustang smbd[19059]: [2006/08/24

Since upgrading to Samba 3.0.23a, mounting a Samba share using mount.cifs generates the following errors in the Samba server's logs: Aug 7 17:45:08 pccentos4 smbd[5345]: [2006/08/07 17:45:08, 0] libsmb/smb_signing.c:srv_check_incoming_message(720) Aug 7 17:45:08 pccentos4 smbd[5345]: srv_check_incoming_message: BAD SIG: seq 2 wanted SMB signature of Aug 7 17:45:08 pccentos4 smbd[5345]:

Hi All, I'm running samba-3.0.23b compiled on a Solaris 10 system compiled against MIT kerberos. I am experiencing odd behaviour where joining the machine to the domain using 'net rpc join' seems to break the kerberos principal tickets and regular user authentication via kerberos ceases to work. My smb.conf is fairly minimal; [global] use kerberos keytab = yes unix

What is the status of https://bugzilla.samba.org/show_bug.cgi?id=3204 ? I am using latest available version of Samba from samba.org and it seems that this issue is not solved. Thanks Regards, Komal

When a do "net rpc list trustdom" I must provide a username and password for the domain admin. But if I want to revoke a trustdom I don't have to provide anything. Not a passowrd, not a user. Is this OK? Im using samba 3.0.14 in a Debian Stable.

Hi, We've recently upgraded a network from Win2k to 2k3 SBS. We were using samba with security = domain (which I believe stopped working - I was on vacation at the time the upgrade was done) and are now using security = ads. We're using samba-3.0.23b-0.1.35 on SuSE Enterprise Linux Server 9 SP3 x86_64 The samba machine has been sucessfully joined to the domain with: kinit

Hi, I have some problem with computer browser and Net Logon. I suspect the MS-patches named MS06-40 (921883). http://www.microsoft.com/technet/security/Bulletin/MS06-040.mspx Could anyone confim if this patches couse problem or not. Actually I use samba 3.0.21c and I would like to know if samba 3.0.23c could resolve problem. thanks St?phane Purnelle

When I connect from MMC (Remote Administration) of a WXPPro client with the server Linux Samba PDC, so that the users and groups of the domain neither the Unix groups/passwd do not see? I have implemented svcctl but she did not solve east problem. Any idea?? Tks

I suspect I might be grossly misunderstanding kerberos and AD here, but I cant seem to grok the following. net ads join integrates my linux samba server (named foundry) into an AD domain and all works fine. The samba server is using the kerberos keytab. root@foundry:~ # kinit -k -t /etc/krb5.keytab foundry$ root@foundry:~ # kinit -k -t /etc/krb5.keytab host/foundry.example.local kinit(v5):