similar to: smbclient 4.0.7 fails transfer with STATUS_INVALID_PARAMETER and SMB2 but not with NT1

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

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,

I have a kyocera TA-205C printer that is can scan to pdf and place the file on a smb share. I have a user on my domain (PCEDOM\printers) that can login and access the share. I tested it out with smbclient and was able to create a file where the printer is supposed to be able to put the file. The printer gave a very unhelpful error message, so I did a packet capture to find the error. (see

I'm wondering if anyone else has any feedback on this or needs anymore info ? Mike -----Original Message----- From: samba [mailto:samba-bounces at lists.samba.org] On Behalf Of Tompkins, Michael via samba Sent: Thursday, January 19, 2017 9:19 AM To: Aurélien Aptel <aaptel at suse.com>; samba at lists.samba.org Cc: USA Xerox Samba <USA.Xerox.Samba at xerox.com>; Futrell, Earl

"Tompkins, Michael via samba" <samba at lists.samba.org> writes: > 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 >

Mandi! Andrew Bartlett via samba In chel di` si favelave... Ok, i coma back to an old thread, because vendor finally reply. Little fast-rewind: i own some Konica-Minolta BizHub multifunction printers/copiers, and i need to ''bind'' it to my new AD domain. But authentication does not work, seems bacause that printer try to use SASL over plain LDAP (no SSL nor TLS). After

On Thu, 2018-05-10 at 15:48 +0200, Marco Gaiarin via samba wrote: > Mandi! Andrew Bartlett via samba > In chel di` si favelave... > > Ok, i coma back to an old thread, because vendor finally reply. Thanks! > > Little fast-rewind: i own some Konica-Minolta BizHub multifunction > printers/copiers, and i need to ''bind'' it to my new AD domain. > >

to my knowlidge, konica = xerox. and this works fine imo but im not able to look this up now. i did have xerox connected to my ldapS addc’s. i can check this monday. Greetz, Louis > Op 11 mei 2018 om 04:09 heeft Andrew Bartlett via samba <samba at lists.samba.org> het volgende geschreven: > >> On Thu, 2018-05-10 at 15:48 +0200, Marco Gaiarin via samba wrote: >> Mandi!

Dear all, I have a bit of a complicated tinc setup yielding weird results that I cannot explain. I would be glad if maybe someone here could help me out. I have 3 machines (with IP addresses in my tinc network) machine A (10.0.0.2) runs gentoo, tinc-1.1_pre17, behind router Y machine B (10.0.0.3) runs gentoo, tinc-1.1pre15, behind router X machine C (10.0.0.1) runs raspbian, tinc-1.1pre15, behind

Mandi! Andrew Bartlett via samba In chel di` si favelave... > > This mean that the printer try to auth in LDAP 'plain' (no SSL, no > > TLS), and so samba refuse that? > No, it means that Samba is refusing to accept a NTLM or Kerberos > authenticated connection without SIGN or SEAL negotiated, as an > attacker could take over an unprotected network connection and do

I'm trying to test/move some of my LDAP-enabled devices from my actual OpenLDAP server(s) to my new samba AD domain. For now, i'm poking with printers, and i'm testing a Konica-Minolta BizHub C224e. Defining user autentication to external source, i can set (between LDAP, NTLM, NDS, ...) 'Active Directory', and i can/must provide the domain naime. After that, DNS and kerberos

Hello everybody, I have a problem with LDAP userdb and dovecot. Let me first explain my LDAP configuration: I got three Active Directory LDAP servers (a.galliera.it, b.galliera.it, c.galliera.it) responding round robin to the name galliera.it. I want to use LDAP for the userdb lookup, so I configured dovecot-ldap-userdb.conf.ext as follow: hosts = galliera.it # round robin base =

Hi. I upgrade samba-ad-dc 4.12.6 to 4.13.2. I use GoogleWifiAP, it sometime access SambaAD-DC internal DNS by TCP protocol. Since recently, I troubled More and more connections without closing. TCPDUMPed(and wireshark) > No. Time Source Destination Protocol Length Info > 23 2020-11-10 19:21:40.775442 [GoogleWifiAP] [SambaAD-DC] TCP 74 48861 ? 53 [SYN] Seq=0 Win=29200 Len=0 MSS=1460

Hi, We're encountering a rather weird, sporadic hang during a large-file transfer. A bit of background on the setup: - Host A rsyncs a MySQL database from Host B. Both sides use rsync 3.1.1 on Debian Jessie. - Host B serves the files using rsync --daemon from an ext4 filesystem residing on a thin LVM snapshot. - Host A uses the following command to rsync the files to a btrfs

Mandi! Rowland Penny via samba In chel di` si favelave... > I think that is what Andrew is trying to tell you, the printer needs to > support SASL over TLS/SSL or it will never work. I don't think there is > anything you can do, but I am surprised that the print doesn't already > support it, after all, it isn't something new ;-) Mi confusion grow. ;-) As stated in my

I have a system in place where it appears that TCP will make a massive change in behavior mid-stream with existing SSH sessions. We noticed the issue first with an application using an SSH forward. However, we were able to rule that out by generating the same TCP characteristics by having a perl script dump text out to a terminal simulating a large data flow from the far end(ssh server) back

Mandi! Andrew Bartlett via samba In chel di` si favelave... > > There's some way to ''tight'' that configuration , eg permit 'ldap server require strong auth = > > no' only by some hosts? > > Or some other smb.conf options that i've missed? > Nothing at this stage. Ok. > The issue is that they need to do fully signed or sealed Kerberos