search for: 3.0.6rc2

Hi: I want to upgrade a Fedora Core 1 Linux machine that is running Samba 3.0.2a to 3.0.5. Initially, I compiled the 3.0.2a source, with defaults, and installed. The installation resides in /usr/local/samba. Can I download the 3.0.5 source, compile and install without breaking anything? Will the configuration be broken? Does anyone know a way to do this cleanly? Anyone's help is

Good afternoon. I have installed the 3.0.6rc2 version of samba and have found the users can't change their password. Cheers, Rafael Paris Gerente de Sistemas Casino e-mail: rparis@hotelmaruma.com pagina web/page: www.hotelmaruma.com Telefono/Phone: 0058 261 730 27 70 Fax: 0058 261 730 28 10

Hello! I use Windows XP SP2 on my clients. I use the http://unattended.sf.net to automatically install my WinXP machines from a MS-DOS client. This works fine in samba-3.0.5 but since SP2 causes a problem with printers I upgraded to samba-3.0.6rc2. RC2 in turn doesn't work with MS-DOS clients. The symptom is that I can boot from the fileserver but when I try to invoke a program I get

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is the second release candidate snapshot of the Samba 3.0.6 code base (the first rc was labeled as 3.0.5rc1) and should be considered for testing only. A release candidate (RC) means that we are close to the final, stable release and in provided for Quality Assurance (QA) purposes. This release is *not* intended for production servers. Use at

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is the second release candidate snapshot of the Samba 3.0.6 code base (the first rc was labeled as 3.0.5rc1) and should be considered for testing only. A release candidate (RC) means that we are close to the final, stable release and in provided for Quality Assurance (QA) purposes. This release is *not* intended for production servers. Use at

I have this problem with Samba: "create_workgroup: workgroup name PRAISENET is too long. Truncating to PRAISENET 2004/08/10 21:47:08, 0] nmbd/nmbd_workgroupdb.c:create_workgroup(68)" There are many lines like this in my logs, for every workgroup when its master browser is a Samba 3. Moreover there are duplicate domains (for the same domain) on the network Workgroup

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Summary: Potential Buffer Overruns in Samba 3.0 and Samba 2.2 CVE ID: CAN-2004-0600, CAN-2004-0686 ~ (http://cve.mitre.org/) - ------------- CAN-2004-0600 - ------------- Affected Versions: >= v3.0.2 The internal routine used by the Samba Web Administration Tool (SWAT v3.0.2 and later) to decode the base64 data

Hi, I had a compilation error of the "passdb/pdb_ldap.c" file with samba-3.0.5. I did not found the source of the problem. But samba-3.0.6rc2 compiles fine. So if someone had the same problem than me, try the 3.0.6rc2 version of samba. It worked for me. ++ Marc ------------------------------------------ Subject: [Samba] passdb/pdb_ldap.c:2651 compilation error !!! From:

I've looked through the archives and the only information I can find regarding Windows XP SP2 is RC2. Has anyone out there had ANY experience with XP SP2 Official and a Samba 3 domain? -- Bert Rapp North Trail RV Center p 239.693.8200 f 239.693.8115

Hello I just upgraded my samba from 2.8 to 3.05 and the user profiles started storing in some strange way before it used to store in /var/samba/profiles/username/machine/ now it makes /var/samba/profiles/%u directory under that machine name . it seems like something in smb.conf chnged and %u variable works no more. Can someone help?

I have been beating my head on this since the release of 3.0.4, or some time in May. I have 2 domains. 1 production, 1 test. My production domain is useing LDAP backend and has (too)many windows clients joined, XP , 2k , "98". And 2 other linux servers joined. One of these linux boxes I have replicated with my problematic box. The only thing diffrent about the replicated box is that its

After updating to samba-3.0.3-5, I began seeing problems with our NT4 Terminal Server. We are unable to copy or access large (200MB) files on the server. The file is an access file, but this doesn't seem to matter, I can't do a "copy bigfile.mdb \\cxhs\sys" Small files don't seem to be a problem. I've tried upgrading to samba-3.0.6rc2-2, no joy We replaced nic,

Hi, I'm having problems creating hard links on a samba share from a samba client. My environment is as follows: - PDC on a Windows NT - samba-3.0.5 client - samba-3.0.5 server (homes) I use winbindd to authenticate and it is working fine, I can create, remove and change files without any problems. The mount command line I'm using is: mount -t smbfs //10.101.0.231/homes /mnt -o

Hello Everyone, I've got Samba 3.0.4 running under Solaris 8 with ADS support... Doing the authentication on the ADS server works, access to the defines shares work... What doesn't work is my username mapping. My Unix usernames are in the form of gaudej and our AD names are in the form of joseph.gaude. My username.map file has gaudej = joseph.gaude and when I have the [home] share loaded

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Summary: Potential Buffer Overruns in Samba 3.0 and Samba 2.2 CVE ID: CAN-2004-0600, CAN-2004-0686 ~ (http://cve.mitre.org/) - ------------- CAN-2004-0600 - ------------- Affected Versions: >= v3.0.2 The internal routine used by the Samba Web Administration Tool (SWAT v3.0.2 and later) to decode the base64 data

I'm running debian testing, so samba 3.05 atm. As of a few upgrades ago, which i think coincided with a library restructure or somewhat samba is no longer honouring read/write/admin lists on share definitions. Using the below share as an example, previously all users could access the share with read access, and those in the ntadmins group had write access. Since the upgrade users can only