similar to: Sudden authentication failures, hex dumps in log.samba

Hi list, I'm getting a lot of these on a CTDB cluster serving files to Windows clients: [2016/06/24 08:53:55.555485, 1] ../librpc/ndr/ndr.c:578(ndr_pull_error) ndr_pull_error(11): Pull bytes 4 (../librpc/ndr/ndr_basic.c:150) [2016/06/24 08:53:55.555506, 1] ../source3/locking/share_mode_lock.c:141(parse_share_modes) ndr_pull_share_mode_lock failed: Buffer Size Error [2016/06/24

On Samba 4.12.0, I receive the error "ndr_pull_uint32: ndr_pull_error(Buffer Size Error): Pull bytes 4 (../../librpc/ndr/ndr_basic.c:152) at ../../librpc/ndr/ndr_basic.c:152" when opening the DNS Manager in MMC. This jumped out at me from the log-level 10 output (I'm happy to send the full logs but would rather do that somewhere more private): /dnsserver: Found DNS zone

I opened bug 14310 (https://bugzilla.samba.org/show_bug.cgi?id=14310). Are attachments I upload there already restricted or do I have to do that myself? Alex On 14/03/2020 22:38, Andrew Bartlett via samba wrote: > We normally do this via attachments to bugzilla bugs restricted to the > samba developers group. Start by filing a bug about this. > > Andrew Bartlett > > On Sat,

No worries Andrew. I haven't upgraded all servers yet so it's not urgent! Is there a secure place I can upload my logs for when there's time to take a look? Cheers Alex On 05/03/2020 23:21, Andrew Bartlett via samba wrote: > On Wed, 2020-03-04 at 18:07 +0000, Alex MacCuish via samba wrote: >> On Samba 4.12.0, I receive the error "ndr_pull_uint32: >>

Hi all, Sernet Samba 4.2.2 as Active Directory on Debian 7.8. No other DC. I can't log in with on Windows systems (Windows 7) when samAccountName are longer than 20 characters. This seems to be a LAN MAN or NT4 limitation which should not happen on AD domain. Any idea what could leads my to that limitation? I can log in using administrator account or any other having a short (enough)

Hi Alex I've had the same DNS manager issue. I've opened a bug (https://bugzilla.samba.org/show_bug.cgi?id=14310) and reported on the mailing list (https://lists.samba.org/archive/samba/2020-March/228772.html) No fix yet. On 18/03/2020 15:43, Alex via samba wrote: > Rowland, > > I've encountered an issue with connecting to the samba DC's DNS service from DNS >

I am soo lost trying to get Samba AD 4.7.5 as a Kerberos source for NFSv4. The NFS server is the Samba AD server running Ubuntu Server 16.0.4.3 and the client is Linux Mint 18.3 This export WORKS and mounts on client ########## /etc/exports ########## /mnt/fileshare         *(rw,no_subtree_check,async) ############################ This export DOES NOT ########## /etc/exports ##########

Hi all, James, After following James' suggestions fixing the several dbcheck errors, and having observed things for a few days, I'd like to update this issue, and hope for some new input again. :-) Summary: three DCs, all three running Version 4.5.10-SerNet-Debian-16.wheezy, samba-tool dbcheck --cross-ncs reports no errors, except for two (supposedly innocent) dangling forward links

Hi, I had Samba 4.2.14 working as AD DC with shares. After upgrade to version 4.3.11 AD DC authentication, ADUC, etc, stopped working. Shares still work fine. OS. Oracle Linux 6.x with UEK, uptodate. Samba compiled from source. Upgrade procedure (nothing special): ./configure --enable-selftest make make install Testparm output: # Global parameters [global] workgroup = EXAMPLE realm =

Hi guys, about a one or two weeks ago I've updated my samba to v4.1.7 which might or might not relate to the problem at hand. However lately we've seen some issues with users not able to login to workstations (win 7). Windows servers (2008 r2 and newer) were also affected. Sometimes one or two reboots would solve this problems, on few occasions I had to rejoin the computer account to the

Hi everyone, A quick question: Is check password script option working for ad dc setup? I believe, ad on it's own cannot provide password protection against dictionaries.

I made some progress with the issue, but didn't solve it completely It's basically a kind of bug (i'm not sure if it's on kerberos side or samba, I think samba is the culprit here (?). Microsoft uses kind of weird SPN for Hyper-V. Weird as there are "spaces" in the string - which is kind of unique as far as SPN's go, usually SPN form a complete string. So I kind

Hello, I just found and odd behaviour here on my test environment (debian jessie with samba 4.4.5 backported from sid). I create and ad-dc as usual, adjust nsswitch.conf and enable pam-auth-winbind (ruuning pam-auth-update). I also define /bin/bash as template shell. Now after i create an samba-user and the users home directory (/home/DOMAIN/achim). I can login with that account on the

Hello Rowland, >> During the migration from Windows DCs to Samba DCs, the following issue came up: >> after transferring PDC emulator role to a samba DC, the according DNS record >> wasn't re-created: >> > Yes and no (well not in the way you are thinking) > Yes, you are missing the fact that the dns_update_list has this: > # The PDC emulator >

I'm working on building a CTDB/Samba cluster on AIX 7.1 with the latest levels to replace an older one running CTDB 1.0.113 and Samba 3.6.1. I have the new servers up and running and they seem to work, but I'm worried about some messages in the logs. I run with log level 1 on the servers so that the connection details are logged. On the old cluster there were only connection/closed

On 28/01/16 21:32, Wayne Merricks wrote: > Apologies, managed to venture onto the dreaded 2nd page of Google and > found an answer. > > If anyone gets stuck add --server to the end of the command and this > points samba-tool directly to the DC you wish to use for joining. > > E.g. my dc of ukads001.int.thevoiceasia.com makes this command: > > sudo samba-tool domain

Everytime I try to login using windows credentials to my db instance I get the error: ORA-12638: Credential retrieval failed. Looking at my alert log I find: ns main err code: 12638 which means the database is not able to connect the domain controller. The database connector makes use of NTLM protocol to authenticate. Is it supported by samba4 (4.1.16)? I'm unable to find any

On 10/29/2018 1:57 PM, Rowland Penny via samba wrote: > On Mon, 29 Oct 2018 13:20:18 -0400 > James Atwell via samba <samba at lists.samba.org> wrote: > >> Hello List, >> I'm receiving several of these messages in my samba >> log file. I'm not entirely sure what the errors are referencing >> either. I'm under the assumption DNS

hey, now after observe last changes on the weekend… i have also the issue. After 10 hours i can’t connect to the shares on my member server. On Log of DC i found this: [2016/10/02 20:35:45.601265, 3] ../source4/auth/kerberos/krb5_init_context.c:80(smb_krb5_debug_wrapper) Kerberos: AS-REQ PL0024$@HQ.KONTRAST from ipv4:<member-ip>:55578 for krbtgt/HQ.KONTRAST at HQ.KONTRAST [2016/10/02

Hello. Samba 4.1.0pre1-GIT-aad669b, joined as a DC to an existing domain. Windows 7 machines may fail to get a ticket: [2012/10/03 09:31:54, 3] ../source4/auth/kerberos/krb5_init_context.c:80(smb_krb5_debug_wrapper) Kerberos: AS-REQ con-11$@KLIN.KIFATO-MK.COM from ipv4:192.168.1.138:49682 for krbtgt/KLIN.KIFATO-MK.COM at KLIN.KIFATO-MK.COM [2012/10/03 09:31:54, 3]