similar to: ADUC: RPC Server is unavailable

Hi Rowland, thank you for your prompt reply, I sent you the testparam output hence lots of defaults (i presumed would be better), here is crude smb.conf: root at araucaria:~# cat /etc/samba/smb.conf [global]     netbios name = ARAUCARIA     realm = AD.TLD     server role = active directory domain controller     workgroup = A1     server services = -dns     ldap server require strong auth

Hi Rowland, Those tests were made on DC (araucaria), not a domain member. root at araucaria:~# testparm /etc/samba/smb.conf Load smb config files from /etc/samba/smb.conf rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) Processing section "[netlogon]" Processing section "[sysvol]" Loaded services file OK. Server role: ROLE_ACTIVE_DIRECTORY_DC Press

Hi, I have a samba 4.7 AD DC running on a Ubuntu 18.04 server with distro packages. I update a user with a new group and this new membership is not reflected on that user. On example below, I can successfully add the user "test.account" to group "test", but not my user "marcio.merlone": root at araucaria:~# id test.account uid=30214(A1\test.account)

Hi, Trying to add an OU via ldbadd but I get the following error: root at araucaria:~# ldbadd --url=/var/lib/samba/private/sam.ldb /root/ou.ldif ERR: No such attribute : "objectclass top  is not a valid objectClass in schema" on DN OU=A1,DC=ad,DC=a1,DC=ind,DC=br at block before line 4 Add failed after processing 0 records root at araucaria:~# root at araucaria:~# cat /root/ou.ldif

On Tue, 27 Nov 2018 16:39:41 -0200 Marcio Vogel Merlone dos Santos via samba <samba at lists.samba.org> wrote: > Hi, > > I have a samba 4.7 AD DC running on a Ubuntu 18.04 server with distro > packages. I update a user with a new group and this new membership is > not reflected on that user. On example below, I can successfully add > the user "test.account" to

On Wed, 28 Nov 2018 10:12:39 -0200 Marcio Vogel Merlone dos Santos via samba <samba at lists.samba.org> wrote: > Hi Rowland, thank you for your prompt reply, > > I sent you the testparam output hence lots of defaults (i presumed > would be better), here is crude smb.conf: > > root at araucaria:~# cat /etc/samba/smb.conf > [global] >     netbios name = ARAUCARIA

Hi all, I am deploying a new AD DC for our network using Ubuntu 18.04 and BIND_DLZ. Al lis fine but the RFC2307 attributes on DC. What's the recommended/correct way to use RFC2307 attributes on DC? At the wiki (1) it says: > For example, setting up an ID mapping back end, such as|ad|(RFC2307) > or|rid|, in the|smb.conf|file is not supported an can cause > the|samba|service to

Hi, I have 3 Debian Buster DC running Samba 4.12.3, each one on a site. Now I have to add a Windows 2008R2 server as DC, but failing miserably to stabilize it for the past 2 weeks. First, kcc did not created NTDS connections automatically, had to create them by hand. Some days have passed and now when I try to replicate from samba to windows, *both on same site*, I get this: root at

Hi, Since we cannot join a W10 machine to NT3.x domain anymore, it is time to move on. We have a decade-old domain 'A1CWB' and will profit from the situation fixing the old S-1-5-21-1234567890-1234567890-1234567890 SID and implementing a new domain name: Old domain: A1CWB, SID S-1-5-21-1234567890-1234567890-1234567890 New domain: AD.A1.IND.BR, decent SID from net getdomainsid, two

Hello, excuse me for my English. I have several samba installations in different places and in all of them I have the same problem. Therefore, something I am doing wrong or I understand wrong. When I want to manage the share from Windows, it returns the error: "Rpc server is unavailable" and on the other hand in the edition of permissions (also from Windows) in advanced is the legend:

On Thu, 29 Nov 2018 20:19:52 -0300 Epsilon Minus via samba <samba at lists.samba.org> wrote: > Hello, excuse me for my English. > > I have several samba installations in different places and in all of > them I have the same problem. Therefore, something I am doing wrong or > I understand wrong. > > When I want to manage the share from Windows, it returns the error:

On Wed, 28 Nov 2018 08:48:07 -0200 Marcio Vogel Merlone dos Santos via samba <samba at lists.samba.org> wrote: > Hi Rowland, > > Those tests were made on DC (araucaria), not a domain member. > > root at araucaria:~# testparm /etc/samba/smb.conf > Load smb config files from /etc/samba/smb.conf > rlimit_max: increasing rlimit_max (1024) to minimum Windows limit >

Dear, I do not think the problem comes around, but I made the modifications you suggest, but the problem persists. Maybe I am misunderstanding the point that you raise. root at samba01:~# cat /etc/samba/smb.conf [global] security = ADS workgroup = DOMAINNAME realm = FULL_DOMAINNAME log file = /var/log/samba/%m.log log level = 1 idmap config * : backend = tdb idmap config * : range = 3000-7999

Hello. We're running Samba 4.3.9 AD on two Ubuntu 16.04 LTS machines. I'm managing AD users and DNS from Windows 10 joined to the domain, by using ADUC. Last week I noticed the following error when starting ADUC as Administrator of the AD domain: ---- Naming information cannot be located because: The RPC server is unavailable. Contact your system administrator to verify that your domain

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

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 >

So, we have Samba file sharing working on CentOS 7.6 with sssd: [root at cns-srv-lnode2 samba]# cat /etc/redhat-release CentOS Linux release 7.6.1810 (Core) [root at cns-srv-lnode2 samba]# smbd --version Version 4.8.3 Some smb.conf configuration details: - security = user - an idmap entry is unnecessary - disable netbios = yes works fine - pretty sure nmbd is unnecessary

On Wed, 8 Aug 2018 10:18:51 -0300 Marcio Vogel Merlone dos Santos via samba <samba at lists.samba.org> wrote: > Hi all, > > I am deploying a new AD DC for our network using Ubuntu 18.04 and > BIND_DLZ. Al lis fine but the RFC2307 attributes on DC. What's the > recommended/correct way to use RFC2307 attributes on DC? At the wiki > (1) it says: > > > For

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