similar to: Samba 3.0.25a Available for Download

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== Old Mother Hubbard went to the NULL To get her NULL NULL a bone. When she got there, the NULL was NULL And so her NULL dog had none. --

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, I've cobbled together the svn commits for SAMBA_3_0_25 that address a few very visible bugs in 3.0.25: * The object picker error for "security = domain" * Supplementary group membership bug with "force group" * Premature password expiration on Samba DCs You can grab the patch file from

Hello all, I've tried everything I can think of, I've gone through Google and the Samba website and I can't come up with a fix for this problem. I've been running Samba 3 for at least the past year with no problems. I run a small FreeBSD 6.2 box that I use as a storage area for the windows XP systems on my network. Things have been fine up until 3.0.25 and 3.0.25a. Now,

Hi guys, I haven't seen any replies to this, but im seeing the exact same thing with Fedora 7 samba (with all the currently available patches). using winbind into a an ADS realm. My samba is 3.0.25b. Clients are XP, 2003 r2 SE and EE 32bit, 2003 r2 SE 64 bit. All work ok for a while, then suddenly start doing the same as below. I.e., when mapped it looks fine, then some time in the future

We restored to 3.0.23d after update to 3.0.25a because of strange dfs behavior. the detailed situation: on msdfs root server 'samba' ls -lR dfsroot/: drwxr-xr-x appl1 dfsroot/appl1 lrwxrwxrwx share1 -> msdfs:server1\share1 [dfs] comment = "SaMBa DFS root" path = /path.../dfsroot # next line does not work prior 3.0.25 !!! # hide unreadable = Yes

I found a solution for this, but I don't understand why this made a difference. First, here's output from testparm: ---------------------------------------------------- testparm Load smb config files from /usr/local/etc/smb.conf Processing section "[backup2$]" Processing section "[backup$]" Loaded services file OK. Server role: ROLE_STANDALONE Press enter to see a

Does anybody have any ideas on this? On our server that has been running 'rock-solid' with no crashes we have now had 3 kernel panics that each appear to have been triggered by the newly upgraded samba daemon. We used to run samba 3.0.21a for 'years' with no crashes. On May 26 we upgraded to 3.0.25 June 9 10:58:28 first crash kernel panic process involved according to log

Dear All, I have compiled 3.0.30/3.2.0 on a Solaris 10 Generic_127111-09. Samba 3.0.25a was a package from http://www.sunfreeware.com/indexsparc10.html The samba share works fine with Windows XP client on all versions. I have tried to test the password expiry feature using the command below: pdbedit -P "maximum password age" -C 300 If I now try on log on the samba logs quite

Is the issue below addressed in 3.0.25b? (no freebsd port available yet so I'm still at 3.0.25a) I can't see anything specifically about this in the release notes. I just want to add that I've also seen this behaviour on a windows xp x64 client. It's a pretty serious problem.. so I'm also thinking I may have to revert to an earlier version if it doesn't look like a

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.

I have compiled both samba-3.0.25a and samba-3.0.25b and with both I have problems setting user password longer than 8 chars with smbpasswd. I get no errors, but if I try to set a password with more than 8 chars the password will only be generated using the first 8 chars. This is on Solaris-10 update 3 on amd64 and I have compiled samba using Sun Studio 11 compiler suite and no other options to

I have been working to get pdbedit to expire passwords. I have seen several bugs related to pdbedit (bugzilla bug 4630 for example) on 3.0.25 so I upgraded to 3.0.25a, the latest Samba version as of this writing. What I am trying to do is set a particular user's password to expire on a certain date. If that can't be done, the ability to set it to expire "now" would be my

All, I am running Samba 3.0.25a on Solaris 8 and I am getting this error message in the /usr/local/samba/var/log.swat log when attempting to start swat: [2007/06/28 11:32:24, 0] lib/util_sock.c:get_peer_addr(1232) getpeername failed. Error was Socket operation on non-socket [2007/06/28 11:32:24, 0] lib/access.c:check_access(327) [2007/06/28 11:32:24, 0]

Hi, I'm running Samba 2.2 on a legacy Solaris 7 box that I need to upgrade to Samba 3 to allow Windows Vista client to access their shares. I built Samba-3.0.25a from source and so long as I ran configure with the "--without-winbind" it compiled and installed okay. It is using DOMAIN authentication so I assume that not including winbind is acceptable. I am running the new version

I have an strange issue with ldap passwd sync = only on FreeBSD 6.1 with Samba 3.0.25a + OpenLDAP 2.3.37 I have the OpenLDAP smbk5pwd overlay which successfuly synchronizes LM and NT passwords: $ ldappasswd -D 'cn=sambamgr,ou=managers,o=stars' -w sambapass -s secret1 'uid=lacoste,ou=Users,ou=Accounts,o=stars' Result: Success (0) My OpenLDAP auditlog file confirms that smbk5pwd

We upgraded from Samba 3.0.24 to 3.0.25a over the weekend and rebooted all of our clients afterwards. Since then, some of our clients are randomly getting the following error: "Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied." Unmapping and mapping the network drive fixes the problem, but one

I have a problem with the latest Samba (3.0.25a) running under FreeBSD (recent STABLE: FreeBSD 6.2-STABLE #41: Mon Jun 11 19:24:30 CEST 2007). I run multiple Samba/FreeBSD file servers (in a Windows 2003 domain with Windows 2003 DCs), and everything worked quite nicely until this week. After an upgrade (both Samba and OS), I have a serious problem with access. I am using pam_winbind with

Since upgrading from 3.0.24 to 3.0.25a this past weekend, network drive connections are randomly being closed and immediately reopened. This creates "Delayed write failed" errors for Firefox and Thunderbird, various errors for Outlook with its PST files on network drives, and errors from programs like InDesign that "The network connection was lost for the file, or the file was

Good morning, I have a working Offline Files setup w/Samba 3.0.24 (FreeBSD 6.2 host OS) and a Win XP SP2 client. Upon updating to Samba 3.0.25, the XP client's offline cache would show (as viewed via the Offline Files Folder) that synced files are write-only ('User W' in the Access column). When offline, theses files appeared to be available via Explorer and double clicking would

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