similar to: [Fwd: New Unix user and group domain]

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 For those interested in some more detail of the EventLog features in the upcoming Samba 3.0.21 release, see: http://www.samba.org/~jerry/Samba-EventLog-HOWTO.txt Thanks to Brian Mroan and Marcin Porwit at Centeris for all their hard work. cheers, jerry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with

Well, I'm attempting to migrate my old NT4-based domain to Samba3. I've got Samba set up with an LDAP backend, I've extended my NDS schema, and I've got users in this new domain set up successfully and authenticating. I've decided that the best, most seamless way to migrate my domain is to create a new domain which will run alongside the old domain. A two-way trust

Hello all, I use samba 2.0.5 in one of my machine and in other machine i use windows xp. This combination works perfectly when come into file sharing. But when i use windows vista with samba 2.0.5 i cannot use samba share. I did lots things in vista to run samba share but iot was helpless. So i like to know that if i upgrade samba to version 3 or later will i be able to run samba share with vista

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =============================================================== Done with Fish. -- John Laroche (Adaptation) =============================================================== Release Announcements ===================== This is the latest stable release of Samba. This is the version

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =============================================================== Done with Fish. -- John Laroche (Adaptation) =============================================================== Release Announcements ===================== This is the latest stable release of Samba. This is the version

Hi, yesterday I compiled an installed samba 3.0.21 on a solaris 8 box (gcc 3.4.2). Since then I frequently see this error message in the log. [2005/12/22 15:55:39, 0] lib/fault.c:fault_report(36) =============================================================== [2005/12/22 15:55:39, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 10 in pid 27816 (3.0.21) Please read the

Dear all, I have a SUN server running as ClearCase view-server and am using Samba for Interop. Today I updated Samba from 3.0.21c to 3.0.24 and now I cannot mount/start my views from windows!! MVFS error log on my windows client gives "{8 pid/tid 49800000c58/85fdf178} MvfsFsNotification: Unsupported filesystem type (6)" Samba logs don't show any error... Trying other

hi, i read about samba4wins, which is really a great work from the team! do you know, if this will work with samba v3.0.14a? i ask because a german news service writes that it?s only possible with 3.0.21 (http://www.heise.de/newsticker/meldung/69132), but i can?t find this information in the notes on http://ftp.sernet.de/pub/samba4WINS/samba4wins-1.0.0-16/ thx for helping me! -- Michael

I noticed that the Release Notes for Samba 3.0.21 say that the oplock implementation has been rewritten. And we seem to be having problems with some .exe files we are sharing out as read-only shares. The shares now only allow the first person to open the executable and run it. Other users time out with a memory address error. Do I need to specify some new oplock option for these shares now? I

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 (CC'ing back on list) Gianluca Culot wrote: > When the users change their passwords on the AD domain server > it takes one hour before winbind starts refusing the old > password (as it is in cache, I suppose) Nope. This is a Windows DC bug. https://bugzilla.samba.org/show_bug.cgi?id=2874 Unless you have enabled "winbind

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, Just a heads up for everyone. We are aware of the problem and are continuing to work on resolving it. cheers, jerry ===================================================================== Samba ------- http://www.samba.org Centeris ----------- http://www.centeris.com "What man

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just a note: You might see a flood of bug report emails. I've fixed a problem with the MTA on bugzilla.samba.org. cheers, jerry ===================================================================== Samba ------- http://www.samba.org Centeris ----------- http://www.centeris.com

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, I'm looking to remove some more old code. Does anyone use either of these features currently? cheers, jerry ===================================================================== I live in a Reply-to-All world ----------------------- Samba ------- http://www.samba.org Centeris

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, We've brought a new wiki online at http://wiki.samba.org/ for Samba users and developers alike. The intent is to allow the community to fill the gap in dynamic or temporary documentation and other relevant information. Our thanks to Craig White who has volunteered to act as standing editor (at least at first). But in general, the wiki

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Warren Beldad wrote: > I have created a user with a password of 15 characters... > then disable: > -bash-3.00# smbpasswd -d user1 > Disabled user user1. > > Enable: > -bash-3.00# smbpasswd -e user1 > New SMB password: > > Why is this happening? Is there any limitation for > the number of password characters? >

CentOS4 RPMS for x86-64 would be awesome. --------------------------------------------------------------------------- Tony Hoover, Network Administrator KSU - Salina, College of Technology and Aviation (785) 826-2660 "Don't Blend in..." ---------------------------------------------------------------------------- -----Original Message----- From:

I just found out that when doing a new installation in works. But as soon as I change the netbios name in the smb.conf the trouble begins... Everything can connect, but then suddenly the error does appear. Does Samba cache it's initial netbios name somewhere? -----Oorspronkelijk bericht----- Van: Sander van Harmelen Verzonden: dinsdag 14 november 2006 13:59 Aan: Sander van Harmelen;

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Fabio Muzzi wrote: > Hello drweb, > > Saturday, November 25, 2006, 4:32:17 PM, you wrote: > > > d> By command: > d> pdbedit -r gad -G 514 -d0 > d> I cann't change primary group. > > > I was looking through the list archives and found your post. I have > the same issue. Any solutions yet? >