similar to: Samba Bug 12808

Hello, This is situation: * [netApps SMB-server] [RHEL-7.1-Client]* | =SMB 2/3= | | sending data>65k Fail | sending data<65k Passes Max Write/Read Size[65535]

On Tue, 31 Oct 2017 16:06:13 +0000 "Tompkins, Michael via samba" <samba at lists.samba.org> wrote: > Re-sending ... We tend to see a lot of issues with NetApp servers and > SMB 311. Not sure what might be wrong with their response packet, > that 4.6.6 doesn't like. > > ~ Mike > > > -----Original Message----- > From: samba [mailto:samba-bounces at

We are running Samba-4.6.6 and are running into an issue where it negotiates to a NetApp server but then the client stops the connection. 8262 2017-10-12 09:32:16.198917 10.136.78.14 10.128.101.128 TCP 66 45848 → 445 [FIN, ACK] Seq=403 Ack=581 Win=16768 Len=0 TSval=11546007 TSecr=3316317046 This is at a customer site, and we cannot recreate it here due to

Thanks for the quick reply Jeremy. We have other FIPS compliant libraries, which check for, and ensure the proper FIPS compliant algorithms are used. Is there a link option to specify this kind of library ? ~ Mike -----Original Message----- From: Jeremy Allison <jra at samba.org> Sent: Tuesday, October 2, 2018 2:08 PM To: Tompkins, Michael <Michael.Tompkins at xerox.com> Cc:

Sorry about the lack of info. So in the wireshark trace, our printer smbclient 4.0.7 sends a Unicode value in Russian of ???? with a password of ????123. The server rejects the login attempt with STATUS_LOGON_FAILURE. The second attempt is with the linux version smbclient 4.0.7, and the same credentials to the same server work. The only thing I see different in the requests are the flags sent:

This issue is reproducible for this customer and a couple of others. We execute the smbclient command the same way for each instance. The null user name is valid syntax sent from the smbclient. When we send the command " smbclient -c 'cd <dir>; ls' ", samba code executes starting with Negotiate Protocol Request, and onward. I'm guessing this could be a DFS issue, but

"Tompkins, Michael via samba" <samba at lists.samba.org> writes: > I'm wondering if anyone else has any feedback on this or needs anymore info ? Can you provide the output of the failing command with full debug messages (-d10)? -- Aurélien Aptel / SUSE Labs Samba Team GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3 SUSE Linux GmbH, Maxfeldstraße 5, 90409 Nürnberg,

====================================================== "Change your thoughts and you change your world." Norman Vincent Peale ====================================================== Release Announcements --------------------- This is the latest stable release of the Samba 4.5 release series. Changes since 4.5.10: --------------------- o Jeremy Allison <jra at

====================================================== "Change your thoughts and you change your world." Norman Vincent Peale ====================================================== Release Announcements --------------------- This is the latest stable release of the Samba 4.5 release series. Changes since 4.5.10: --------------------- o Jeremy Allison <jra at

I am wondering if anyone has had a chance to look at bug 12518? This is the context of the message: Wireshark trace gives a STATUS_INVALID_PARAMETER when running smbclient -c 'cd <dir>;ls' as a standalone program. This is a customer issue. We cannot recreate this issue so we're looking for why this may be happening. From the trace you'll see multiple sessions with

What is the status of cross compiling samba 4.1.0 with the new waf configure. We don't have a native compiler or emulator to use. We used autoconf in 3.6.5 and earlier, which worked successfully. We are in need of smbclient, which supports SMB2 (and maybe SMB3?) right away, so we need to resolve this issue. Thanks, Mike Tompkins

The problem is that I don't want it to use the IP address, but to use the hostname. Regards, - Mike ? ? -----Original Message----- From: samba-bounces at lists.samba.org [mailto:samba-bounces at lists.samba.org] On Behalf Of Rowland Penny Sent: Monday, April 20, 2015 10:38 AM To: samba at lists.samba.org Subject: Re: [Samba] smbclient 4.0.7 resolves host name to IP

Hai, The latest update is now online. Debian Buster Samba 4.12.5 + extra patches for amd64/i386/armhf. samba (2:4.12.5+dfsg-2.1buster1) buster; urgency=medium * Rebuild from Debian Sid for Debian Buster * d/control, re-added acl as Recommands to samba package * d/control added libicu-dev,add Missing support for Unicode normalisation. * d/patches, fix debian bug #964165 with

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

I did a similar DC upgrade from 4.1.13 to 4.6.6(like your option 1, upgrade on existing AD servers, I have two, first upgrade on none-FSMO). and I don't have any issues with the DC upgrade itself. But be careful with your member servers. After the upgrade, I have to change some default values on file servers: 1. samba 3.5.10 member server(rpm from CentOS 6.2) lost connection to samba

Our smbclient 3.6.5 and smbclient 4.0.7 does not work with SMB2/SMB3, which is a security concern for us. Is there a patch or a workaround that can be done for those releases? I've read that Apple made changes in Maverick 10.9, which now causes failures, but am hoping that something was done to support the MAC OS 10.9 releases. Regards, Mike Tompkins

When we build smbclient 4.3.3 we now have 76 shared libraries to deliver with the smbclient binary. Is there any way to specify it statically linking the libraries so we only have to deliver an executable ? With 3.6.5 and 4.0.7, we only had 3 libraries, which was more more manageable. Thank you, Mike Tompkins

On Tue, 24 Oct 2017 19:30:23 +0200 Daniel Carrasco via samba <samba at lists.samba.org> wrote: > Hello, I answer bellow. > > Thanks!! > > 2017-10-24 16:52 GMT+02:00 L.P.H. van Belle via samba > <samba at lists.samba.org > >: > > > Hai, > > > > I did a re-read of you thread. > > > > First. > > If you use smblcient, with a

We get STATUS_INVALID_PARAMETER failures when smbclient uses SMB2 but passes with NT1. We do get some success, but mostly failures. It appears to happen after it transfers the PDF file. These are the packets leading up to SMB2 failing after the transfer: No. Time Source Destination Protocol Length Info 266 2015-04-09 08:30:43.688568000

Re-sending ... We tend to see a lot of issues with NetApp servers and SMB 311. Not sure what might be wrong with their response packet, that 4.6.6 doesn't like. ~ Mike -----Original Message----- From: samba [mailto:samba-bounces at lists.samba.org] On Behalf Of Tompkins, Michael via samba Sent: Monday, October 23, 2017 2:06 PM To: samba at lists.samba.org Cc: Karuppiah, Thangavadivel