similar to: Samba 3.6.9-151 Parse_share modes: buffer too short

Anyone know the reason RHEL bumped Samba from 3.5.10 to 3.6.9? This version has a regression with BackupExec and Veeam backing up to network shares. I receive access denied errors. Samba is in security=user mode and not joined to a domain. If I downgrade just the Samba packages to the CentOS 6.3 version 3.5.10 everything works again. I've found a couple of bug reports and the one suggested fix

Hi, I'm running a cluster on 3.6.9 and am planning to upgrade to the latest 3.12.x version. I am able to schedule a downtime for the upgrade. Do I need to take intermediate steps, i.e. upgrade 3.6 -> 3.8 -> 3.12, or is upgrading from 3.6.9 -> 3.12.x fine (given the cluster is offline)? -- Marius -------------- next part -------------- A non-text attachment was scrubbed... Name:

Hi @ all, we use samba as a fileserver on CentOS and an OpenLDAP server on Ubuntu 10.04. The samba server shared only files, so we can access with the win7 clients (and OpenLDAP credentials) to the files on the linux environment. So after upgrade we don't can connected us to the samba share. I have tested the connection with the tool smbclient "smblcient -L <servername> -U

Hi, we still run a Red Hat EL 6.x samba-3.6.9-151 PDC with domain login, roaming profiles, Windws 7 clients and LDAP back end. In the last couple of weeks we notice some unregular crashes with abrt reports. But as an university our RH subscription dose not include the full support. I cant see any changes to the installation or configuration which might have an influence to the chrashes. So any

Trying to get a printer server running Samba 3.6.9 (On CentOS 6.5) going. Trying to add said printers to a Windows Server 2012 machine prior to deploying to a network of Windows 8.1 laptops. Definitely making progress; finally figured out the initial permissions issue I was having (combination of a winbind separator and using the wrong group prefix and syntax for user lists in an AD context), but

Hi, anyone tried to speed up samba file transfer over the network by turning off the kernel opportunity locking - the so called: "kernel oplocks = no"? 2 questions: 1. In scenario, where you have purely data storage filesystem (no apps, databases anything), shared only over Samba and accessed only by windows client workstations - would it be OK to use the "kernel oplocks =

After attempting to upgrade to version 3.6.23 I discovered that I was unable to authenticare against another Samba server running as a PDC and using winbind. Due to time constraints, I erased the samba setup and reinstalled version 3.6.9. Everything went back to normal. Is this a bug or did something on the configuration side change?

I set-up a basic AD DC using samba 4.1.9 successfully. I joined my NAS to the domain, i.e. I saw no errors and see the users and groups of my AD listed in the GUI of the NAS. When I try to connect to a share of the NAS the following happens: mgr at ws1:~$ smbclient -U 'AD\mgr' //nas/Test Enter AD\mgr's password: Domain=[AD] OS=[Unix] Server=[Samba 3.6.9] tree connect failed:

Hi everybody, our university uses a Samba 3.6.9 server as PDC for a windows domain on a single physical server (external LDAP on another server is used). To get some redundancy up running a second physical machine was bought, which is exactly the same as the one running. Now I?m searching for the best way to get the job done. The first thought was to build a HA-Cluster with Corosync/Pacemaker

Hi list, perhaps someone can help me out? fact: - samba 3.6.9 plus CentOS 6.5 - i have user quotas set up on their HOME directories, which resides in the "/home" filesystem - on windows workstation their disk quota is not shown, instead they see whole filesystem free/taken space (which generate much grumbling) After searching lists, googling etc., i decided to give a try the

Hello, in school We have CentOS6.5 server with Samba3.6.9 (default from CentOS3.6.9 repository). Clients are WinXP, Win7 and Win8.1, We use roaming profiles. Everything is working perfect, except that when user logs off from Win8.1 client, he is not able to log in for about 15 minutes to any Win8.1 client at school. After 15 minutes it is possible again. I do have pretty standard smb.conf, no

Hmmm... It appears I never posted the corrected version of this patch so it never made it upstream. See: http://lists.xen.org/archives/html/xen-devel/2011-11/msg00587.html http://lists.xen.org/archives/html/xen-devel/2011-11/msg02145.html It would be good if this very minor fix was also applied to 4.2 (and, if possible, 4.1). Thanks, Dan =================== The program xen-tmem-list-parse

Hello, I have a very odd issue happening, that I hope someone else might be able to give me pointers. I have two different networks running in two different locations, connected by a network vpn. In each network I have a test smb virtual machine. --------- Smb Machine 1: (smbtest1) (remote network) # cat /etc/redhat-release CentOS release 6.4 (Final) #rpm -qa | grep samba

==================================================================== "What I just said is the fundamental, end-all, final, not-subject-to-opinion absolute truth, depending on where you're standing." Steve Martin ==================================================================== Release Announcements ===================== This is is the latest stable release of Samba

==================================================================== "What I just said is the fundamental, end-all, final, not-subject-to-opinion absolute truth, depending on where you're standing." Steve Martin ==================================================================== Release Announcements ===================== This is is the latest stable release of Samba

Hello good people, I am fighting with following issue: our users are complaining about very slow/delayed displaying of main folders during accessing server using \\dns.name.of.server (using \\IP or \\netbios_name is it with same slowness). But once they are authenticated, displaying contents of (sub-)folders are getting normal. Once the user hit "enter" key on

maybe there is a bug regarding the use of nis to mount the user's home directory at the login or my misconfiguration. After the CentOS 6.4 (64bit) installation I checked for the latest samba version on the official repository using yum: the latest version (that was already installed) is samba- 3.6.9-151.el6. >From "man smb.conf" I have seen that "nis homedir" is not yet

Thanks in advance for your help. We recently upgraded from Centos 5.X samba 3.5 to Centos 6.X samba 3.6.9. Shared drives and data are accessible which indicates that user accounts were also successfully migrated. However when attempting to connect one of our Windows 7 Pro 64-bit SP1 workstation to our Samba domain controller the connection fails. I did have to add a SRV record for