search for: bheemarasetti

...r with samba for each of the domains and a front server routes it to the appropriate container. That is the reason for having non-default ports and binding interfaces. >>> Is this Samba server a part of a cluster ? No, it is not part of a cluster. On Tue, Jul 4, 2023 at 4:49?PM Bharath Bheemarasetti < bharath.bheemarasetti at gmail.com> wrote: > >>> What are the DC's ? > > DC is a read-write windows active directory domain controller on Windows server 2016. > > >>> Why are you using NTLMv2 ? what is it required for ? > > The smb client here is...

...gitlab.com/samba-team/samba/-/merge_requests/3162 > And there is a bug report here: > https://bugzilla.samba.org/show_bug.cgi?id=15413 > Could this be your problem ? Thanks, that is the exact problem we are facing. Will it be backported to 4.15? On Tue, Jul 4, 2023 at 6:32?PM Bharath Bheemarasetti < bharath.bheemarasetti at gmail.com> wrote: > >>> Why are you using a non default port for SMB ? The defaults are 139 and 445. > > I not aware of the complete details but we have a dependency for the smb server to support multiple domains, so we spin up a container with sa...

...client. >>> Did you add idmap config lines for the '<workgroup>' domain ? Not yet, will add that the next time we hit the issue. >>> Is it possible you are also using sssd or something similar ? No, we are not using sssd. On Mon, Jul 3, 2023 at 1:10?AM Bharath Bheemarasetti < bharath.bheemarasetti at gmail.com> wrote: > On further investigation, the error that shows up in packet capture is > that the DC is returning [Fault: nca_s_fault_sec_pkg_error] for the > NetrLogonSamLogonEx call. There are no error logs (or any logs) regarding > the netlogon c...

...es, how do I go about debugging that as it is not apparent from the logs? P.S: We have different setups and the frequency of this error is different in all of them. Also, there is another setup with Samba 4.7 on Ubuntu 18.04 and everything works fine there. On Fri, Jun 16, 2023 at 1:26?PM Bharath Bheemarasetti < bharath.bheemarasetti at gmail.com> wrote: > First 'winbind enum' lines, they can and do slow things down in large > domains and aren't required at all, getent etc will work without them. > there are some old programs that will not work without them, but when > was...

...s there anything else that can be done to fix this permanently? You might also want to read the smb.conf manpage, you have lots of lines that I would never set. Thanks, I removed some lines which are not used anymore and will be cleaning up others shortly. On Sat, Jun 3, 2023 at 1:09?PM Bharath Bheemarasetti < bharath.bheemarasetti at gmail.com> wrote: > A couple of things possible, from 4.8.0 winbind must be running and your > smb.conf is, to be blunt, rubbish. You need to set the workgroup, you > need to have idmap config lines for the workgroup, the 'winbind enum' > lines...

...log level = 5 max log size = 1000 *Share configuration:* path = <path> guest ok = no writeable = no browseable = no valid users = "<domain>\<user>","+<domain>\<user group>" force user = root On Fri, Jun 2, 2023 at 3:21?AM Bharath Bheemarasetti < bharath.bheemarasetti at gmail.com> wrote: > Hi, > I recently upgraded a smb server from Ubuntu 18.04 to Ubuntu 20.04 which > required the Samba version to be upgraded from 4.7.6 to 4.15.13. > Post the upgrade, winbind authentication fails > with NT_STATUS_RPC_SEC_PKG_ERROR...

On Mon, Jul 03, 2023 at 01:10:26AM +0530, Bharath Bheemarasetti via samba wrote: >On further investigation, the error that shows up in packet capture is that >the DC is returning [Fault: nca_s_fault_sec_pkg_error] for the >NetrLogonSamLogonEx call. There are no error logs (or any logs) regarding >the netlogon call failure in the netlogon logs even a...

Hi, I recently upgraded a smb server from Ubuntu 18.04 to Ubuntu 20.04 which required the Samba version to be upgraded from 4.7.6 to 4.15.13. Post the upgrade, winbind authentication fails with NT_STATUS_RPC_SEC_PKG_ERROR intermittently. The error goes away on restarting the smb service but comes back after some time. There were no isses with the setup before the upgrade. Tried clearing the