similar to: RPC Server Unavailable - 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

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

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

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 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 James, Thanks for your suggestion. When we had two servers in the pool, we were pushing GPO using rsync from PDC at every 30 minutes. However when we added the two more domain controllers, our rsync script turned to be a pull from PDC every 30 minutes. Would this have made those policy objects inconsistent? We have set up sysvol replication using rsync unidirectional that is a push

Hi, We are using Samba AD 4.6.3 and built it from source on CentOS 7. The DNS back end is BIND 9.9.4 Initially all replications were working fine and all group policies were getting applied. All of a sudden, we are finding that GPO applying process is erratic. Sometime it applies and sometimes not. We have edited the Default Policy using Windows RAST tool. Thinking that ACLs on

On Mon, 2019-06-17 at 20:14 +0530, 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 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 >

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

Hello Rowland, ldap search command throws error as below. I am unable to search ldap. ------- ldap_initialize( ldap://dc.exza.local:3268 ) ldap_start_tls: Can't contact LDAP server (-1) Enter LDAP Password: ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1) ---------- I am using BIND_DLZ dns back end. and server is listening on 3268 and 3269 -- Thanks & Regards, Anantha

> 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

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

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