similar to: Samba/Ldap problems with Versions > 3.0.24

> I just upgraded one of our samba BDC's (with LDAP back end on > solaris 10) from 3.0.23c to > 3.0.26a and can no longer mount shares. > > The error message I'm seeing in the samba logs is > > [2007/11/15 14:15:26, 1] auth/auth_sam.c:sam_account_ok(172) > sam_account_ok: Account for user 'dbb' password must change!. > [2007/11/15 14:15:26, 3]

Hi, I just upgraded one of our samba BDC's (with LDAP back end on solaris 10) from 3.0.23c to 3.0.26a and can no longer mount shares. The error message I'm seeing in the samba logs is [2007/11/15 14:15:26, 1] auth/auth_sam.c:sam_account_ok(172) sam_account_ok: Account for user 'dbb' password must change!. [2007/11/15 14:15:26, 3]

I have a problem with duplicated date_time stamps that I do not see as duplicated. I read a file with observations taken every 30 minutes: > aur2009=read.csv(paste(datadir,"AUR_ECPP_2009.csv",sep="/"),sep=";",stringsAsFactors=F) > aur2009[1:3,1:5] Date.Time E_filled E_filled_flag LE_filled LE_filled_flag 1 1/1/2009 0:00 0 NaN 5.86

As part of our deployment of FC updates we have upgraded our office server from 3.0.24-3 to 3.0.24.4. We got some strange results. Shares that have the same name as the users home directory and/or the same name as their users id became inaccessible. For example, my user id is kens, my home directory is in /home/kens and there was a share of it called kens. There is also a common share

I'm having a problem with BUILTIN accounts on a Samba 3.0.24 PDC with an LDAP backend on Ubuntu. I followed this guide for setting up the server: http://samba.org/samba/docs/man/Samba-Guide/happy.html ...and everything worked well until I migrated all the user, machine, and group accounts from the old domain and the PDC went into production this morning. Once the machine went live, I

Has anyone experienced any issues with Samba (3.0.24-r3), specifically with ADS domain joins, running on Hardened Gentoo 2007.0 (kernel 2.6.21 / AMD64)? I get "CLDAP Request Failed" error messages when attempting to do a net ads join, which has been successful with numerous other systems. This is familiar territory for us and a new issue never seen before. Thanks.

Coin, Quoting Quartexx <quartex73 at gmail.com>: > I'm experiencing your same issue. Have you found a fix for this? > Thanks in advance for your reply I downgraded to 3.2.5 to get a working version on the production server, and made a few more tests with 3.4.5. I discovered the ACL bug was linked to the full_audit vfs object, and deactivating it fixed the modification

I'm currently running samba 3.0.20a I can configure and make 3.0.20a with no problem I run the same configure command on the 3.0.24 source, configure works fine, but make returns the following. ( and just to test if a patch screwed me up I tested configuring and making the 3.0.20a version again, and it worked as it should ) Any bugs with 3.0.24??? Using FLAGS = -O -D_SAMBA_BUILD_

here's my krb5.conf:-----------------------------------------------[libdefaults] default_realm = HQ.COMPANY.COM [realms] HQ.COMPANY.COM = { kdc = 192.168.100.1 }[domain_realm] .hq.company.com = HQ.COMPANY.COM hq.company.com = HQ.COMPANY.COM----------------------------------------------- here's my

Hi all, is there a dead line for 3.0.24? Regards, LD

greetings list. am serving SMB using the samba-3.0.24 package on an openbsd 4.1-release machine and am seeing really low throughput from the server, even when both the server and client are on gigabit ethernet. the maximum throughput i've been able to attain is ~6 MBps, which is pretty slow, both on 100 Mbps and 1 Gbps segments. this top speed is identical on both 100 Mbps and 1 Gbps.

This is my setup. I am connecting to a Windows 2003 server. Everything was working fine with my old setup : 3.0.20b. krb5-1.6: (I also tried it with krb51-.5); ./configure --without-tcl --enable-shared samba-3.0.24: ./configure --with-ads --with-ldap --with-krb5=/usr/local/ smb.conf: [global] netbios name=MACHINE NAME workgroup = MYWORKGROUP realm = myactivedirectoryrealm

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've posted an updated version of my 3.0.24-gc dev branch to deal with the break in "force group" caused by the CVE-2007-2444 patch and backported the Vista related bug fixes from the Samba patches page. The bzr branch is hosted at http://people.samba.org/bzr/jerry/samba-3-0-24-gc.bzr/ The source tarball is available from

I have a machine with a running samba 3.0.24 with winbind. After an update to 3.0.25c I couldn't connect from win clients. So I first tried to rejoin and got some errors about trust account problems - sorry didn't save them. Then I deletet the account the tried a fresh join from the machine: net rpc join -Uaga -Waag -Serde Password: [2007/08/23 11:13:39, 0]

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== I can say 'no' in 4 different languages. -- Jeremy Allison ============================================================== Release Announcements ===================== This is the latest stable release of Samba. This

Hi all, I have found what appears to be a bug in 3.0.24. I upgraded from 3.0.22 and have been using this setup for some time. Also using a LDAP backend. My existing users had ldap profile directory set as follows: \\%L\profiles\username And samba home share as \\%L\username However, once I upgraded to samba 3.0.24, the server sends the windows clients the un-expanded path of

Hello, I did it from the same side on a suse 9.3. For me it worked with smpldap-useradd -m . But I had to recognize that some of the steps descriped there did not work on suse and I had to change different things in my ldap.conf and with pam and nss. Did yoe set smbpasswd -w yorldappassword and smbpasswd -a root perhaps you must have a usermap in smbusers root=administrator or just a net rpc

Hi all, I've recently managed to compile Samba v3.0.24 for OS/2 and have debugged most of the issues. The positive is that relatively few source changes were required to get the daemon working, however, having said that, there are two problems that I'm still having trouble with. 1) smbpasswd is generating a broken password - so password protected clients can't connect. eg.

Hello ! I have the following problem running Samba 3.0.24 under AIX 5.3 : It seems that the pipe winbind to \lsarpc breaks The Error Message in the Winbindd log is the following: read_socket_with_timeout: timeout read. read error = Connection reset by peer. [2007/03/07 14:49:52, 0] rpc_client/cli_pipe.c:rpc_api_pipe(790) rpc_api_pipe: Remote machine SHHDC3 pipe \lsarpc fnum 0x400areturned

This weekend upgraded a Solaris 9 system which has been using samba-3.0.10 for a while without any problems to version 24 with patches applied. When Samba-3.0.10 is running, can browse to share as well as map it without getting any prompts or failures. Under 3.0.24, get prompted for username and password and still not allowed into share. User is on Windows XP professional and AD server is