similar to: smb2_validate_sequence_number: bad message_id 2

Hello to all, I can confirm, that the bug, smb2_validate_sequence_number: Jul 21 08:22:44 dom2 smbd[1908004]: smb2_validate_sequence_number: smb2_validate_sequence_number: bad message_id 2 (sequence id 2) (granted = 1, low = 1, range = 1) Jul 21 09:24:39 dom2 smbd[1908332]: [2023/07/21 09:24:39.140658, 0] ../../source3/smbd/smb2_server.c:677(smb2_validate_sequence_number) Jul 21 09:24:39 dom2

Hi, I am running Samba 4.8.2 with fruit and use it to connect a MacOS to the server. Mostly it works very good, but occasionally the connection halts or the Mac disconnects, and in the log I find these messages: Jun 20 13:00:00 orca smbd[6033]: [2018/06/20 13:00:00.856101, 0] ../source3/smbd/smb2_server.c:641(smb2_validate_sequence_number) Jun 20 13:00:00 orca smbd[6033]:

On Wed, Jun 20, 2018 at 03:40:48PM +0200, Are via samba wrote: > Hi, > I am running Samba 4.8.2 with fruit and use it to connect a MacOS to the server. Mostly it works very good, but occasionally the connection halts or the Mac disconnects, and in the log I find these messages: > > Jun 20 13:00:00 orca smbd[6033]: [2018/06/20 13:00:00.856101, 0]

On Tue, Aug 30, 2016 at 11:57 AM, Jeff Hodge <jeff.hodge55 at gmail.com> wrote: > On Mon, Aug 29, 2016 at 6:13 PM, Jeremy Allison <jra at samba.org> wrote: > >> On Mon, Aug 29, 2016 at 11:41:53AM -0400, Jeff Hodge via samba wrote: >> > During an ubuntu 14.04 update samba was updated from 4.1.6 to 4.3.9. We >> > had no problems with any windows system

Hi folks, I've been trying to get shadow copy / previous versions working under sernet-samba-ad-4.1.6-7.el6.x86_64. I cannot see where I am going wrong. I have: [global] workgroup = COMPANY realm = COMPANY.LOCAL netbios name = DC server role = active directory domain controller server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbind,

Release Announcements --------------------- This is the latest stable release of the Samba 4.17 release series. Changes since 4.17.10 --------------------- o? Jeremy Allison <jra at samba.org> ?? * BUG 15419: Weird filename can cause assert to fail in ???? openat_pathref_fsp_nosymlink(). ?? * BUG 15420: reply_sesssetup_and_X() can dereference uninitialized tmp ???? pointer. ?? * BUG

Release Announcements --------------------- This is the latest stable release of the Samba 4.17 release series. Changes since 4.17.10 --------------------- o? Jeremy Allison <jra at samba.org> ?? * BUG 15419: Weird filename can cause assert to fail in ???? openat_pathref_fsp_nosymlink(). ?? * BUG 15420: reply_sesssetup_and_X() can dereference uninitialized tmp ???? pointer. ?? * BUG

Hi List, I recently upgraded one of our high-volume SMB servers from samba 3.x to samba 4.1.12 (also changing the OS). Now I have a strange problem. The CPU load on the server is very high, processes that are causing it are nslcd or since I changed to it sssd and the smbd processes themselves. ? Top looks like this: --------------------------------- PID USER????? PR? NI? VIRT? RES? SHR S

That does indeed show "default". For logs, I tested with my system and a system that gets SMB2. Any tips for what I might be looking for? Early on in the logs, I see this for the NT1 system (no mentions of smb2 anywhere) [2016/04/19 14:48:37.738460, 3, pid=21479, effective(0, 0), real(0, 0)] ../source3/smbd/negprot.c:395(reply_nt1) using SPNEGO [2016/04/19 14:48:37.738476, 3,

Marco Gaiarin via samba ha scritto il 25/08/20 alle 18:53: > [...] >> The only other thing I can think of at the moment is to remove >> 'winbind use default domain = yes' > > It was a try, i think in NT mode don't bother at all. on my samba server with 'winbind use default domain" set to yes dominioNT\ is removed from users and groups names... >

Release Announcements --------------------- This is the latest stable release of the Samba 4.18 release series. Changes since 4.18.5 -------------------- o? Jeremy Allison <jra at samba.org> ?? * BUG 15420: reply_sesssetup_and_X() can dereference uninitialized tmp ???? pointer. ?? * BUG 15430: Missing return in reply_exit_done(). o? Andrew Bartlett <abartlet at samba.org> ?? *

Release Announcements --------------------- This is the latest stable release of the Samba 4.18 release series. Changes since 4.18.5 -------------------- o? Jeremy Allison <jra at samba.org> ?? * BUG 15420: reply_sesssetup_and_X() can dereference uninitialized tmp ???? pointer. ?? * BUG 15430: Missing return in reply_exit_done(). o? Andrew Bartlett <abartlet at samba.org> ?? *

Hi, Using the 0.10.4 gem under ruby 1.8.5 (2006-08-25) [i686-linux], I get different results with a TermQuery and a search string. Namely, using a search string seems to always work whereas using a TermQuery often doesn''t return any entries. For example: > x=@i[450][:message_id] => "9e7db9110509070759732b21c4 at mail.gmail.com" >

Release Announcements ===================== This is the third release candidate of Samba 4.19.? This is *not* intended for production environments and is designed for testing purposes only.? Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.19 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the third release candidate of Samba 4.19.? This is *not* intended for production environments and is designed for testing purposes only.? Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.19 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

I have a join table I''m creating with a migration as follows: create_table :read_global_messages, :id=>false do |t| t.column :user_id, :integer t.column :message_id, :integer end So far so good, however I want the primary key to be user_id and message_id. How do I do this? I tried the following, but that doesn''t work: add_index

Release Announcements ===================== This is the fourth release candidate of Samba 4.19.? This is *not* intended for production environments and is designed for testing purposes only.? Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.19 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the fourth release candidate of Samba 4.19.? This is *not* intended for production environments and is designed for testing purposes only.? Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.19 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements --------------------- This is the first stable release of the Samba 4.19 release series. Please read the release notes carefully before upgrading. NEW FEATURES/CHANGES ==================== Migrated smbget to use common command line parser ------------------------------------------------- The smbget utility implemented its own command line parsing logic. After discovering

Release Announcements --------------------- This is the first stable release of the Samba 4.19 release series. Please read the release notes carefully before upgrading. NEW FEATURES/CHANGES ==================== Migrated smbget to use common command line parser ------------------------------------------------- The smbget utility implemented its own command line parsing logic. After discovering