similar to: Peculiar Problem with DNS

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

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

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

Now, its getting more detailed for the samba devs and more out of my scope.   But a small last question from me. Are you moving OU's with users and are there GPO's liked to these OU's? If yes, detach the GPO link and try moving without GPO's attached.   Still errors? Are these users logged in or not? If still logged in, try an OU without users logged in.     I also did read

Hello Rowland, ldbsearch command is returning 0 records. # returned 0 records # 0 entries # 0 referrals On the backup front, I take the back up using samba-tool backup command and it was successful. Can I create a new ForestZone using samba-tool? I asking this question as RSAT is not connecting to DNS server. Thanks & Regards, Anantha Raghava H A This e-mail communication and any

Hi, No great technique. We have two Virtual machines with RSAT connected two domain controllers of the same location, same network segment. When we create an object in say OU in one of the domain controllers, we expect the object to be replicated immediately to the other. It appears in the second server after about 3 - 4 minutes and continuous refresh. By the same time it appears in the DC

Hi, Last evening we upgraded one of our 4 Domain Controllers from 4.6.5 to 4.7.1 and all of a sudden the DNS resolution issue started. We are using BIND9_DLZ back end. This server we had upgraded has all 7 FSMO Roles. Some time back we upgraded the other 3 servers from version 4.6.5 to 4.7.1 and there was no issue at all. I have also observed a very peculiar behaviour that is all of a

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

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, We have 4 Domain Controllers (2 in Bangalore and 2 in place that is 350 KM away from Bangalore, connected by a 200 Mbps Point-To-Point link) in our setup. Off late I am finding that the data replication is taking time (about 3 - 4 minutes). I did run samba-tool dbcheck command on all 4 servers and it did not return any errors. It is also noticed that the synchronization between the

On 22/03/2023 01:04, Anantha Raghava via samba wrote: > Hi, > > While upgrading Samba-AD fromm 4.15.9 to version 4.18, I ran into a > peculiar problem. AD Component is up, but DNS is just not coming up. > kinit is reporting KDC not found problem. > > All these years I have been compiling samba from source and for nearly 7 > years, it was working like a charm. But this

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

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, 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, 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

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 are using Samba AD DC (Version 4.6.5) on CentOS 7.3. We have two servers with BIND9 DNS and all are working just fine. Today, when we attempted to move couple of users from one OU to another, Windows RSAT reported /*"Windows cannot move object. Ther*//*e *//*is not enough storage space*//*"*/. Our servers have 300 GB Storage more that 270GB is free on the storage. At the

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, While upgrading Samba-AD fromm 4.15.9 to version 4.18, I ran into a peculiar problem. AD Component is up, but DNS is just not coming up. kinit is reporting KDC not found problem. All these years I have been compiling samba from source and for nearly 7 years, it was working like a charm. But this upgrade activity, we ran into rough weather. We do not upgrade the existing servers where as,

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