similar to: Disaster Recovery Activity with Samba-AD-DC

On Fri, May 17, 2024 at 03:01:44PM +0530, Anantha Raghava via samba wrote: >Hi, > >We increased the CPU count of one of the samba-ad servers in Data >Center B, and the problem seems to have come under control, despite an >observable delay. It is also observed that on one of the servers that >held PDC Emulator, naming, dnsname, forestdns FSMO roles, the CPU >consumption was

Hi, We increased the CPU count of one of the samba-ad servers in Data Center B, and the problem seems to have come under control, despite an observable delay. It is also observed that on one of the servers that held PDC Emulator, naming, dnsname, forestdns FSMO roles, the CPU consumption was consistently over 85% consistently and even spiking to 100% . Except samba-ad-dc, no other services

Hi, Let me just check this and revert back. -- Thanks & Regards, Anantha Raghava DISCLAIMER: This e-mail communication and any attachments may be privileged and confidential to eXza Technology Consulting & Services, and are intended only for the use of the recipients named above If you are not the addressee you may not copy, forward, disclose or use any part of it. If you have

Hello Rowland, > On Sat, 30 Jun 2018 14:51:48 +0530 > Anantha Raghava via samba <samba at lists.samba.org> wrote: > >> Hi, >> >> We have been using Samba File Server (Version 4.3.11 Ubuntu 14.04 >> LTS) for quite sometime now. We recently installed Samba-AD (Samba AD >> Version 4.7.6) and made the file server a member of the Domain. >> Everything

Hello Marc, Upgrade DNS worked properly as you can see below. --------- samba_upgradedns --dns-backend=BIND9_DLZ Reading domain information DNS accounts already exist No zone file /usr/local/samba/private/dns/EXZA.LOCAL.zone # is this the culprit? DNS records will be automatically created DNS partitions already exist dns-dc account already exists See

You guys mix to things. > AFAIK is the 'privileges' that are host-specific. Is correct. >the policies are on the domain (in the LDAP data, > the root DN, look at them!). Yes, but only the GPO policies and these are not applied to the samba server. And because of that, samba-tools password settings needs to be set on every DC. Greetz, Louis > -----Oorspronkelijk

Hello James, Thanks for your quick response. Find attached smb.conf file from DC1 and DC2. Also attached the screen shot of the event viewer from the workstation. At the moment, we have brought down the DC3 and DC4 in another location and observed that DC2 is unable to replicate get the information from DC1 or send the information to DC1. It appears replication is working in background but

> On Sat, 30 Jun 2018 21:09:07 +0530 > Anantha Raghava via samba <samba at lists.samba.org> wrote: > >> Hello Rowland, >>> On Sat, 30 Jun 2018 14:51:48 +0530 >>> Anantha Raghava via samba <samba at lists.samba.org> wrote: >>> >>>> Hi, >>>> >>>> We have been using Samba File Server (Version 4.3.11 Ubuntu 14.04

On Sat, 2017-12-02 at 11:58 +0530, Anantha Raghava wrote: > Hello Andrew, > > Thanks for proper explanation.  > > To overcome this,  also as we need to store logs for long,  now we > have written a shell script,  executed as a crop every three minutes > that checks the file size.  If the file size is 1 GB or above,  it > moves the log file to

Hi, We are running Samba-AD and all things are working absolutely fine. However, two very specific issues observed one related to Windows Clients (Members) automatically synchronizing the time with PDC emulator and second password policies are not getting enforced. /*Time Synchronization:*/ Normally, in totally Windows environment, when adding a windows PC (Or server) to a domain as a

Hi, I am trying to upgrade frm INTERNAL DNS to BIND_DLZ. I followed the procedure given in https://wiki.samba.org/index.php/Changing_the_DNS_Back_End_of_a_Samba_AD_DC and https://wiki.samba.org/index.php/BIND9_DLZ_DNS_Back_End. When I start the BIND Service, it fails with an error. In journalctl -xe we come to know that named service is unbale to open dlz_bind9_9.so file. Full error message

Hi, Although Samba is listening on port 3268, proxy returns error "unable to connect" Any suggestions to fix this? -- Thanks & Regards, Anantha Raghava DISCLAIMER: This e-mail communication and any attachments may be privileged and confidential to eXza Technology Consulting & Services, and are intended only for the use of the recipients named above If you are not the

Hello Marco, I was also searching about this. The updates are: Windows Server 2022 - KB5028171 Windows 11 - KB5028185 Windows 10 - KB5028166 On Monday, we will remove this update on couple of members and check. If it sets back to normal, I will report back here. Thanks & Regards, Anantha Raghava H A DISCLAIMER: This e-mail communication and any attachments may be privileged and

Hi, After upgrading to BIND9_DLZ, BIND service is properly starting. However, DNS updates are failing. When I try to force the DNS update, I get the following error. Even kinit command returns "kinit: Cannot find KDC for realm "EXZA.LOCAL" while getting initial credentials" --------------------------------------- [root at dc ~]# samba_dnsupdate --verbose --all-names IPs:

Hello.. Can we promote the Samba AD DC (Version 4.6) to be a global catalogue server? We need to integrate Websense Proxy with this and Proxy server searches Global Catalogue on Port 3268. -- Thanks & Regards, Anantha Raghava eXzaTech Consulting And Services Pvt. Ltd. DISCLAIMER: This e-mail communication and any attachments may be privileged and confidential to eXza Technology

Hello James, Even after setting the rfc2307 in smb.conf replication error continues and password change error continues. Error thrown while forcing replication is shown below. ------------------------------------------------------------------- Even after setting RFC, DC2 is not getting synced from DC1. Connection time out error comes. #samba-tool drs replicate DC2.KTKBANKLTD.COM

Hi, We provide DC Host's IP address and port as 3268 and user DN of administrator as CN=Administrator,CN=Users,DC=ktkbank,DC=com and supply password. But proxy reports "unable to connect to directory". However, the Proxy's Content Gateway is a member of AD DC and it uses integrated windows authentication. -- Thanks & Regards, Anantha Raghava DISCLAIMER: This

Hi, In samba logs I see these entries. {"timestamp": "2024-03-22T17:00:13.553400+0530", "type": "Authentication", "Authentication": {"version": {"major": 1, "minor": 2}, "eventId": 4624, "logonId": "d42e868adc3300ef", "logonType": 3, "status":

Hello Andrew, A gentle reminder for the patch. Can you share the patch as you mentioned? -- Thanks & Regards, Anantha Raghava Do not print this e-mail unless required. Save Paper & trees. On 29/10/17 11:57 AM, Andrew Bartlett wrote: > On Sun, 2017-10-29 at 09:11 +0530, Anantha Raghava wrote: >> Hi, >> >> I did upgrade the server to Windows Server 2008 R2

Hi, This morning, again we encountered the same issue. When RSAT reported the RPC Server error, the replication between servers was failing as well. As you suggested, we rung the dbcheck command, which threw the mismatch on count of deleted objects. 3 servers had 3 entries in deleted objects whereas the 4th server had 4 entries in deleted objects. samba-tool dbcheck --reindex did not fix