similar to: Export authentication & authorisation logs to Windows Event Viewer

On Sat, 2018-01-06 at 14:05 +0530, Anantha Raghava wrote: > Hello Andrew, > > Thanks for quick response. > > The requirement here is, we are deploying a Smokescreen IllusionBLACK appliance for cyber security(Deception technology, unfortunately this appliance is built on Windows), and Active Directory Decoys are created. A task is created in the appliance that can read the AD

Hi, We recently migrated the samba-ad-dc from 4.6.5 to 4.7.1. Over a period of last 15 days or so we have been observing that although the samba log rotates, upon rotation, samba will start writing the logs to both the main log file and the <main log>.old file simultaneously. While, the main log file rotates properly, instead of deleting old file and create a new one on rotation, samba

Hi, On Mon, 16 Jul 2018 17:37:21 +0530 > Anantha Raghava via samba <samba at lists.samba.org> wrote: > >> Hi, >> >> Thanks for clarification. >> >> However, we held back from implementing your suggestion and observed >> that after about 40 odd hours from the initial publishing of the >> policies, all clients connecting to any of the Domain

Hi, I have installed the Samba AD DC Version 4.6.3 and we are trying to enable Event Logging. We have followed the procedure given in https://wiki.samba.org/index.php/Event_Logging. But I am unable to get the Samba AD DC to write the events into Log. Also I am not able to figure out where the directory and files are created. We need to generate audit logs of Users and AD DC administrator

Hai, Im joining this one if you dont mind. My setup: Debian 8 (Jessie) ADDC's : samba 4.6.6 Member with profiles : samba 4.6.6 This problem is here seen also on a Windows7 Pro 64bit client. The client here, is related to the user profile, this one is having a corrupted user profile in my case. Due to this, my GPO fails and i see event id: 4098 , error code : 0x8007000E insufficions

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 Andrew, From the day one, we set the log level to 3. Log size is really huge. However, I did not see some thing very interesting and related to this error. It is all to do with user login, information, etc. Should I have to increase the log level to get more info? One thing we noticed. When we restart the samba-ad-dc service, it allows us to add new users, add new computers to domain,

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 & Louis, Yesterday by around 1:30 PM we had the same issue. Samba AD kicked all of us out and RSAT did not connect to any domain controllers. /*Incidentally the RSAT that caused this error was running on Windows 7 Professional 64 Bit edition.*/ When I restarted the samba-ad-dc service, all started working well again. However, as mentioned again, I could not trace the error

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, > Hi Anantha, > > Am 06.07.2017 um 10:02 schrieb Anantha Raghava via samba: >> Is there any way we can rebuild corrupt Default Domain Policy and >> Default Domain Controller Policy. > What is broken? Entire Default Domain and Default Domain Controller Policies along with other Polices that we had built are broken. >> In windows AD we can use dcgpofix

Hi, Thanks for clarification. However, we held back from implementing your suggestion and observed that after about 40 odd hours from the initial publishing of the policies, all clients connecting to any of the Domain Controllers started to get the policies. No client was throwing any error while applying the policies from any of the 4 Domain Controllers. Does it mean that

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

Hello, I have implemented Samba as Active Directory Domain Controller with Version 4.6.3 on CentOS 7.3, el-514. We have 4 domain controllers named as DC1, DC2, DC3 and DC4. DC1 & 2 are in one location and DC3 & 4 are in a different location. DNS is SAMBA INTERNAL. All 4 servers are properly synchronizing and even GPO updates are working properly with rsync process. However, off late

Hi, String of peculiar behavior continues... Samba Version 4.7.5, Bind Version 9.8 No. of Samba-AD-DC Servers : 4 (dc1, dc2, dc3 & dc4). All FSMO roles are on dc1. All the while all things were perfect. Yesterday, due to some reason, the BIND Service on dc2 stopped. This resulted in none of the other domain controllers could resolve the names. On dc2, only named service was stopped but

Hi, Is there any way we can rebuild corrupt Default Domain Policy and Default Domain Controller Policy. In windows AD we can use dcgpofix utility to recreate the Default Domain and Domain Controller Policies. Something similar available in Samba AD DC? -- Thanks & Regards, Anantha Raghava Do not print this e-mail unless required. Save Paper & trees.

Hi, Samba-AD-DC is working great for us here. All integration working as expected. However one small issue. We attempted to use "samba_backup" script to backup the configuration data. It works fine. However, when we set it as a cronjob, the cron triggers at the given time during the day, but the samba_backup script fails to execute. No logs either. All other cronjobs, like rsync

Hi, We have been consistently having issues with GPO and they are not consistent. We are using version 4.6.3 with BIND DNS Backend. As suggested in some of our previous communications, when we run the samba-tool ntacl sysvolcheck it results in the error as detailed below. [root at dc1 ~]# samba-tool ntacl sysvolcheck lp_load_ex: refreshing parameters Initialising global parameters rlimit_max:

Hi, Yes, we have 4 DCs & the Replication is the issue. It is taking time. But have no clue as to how to fix it. Suggestions are welcome. -- Thanks & Regards, Anantha Raghava Do not print this e-mail unless required. Save Paper & trees. On 04/04/18 10:31 PM, lingpanda101 wrote: > On 4/4/2018 12:50 PM, Anantha Raghava via samba wrote: >> Hi, >> >> On Windows

On Mon, 22 Jan 2018 20:49:59 +0530 Anantha Raghava via samba <samba at lists.samba.org> wrote: > Hi Rowland / Denis, > > Thanks for your quick reply. Find below smb.conf and named.conf for > your reference. > I would change the 'options' part of named.conf to this: options {         directory       "/var/named";         dump-file