search for: 3.0.25

Hi, I have tested winbind in samba-3.0.25-pre2 and encountered some problems. We have a working config with Linux samba-3.0.23d and W2k3 AD R2 rfc2307bis, but when I switch to 3.0.25 it stopped working. I am not quite familiar with the new configuration directives for idmap, but the old config did not work either with 3.0.25, so I tried to use the new ones. Is there apparent errors in my config

I updated all my servers to 3.0.25 early this morning. Everything seems 100% A-OK except for the most surprising thing, all my Windows and Macintosh clients, no problems. But I'm having severe difficulty with the 3.0.25 smbclient. If I use smbclient from 3.0.24 it too can connect to my 3.0.25 servers without issue. Its bizarre. Before I go into it let me say, I've got some 3.0.25

Hi. I have problems, when upgraded from samba sernet 3.0.24 to 3.0.25 (too early ?): 1) always must change password, when log in to windows XP professonall - samba 3.0.25 PDC - password expired 2) I can't browse widnows network on client machine - network broswer in WinXP don't respond - just hangs 3) I cann't priny any more to printers attached to another widnows machines

Hi, I'm currently using v3.0.24 in production and all works well. I'm testing 3.0.25 to see if I'm going to have any problems with it if I have to upgrade. I have a problem with the "force group" setting if it is set to a local Unix group. This same setting works fine in 3.0.24 but I'm denied access to the same share in 3.0.25. If I comment off the "force

Gerry, It looks like 3.0.25 breaks "stand alone/no winbind/no domain" servers. This is remeniscent of the 3.0.23b SID/GID problem. The only thing that jumps out at me is that you can't access your home share and other shares just quit working. Looking at the log files, I see this: [2007/05/14 15:24:55, 10] smbd/open.c:share_conflict(389) share_conflict:

Hi, I am setting up ctdb samba, and have hit a brick wall trying to solve the following issue. 1. getent does not retrieve the list of domain users or groups (wbinfo works fine) I'm not sure what I'm missing but I've almost spent the whole day trying to resolve this one and haven't made any progress :-( Any help or suggestions are appreciated My configuration is

I use the sernet samba packages on debian sarge and have problems after upgrading to 3.0.25 with rid mappings. My rid configuration for 3.0.24 looks like this idmap backend = rid:ISC=500-100000000 idmap uid = 500-100000000 idmap gid = 500-100000000 after updating to 3.0.25 I get a core dump of winbind (log at the end of the post) with these settings. I tried to use the new configuration

Hello, I've been testing out 3.0.25 before putting it into production and came across an issue. As a simple example.. in a share definition root preexec = echo "hey there, hi there, hello" > /tmp/hiya.txt works fine under 3.0.24 not so under 3.0.25, /tmp/hiya.txt isn't created. Cranking up the debugging and using some other similiar tests it seems to me that Samba is in

-----Original Message----- From: Wayne Rasmussen Sent: Friday, June 01, 2007 11:01 AM To: 'Gerald (Jerry) Carter' Subject: RE: [Samba] Followup Restricting to a subset of the domain controllers on a site Noticed a couple of changes with Samba-3.0.25 and wondered if I am doing something wrong or if it is a side-effect. attached three files: smb.conf, samba-3.0.10.log, samba-3.0.25.log

People who have reported this bug (Endless Password Expiration in 3.0.25, bugzilla id #4630) can you please let me know if you're working on 64-bit machines please ? I'm trying to track this down for 3.0.25a and am working on a theory.... Jeremy.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== I'm thinking with sand here! -- JFK in "Bubba Ho-Tep" ============================================================== Release Announcements ===================== This is the first production release of

I have several servers running Samba, all using security = ads mode. After updating one of the servers to 3.0.25, non-Kerberos login attempts now fail, although Kerberos logins work just fine. E.g.: $ smbclient -k -L //my-server OS=[Unix] Server=[Samba 3.0.25-0.0] Sharename Type Comment --------- ---- ------- ... $ smbclient -U username -L

Hello, I install the new version 3.0.25 on SunOS name.rz.RWTH-Aachen.DE 5.10 Generic_118855-33 i86pc i386 i86pc But it crashes if I try to write something at a share. In the samba logs I can find the lines INTERNAL ERROR: Signal 11 in pid 13573 (3.0.25) Please read the Trouble-Shooting section of the Samba3-HOWTO and in the syslog I see enunix: [ID 603404 kern.notice] NOTICE: core_log:

Hi, I'm presently testing to upgrade from 3.0.22 to 3.0.25 and have an ads problem. net -d 10 -s /etc/samba/smb.conf ads join 3.0.25: ======= [2007/07/18 12:03:11, 4] libsmb/namequery_dc.c:ads_dc_name(131) ads_dc_name: using server='ADS-2K3.ADS2K3.Q-LEAP.DE' IP=192.168.53.212 [...] [2007/07/18 12:03:11, 3] libads/ldap.c:ads_connect(394) Connected to LDAP server 192.168.53.212

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== I'm thinking with sand here! -- JFK in "Bubba Ho-Tep" ============================================================== Release Announcements ===================== This is the first production release of

Dear Samba people, I am going to upgrade a Samba domain member server, which is a member of an AD domain. Its Windows user-ids and group-ids are stored on 2 Open-LDAP servers. I have look in the mailinglists and in the docs, but have not found any good examples of how to change the old syntax into the new(in 3.0.25). Is there a place where I can find some examples ? Our old idmap config lines

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, For the minority of people who still run RedHat 9 or earlier, I will not be building an RPM for Samba 3.0.25 for that platform. If someone wants to pickup maintenance of it, I'll be glad to turn it over. I will leave the RedHat-9 packaging files in for the 3.0.25pre2 release that we are currently working on, but unless I hear an outcry

We've updated from 3.0.24 to 3.0.25 and we've noticed some minor problems such as some clients had to reboot in order to mount the share. And the log is now showing this warning all the time: WARNING: Winbindd not running, mapping ids with legacy code [2007/05/17 08:57:37, 2] passdb/lookup_sid.c:sid_to_gid(1435) We are thinking to revert to the previous version 3.0.24 which works

By mistake or by design membership in a Windows Primary Group seems to be mandatory! We are using printservers configured as member servers of Samba domains. with the following configuration security = DOMAIN password server = PDC encrypt passwords = yes map to guest = Bad Password The Samba PDCs use plain smbpasswd files. Since upgrading to 3.0.25 and

Hi List, Just a quick question for you: Does Samba 3.0.20 support the full_audit module? I've got the module operating on two boxes, one with Samba 3.0.25 and the other with 3.0.20, and only the former seems to interpret VFS directives, such as: full_audit:prefix = %u full_audit:failure = none full_audit:success = open write close On the 3.0.20 box, they seem to be ignored,