similar to: MS-RPC error

Hi, We are planning to integrate CISCO-ISE with Samba-AD (Version 4.6.5). Websense gateway / proxy are all properly integrated and even single sign-on is properly functioning. However, before attempting integration of Cisco ISE with Samba-AD, through I should clarify on the following. Hence writing this mail. Cisco ISE supports LDAPs with Following authentication methods: * Extensible

Hi, Some time back I had written to the list about integrating Cisco ISE and facing errors with RPC login. When we actually integrated using ISE 2.4.0357 we noticed that Kerberos authentication is working like a charm. But MS-RPC authentication throws error. From the samba logs, we noticed that ISE workstation is able to negotiate the RPC ports switch to higher Dynamic RPC ports,

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

Hi, We did not upgrade in the real sense of upgrade. We did not directly apply the patch on the servers. Our steps were as follows: 1. Created an additional Domain Controller with Samba-AD 4.10.4. 2. Transferred the FSMO Roles to the new domain controller. 3. Stopped Samba-AD-DC and Bind9 services, demoted the Samba-4.7.6 DCs with samba-tool domain demote command. 4. Cleaned the

Hi, We were running Samba-AD - Version 4.7.6 for over 2 years without any errors. We have 4 Domain Controllers in our setup and DNS is BIND_DLZ (BIND 9.9.4). Off late (since 8th June 2019) we upgraded the Samba-AD version to 4.10.4 and all of sudden we started receiving the error "RPC Server not available" when we are trying to join the new PCs to domain. After multiple attempts

Hi, We were running Samba-AD - Version 4.7.6 for over 2 years without any errors. We have 4 Domain Controllers in our setup and DNS is BIND_DLZ (BIND 9.9.4). Off late (since 8th June 2019) we upgraded the Samba-AD version to 4.10.4 and all of sudden we started receiving the error "RPC Server not available" when we are trying to join the new PCs to domain. After multiple attempts

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,

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

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, 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, Can we export the samba audit logs (Authentication & Authorisation Logs) to Windows Event Viewer? I am trying to export the authentication & authorisation logs to a Windows Server to be shown in Windows Event Viewer. I read the link - https://wiki.samba.org/index.php/Event_Logging. But couldn't follow much. Can someone throw more light on the procedure, if it is possible? --

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

Sorry Rowland, I didn't get that mail. Let me check again and revert back to you. Regards, Ananth On Tue, Jun 18, 2019, 2:29 PM Rowland penny via samba <samba at lists.samba.org> wrote: > On 18/06/2019 09:47, Anantha Raghava via samba wrote: > > Hi, > > > > We were running Samba-AD - Version 4.7.6 for over 2 years without any > > errors. We have 4 Domain

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: