similar to: Upgrade from 3.0 to 3.5 & preserve domain trust?

I've been running samba on RHEL5 for the past couple of years with XP clients. Late last year, in order to support new Win7 clients, I upgraded from samba-3.0.33 packages to samba3x-3.3.8 (from the Red Hat-managed configuration tree) and after some struggles got everything working. But now after upgrading to samba3x-3.5.4 I am only able to connect as a known user and not as a guest. Relevant

CentOS Errata and Security Advisory 2011:0306 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2011-0306.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 0165a47460879890701501a6ba33924a samba3x-3.5.4-0.70.el5_6.1.x86_64.rpm 6e8191de3fcd3ed784857ed439fa5bce samba3x-client-3.5.4-0.70.el5_6.1.x86_64.rpm

CentOS Errata and Bugfix Advisory 2011:1007 Upstream details at : https://rhn.redhat.com/errata/RHBA-2011-1007.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: fb86795bd28ea3adb5c2a8319819bd82 samba3x-3.5.4-0.83.el5.x86_64.rpm ab308cb8053a8cf590229d03347da918 samba3x-client-3.5.4-0.83.el5.x86_64.rpm

CentOS Errata and Security Advisory 2011:1220 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2011-1220.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: d1af26928e5b3437ed117f2ffbef2cb3 samba3x-3.5.4-0.83.el5_7.2.x86_64.rpm 0277d8f285c5006f57ae9f3a50ceb8fc samba3x-client-3.5.4-0.83.el5_7.2.x86_64.rpm

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

CentOS Errata and Security Advisory 2011:0306 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2011-0306.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: dee206b3a0e56e88ccfd8c312d765af7 samba3x-3.5.4-0.70.el5_6.1.i386.rpm eb9d1d0ae9ac70e6f17d470b7bca4de0 samba3x-client-3.5.4-0.70.el5_6.1.i386.rpm

CentOS Errata and Bugfix Advisory 2011:1007 Upstream details at : https://rhn.redhat.com/errata/RHBA-2011-1007.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: 0b924fc207821b327e4a48e40015c866 samba3x-3.5.4-0.83.el5.i386.rpm 72312ee2509accb48b5ae361297e8943 samba3x-client-3.5.4-0.83.el5.i386.rpm

CentOS Errata and Security Advisory 2011:1220 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2011-1220.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: 155e4c1fd8f4165e83e602cee07f3e68 samba3x-3.5.4-0.83.el5_7.2.i386.rpm cdaf234215185ad93ae0c773edb625e2 samba3x-client-3.5.4-0.83.el5_7.2.i386.rpm

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Hi. I'm using CentOS 5 with samba3x packages (Samba 3.5.10) and Solaris 10 (Samba 3.5.8) for achieving AD integration. Samba hosts are added as domain members. Now, I've tried to add CentOS 6, which also uses 3.5.10, but have encountered a problem -> users cannot authenticate for some reason. Configurations are pretty much the same across the board, and they look like this: #

Hi Related to my previous posting on joining win7 to a domain with samba-3.6.6 (which I finally managed to do!) With Centos5 one has the option of installing either Samba which is 3.0.33 or Samba3x which is 3.6.6 with the latest updates to centos5.9 My own server was set up with samba3x and hence was able to attempt connection of win7 PC I have several customers with older installations using

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Hi, I upgraded a working centos5.5 with squid using ntlm auth to centos 5.6 today. After doing so squid failed to authenticate. Downgrading samba3x to samba3x-3.3.8-0.52.el5_5.2 got things working again. In the squid config I have, auth_param ntlm program /usr/bin/ntlm_auth --helper-protocol=squid-2.5-ntlmssp in the squid config and this was working until the upgrade. testparm shows no errors

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Well, I think this is not the only time you guys ever seen that kind of mails. First of all, I did checked all that is to be checked before writing to list. wbinfo -u and wbinfo -g work flawless. Also wbinfo -a, so I can authenticate without problems. The setup is a normal trust setup where domain X (my domain) trusts domain Y (another company).

I see via yum that there is "samba" and there is "samba3x" available for CentOS (my boxes are hooked to the main CentOS repo, Fedora EPEL, and RPMFORGE). 'samba' is 3.0.33 'samba3x' is 3.3.8 Is there any down-side to upgrading to 'samba3x' and running 3.3.8 instead of 3.0.33? I'm assuming that, in general, I should be running the latest

I have 2 CentOS 5.6 x86_64 servers configured with with samba 3.5.4, CTDB, GFS and DRDB in an avtive,active cluster. After some time winbind looses the ticket. After this I have to do a net ads join on the server to get things going. The main DC is a windows 2003 server with SP2. I do have 2 more samba 4 DC's that I use for backup authentication only that run on debian 6 that are a VM. Not

Hello, After an upgrade from 3.3 to 3.5, we ran into this bug when we tried using NTLM for authentication: https://bugzilla.samba.org/show_bug.cgi?id=7481 . To solve this issue, I am now trying to upgrade from the (latest) CentOS 3.5 packages, to the "Enterprise Samba" 3.6 packages from enterprisesamba.org. After upgrading, the SID changed, so I changed it back to the old value.

Good morning, folks. I've been driving myself to distraction trying to test out SMB2 performance under Linux. I see that the Samba on RHEL 5 is relatively old, I'm dealing with an upstream NetApp fileserver that is configured for SMB2, so I've got clients to test. The Samba on RHEL 5 is relatively old, 3.0.33, with samba3x-3.5.4 alternatively available, and cifs-utils-* available

My customer has a Centos Linux 5.10 server running Samba 3. (Samba version 3.0.33-3.40.el5_10) The machine is about three years old. I suggested that they should consider replacing it with a Centos 6 machine and Samba 4, but they decided as it was doing its job without any issues to keep it as is. I also suggested updating to samba3x but they decided not to do this. I recently installed a centos

Good morning all, I really hate emailing lists, but I've come to a wall that I just cant work out how to get past at the moment, so am hoping for some community assistance if possible. Some background: We are running Windows Server 2003 on all of our domain controllers, and are in the middle of migrating to server 2008 R2. We have unix exentions enabled (rfc2307 I believe), and manage