search for: vonobernitz

...server. Run this script, anonimized it and post the content to the list. Then i know all i want to know. https://raw.githubusercontent.com/thctlo/samba4/master/samba-collect-debug-info.sh Greetz, Louis > -----Oorspronkelijk bericht----- > Van: von Obernitz, Daniel > [mailto:daniel.vonobernitz at uni-greifswald.de] > Verzonden: woensdag 22 april 2020 14:50 > Aan: L.P.H. van Belle; samba at lists.samba.org > Onderwerp: Re: [Samba] pad length mismatch error message > > Hi Louis, > > it happens on the AC-DC nodes on Debian 10, running with > BIND9_DLZ backend......

..._Server Now look at the example config here and change yours acording. Smb.conf change that or add -dns server services = -dns As far i can see your dns is using samba internal dns. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: von Obernitz, Daniel > [mailto:daniel.vonobernitz at uni-greifswald.de] > Verzonden: woensdag 22 april 2020 16:33 > Aan: L.P.H. van Belle; samba at lists.samba.org > Onderwerp: Re: [Samba] pad length mismatch error message > > Hi, > > bind9_DLZ is enabled and running, DNS in general is working > absolutely fine. > &...

Hi, I found the following error message in the log.samba: [2020/04/20 16:32:33.168921, 1] ../../librpc/rpc/dcerpc_util.c:373(dcerpc_pull_auth_trailer) ../../librpc/rpc/dcerpc_util.c:373: ERROR: pad length mismatch. Calculated 44 got 0 It happens on all nodes on different times, but unfortunately I have no specific situation or action which causes this. We are currently using Samba version

...to the list. > > Then i know all i want to know. > https://raw.githubusercontent.com/thctlo/samba4/master/samba-collect-debug-info.sh > > Greetz, > > Louis > > > > -----Oorspronkelijk bericht----- > > Van: von Obernitz, Daniel > > [mailto:daniel.vonobernitz at uni-greifswald.de] > > Verzonden: woensdag 22 april 2020 14:50 > > Aan: L.P.H. van Belle; samba at lists.samba.org > > Onderwerp: Re: [Samba] pad length mismatch error message > > > > Hi Louis, > > > > it happens on the AC-DC nodes on Debian 10, runni...

Hi Andrew, > Once you work out what client is changing this, then send me a network > capture and matching Samba log (use "debug hires timestamp = Yes", "log > level = 4") and I'll add it to my backlog to look into. I think I was able to identify and reproduce the occurrence of the error message: 1. You have a new Windows 10 client 2. The computer MUST NOT be in

Hi, > > The error message itself makes sense, the computer object > > does not have write access to the ldap (and I think should > > never have), but the administrator should have them. > > No it has no rights on it's own computer object in the AD. > And they should have that. > Try joining an other computer and verify the settings. I just did a test with

Hi, when I remove a Windows client from the domain I get the following error message in log.samba: [2020/04/21 13:06:11.453483, 1] ../../source4/rpc_server/samr/dcesrv_samr.c:4071(dcesrv_samr_SetUserInfo) Failed to modify record CN=DESKTOP-C9L2OUQ,CN=Computers,DC=ad,DC=example,DC=net: Object CN=DESKTOP-C9L2OUQ,CN=Computers,DC=ad,DC=example,DC=net has no write property access The computer can

Hi Louis, it happens on the AC-DC nodes on Debian 10, running with BIND9_DLZ backend... dpkg -l |grep bind9 ii bind9 1:9.11.5.P4+dfsg-5.1 amd64 Internet Domain Name Server ii bind9-host 1:9.11.5.P4+dfsg-5.1 amd64 DNS lookup utility (deprecated) ii bind9utils 1:9.11.5.P4+dfsg-5.1 amd64

Hi Andrew, > Thanks for reporting this. Firstly, don't worry about 'attr' packages > or how Bind9 or DNS is configured etc, this is an error in our core RPC > server, and not something that is able to be configured (neither at > build nor runtime). > > A client, and we don't include enough information in the message as to > which, so you will need to turn up