similar to: [Announce] Samba 4.13.4 Available for Download

Release Announcements --------------------- This is the latest stable release of the Samba 4.12 release series. Changes since 4.12.10 --------------------- o Jeremy Allison <jra at samba.org> * BUG 14210: libcli: smb2: Never print length if smb2_signing_key_valid() fails for crypto blob. * BUG 14486: s3: modules: gluster. Fix the error I made in preventing talloc leaks

Release Announcements --------------------- This is the latest stable release of the Samba 4.12 release series. Changes since 4.12.10 --------------------- o Jeremy Allison <jra at samba.org> * BUG 14210: libcli: smb2: Never print length if smb2_signing_key_valid() fails for crypto blob. * BUG 14486: s3: modules: gluster. Fix the error I made in preventing talloc leaks

Release Announcements --------------------- This is the latest stable release of the Samba 4.12 release series. Please note that this will be the last bugfix release of the Samba 4.12 release series. There will be Security Releases only beyond this point. New GPG key ===========

Release Announcements --------------------- This is the latest stable release of the Samba 4.12 release series. Please note that this will be the last bugfix release of the Samba 4.12 release series. There will be Security Releases only beyond this point. New GPG key ===========

Running Asterisk 1.6.2.11 on debian 5.0.6 with mpg123 1.4.3 when i start asterisk, i immediately see two mpg123 processes spawned which sit there forever. I can't imagine it's normal behavior, but if it is, please explain :) # /etc/init.d/asterisk stop stopping asterisk. #[...] # /etc/init.d/asterisk start starting asterisk. # psg aster root 14573 1 0 16:29 pts/2 00:00:00

Release Announcements --------------------- This is the latest stable release of the Samba 4.13 release series. Changes since 4.13.4 -------------------- o Trever L. Adams <trever.adams at gmail.com> * BUG 14634: s3:modules:vfs_virusfilter: Recent talloc changes cause infinite start-up failure. o Jeremy Allison <jra at samba.org> * BUG 13992: s3: libsmb: Add missing

Release Announcements --------------------- This is the latest stable release of the Samba 4.13 release series. Changes since 4.13.4 -------------------- o Trever L. Adams <trever.adams at gmail.com> * BUG 14634: s3:modules:vfs_virusfilter: Recent talloc changes cause infinite start-up failure. o Jeremy Allison <jra at samba.org> * BUG 13992: s3: libsmb: Add missing

So I just spent a frustrating day trying to get smbclient from 4.2.x and master connecting to a NetApp 8.2 box using SMB2 or SMB3 with NTLM auth. Short answer - it doesn't work :-(. Longer answer - the NetApp is choking on something inside the SPNEGO NTLMSSP packets we're sending it - giving the error that it couldn't parse the SPNEGO packet. Unfortunately (and knowing bugger-all

On Tue, Jan 20, 2015 at 03:40:48PM -0800, Jeremy Allison wrote: > So I just spent a frustrating day trying to > get smbclient from 4.2.x and master connecting > to a NetApp 8.2 box using SMB2 or SMB3 with > NTLM auth. > > Short answer - it doesn't work :-(. Longer > answer - the NetApp is choking on something > inside the SPNEGO NTLMSSP packets we're sending >

Jeremy Allison wrote on 1/22/15 11:01 AM: > On Tue, Jan 20, 2015 at 03:40:48PM -0800, Jeremy Allison wrote: >> So I just spent a frustrating day trying to >> get smbclient from 4.2.x and master connecting >> to a NetApp 8.2 box using SMB2 or SMB3 with >> NTLM auth. >> >> Short answer - it doesn't work :-(. Longer >> answer - the NetApp is choking on

Hello list, with dovecot 1.2 on AIX rquota RPC calls fail with quota-fs: remote ext rquota call failed: RPC: 1832-012 Program/version mismatch when using a netapp filer. This is what netapp says: Bug ID 97288 Title Support requested for rquota version 2 Bug Severity 5 - Suggestion Bug Status Closed Product Data ONTAP Bug Type NFS Description Linux has implemented its own extensions

Hi All, It appears the NetApp OnTap tftp server we were using doesn't implement the "OpCode: Error Code (5); Error Code: File not found (1)" response." so we just moved the tftp service to RHEL boxes running HPA tftpd. It's essential for our deployment system to locate the pxelinux config specific to an installation request based on it's MAC address. If the MAC based

If a file is stored directly on a DFS enabled share, renaming fails with NT_STATUS_OBJECT_PATH_NOT_FOUND. The usecase may sound unusual, but a customer is using NetApp ONTAP 9, which by default advertises DFS capabilities for all shares, and he cannot disable it for policy reasons. I can also reproduce the issue with smbd and Windows Server 2012 R2 (haven't checked with other versions).

Hi all, Sorry for the OT. I've got an IBM N3300-A10 NAS. It runs Data Ontap 7.2.5.1. The problem is, from the docs it says that it only supports either RAID-DP or RAID4. What I want to achieve is Max Storage Capacity, so I change it from RAID-DP to RAID4, but with RAID4, the maximum disk in a RAID Group decrease from 14 to 7. In the end, either using RAID-DP or RAID4, the capacity is the same.

I am experiencing an odd problem while attempting to mount and access a directory with smbfs. smbclient does not exhibit the same behavior. I have created a directory /mnt/smb-test and am attempting to mount a volume from a NetApp Filer running OnTap 7 with NTFS security mode. An Active Directory DC handles security for the share. The Linux machine shows as registered in AD and I can use

We are running scripts using smbclient to get some data of NetAPP filer and we run into the output below. After doing some digging, I found that there is a incompatibility between NetAPP Data ONTAP OS and samba. Is this still the case or there is a fix for it. We are running 3.0.10 Any ideas would be great George Client started (version 3.0.10). Connecting to 169.177.18.109 at port 445

Hello: Platform: CentOS 6.7 x86-64 $ rpm -qa | grep samba samba-common-3.6.23-30.el6_7.x86_64 samba4-libs-4.2.10-6.el6_7.x86_64 ie-samba-utils-3.6.13-7.x86_64 samba-winbind-3.6.23-30.el6_7.x86_64 samba-client-3.6.23-30.el6_7.x86_64 samba-winbind-clients-3.6.23-30.el6_7.i686 samba-winbind-clients-3.6.23-30.el6_7.x86_64 Problems began after requiring SMB signing (I forgot the specifics but it was

The problem you describe below is fixed in Data NOTAP 5.3x. If you're on an older version, you might want to upgrade. There's another issue, though. The fix for which should be in the next release of Data ONTAP, which isn't far off (sorry for being vague). If you're interested in a good NetApp mailing list that's not run by NetApp, drop an email to:

Hi, I'm trying to add a NetApp (Data Ontap 8.1.4) to a Samba 4.1.6 domain and it is failing with the message "Setup cannot connect to an LDAP server for the NETAPP.TEST active directory domain, and so cannot continue". I compared network packets exchanged between netapp/samba and netapp/win2008R2 and the difference is that samba returns 0 results to the query filter

On Tue, Oct 22, 2019 at 12:27:17PM +0200, Christoph Ziebuhr via samba wrote: > If a file is stored directly on a DFS enabled share, renaming fails with > NT_STATUS_OBJECT_PATH_NOT_FOUND. > The usecase may sound unusual, but a customer is using NetApp ONTAP 9, which > by default advertises DFS capabilities for all shares, and he cannot disable > it for policy reasons. > I can also