similar to: DNS issues after upgrade

Hi Anantha, > The upgrade from 4.6.5 broke all the servers. Although the services were > running and there is no error message, DNS resolution failed. Even from > inside the domain controllers, DNS queries failed. > > Samba Version 4.7.1 and Named Version 9.9.4. The same issue happened > with samba version 4.7.3 and 4.7.4 > > We had to revert back to 4.6.5 to bring the

Hi, The upgrade from 4.6.5 broke all the servers. Although the services were running and there is no error message, DNS resolution failed. Even from inside the domain controllers, DNS queries failed. Samba Version 4.7.1 and Named Version 9.9.4. The same issue happened with samba version 4.7.3 and 4.7.4 We had to revert back to 4.6.5 to bring the servers back online. Now I have few

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      

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

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

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

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

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

On 23/03/23 5:08 pm, Rowland Penny via samba wrote: > > > On 23/03/2023 11:30, Anantha Raghava via samba wrote: > >> You are right. They are not starting. One of the server is throwing >> NTDS and rid related error and exit. By the way this one was having >> all FSMO roles before it was removed. I haven't tried the other one. >> I will try and & turn

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

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,

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 Rowland / Denis, Thanks for your quick reply. Find below smb.conf and named.conf for your reference. Few things I wish to clarify here. 1. We have installed the samba on CentOS 7.4 not on Debian OS. As, packages from repositories are of version 4.3 and 4.4, we have used sources, compiled & installed the package. 2. named.log had an entry "DNSKEY (.) could not be obtained, Time

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

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, I did upgrade the server to Windows Server 2008 R2 along with AD. However, when I attempt to add Samba-4 as additional domain controller, it is able to provision the Domain and starts to replicate the data. However, while replicating, it throws up an error as shown below and stops. Samba-4 will remove itself being additional domain controller. I tried this migration using Samba Version