similar to: Doman join issues

Hi Rowland, I get the same error messages even with the following smb.conf, generated by the migration process. [global] workgroup = LIN realm = LIN.COM netbios name = LINSERVER01 server role = active directory domain controller server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbindd, ntp_signd, kcc, dnsupdate idmap_ldb:use

Hai, 1) apparmor, disable it, and try again, so we can confirm if its an apparmor settings. 2) winbind is starting from systemd while as AD-DC you should disable that. - stop the member parts of samba and systemd. systemctl stop winbind smbd nmbd samba systemctl disable winbind smbd nmbd samba systemctl mask winbind smbd nmbd samba - enable the samba-ad-dc part in systemd.

On Mon, 6 May 2019 02:51:18 +0000 Praveen Ghimire via samba <samba at lists.samba.org> wrote: > From: Praveen Ghimire via samba <samba at lists.samba.org> > To: "samba at lists.samba.org" <samba at lists.samba.org> > Subject: [Samba] Doman join issues > Date: Mon, 6 May 2019 02:51:18 +0000 > Reply-To: Praveen Ghimire <PGhimire at sundata.com.au>

On Mon, 6 May 2019 09:47:44 +0000 Praveen Ghimire via samba <samba at lists.samba.org> wrote: > Hi Louis, > > Thank you for that. > > I don’t have a /var/lib/samba/bind-dns/dns/ , only > have /var/lib/samba/private/dns. > > Apparmor is now stopped and masked. I had masked the smbd and nmbd > post the migration, have masked the winbind now. > > Have

Hi , We ran the classicupgrade today and have come across an issue with sysvol. The users are getting access denied message when accessing sysvol/netlogn. Other shares are ok. The administrator can access the sysvol and netlogin root at dozer5-ad:/var/lib/samba# ls -al total 67 drwxr-xr-x 6 root root 11 May 10 17:33 . drwxr-xr-x 32 root root 32 May

Hi Louis, Thank you for that. I don’t have a /var/lib/samba/bind-dns/dns/ , only have /var/lib/samba/private/dns. Apparmor is now stopped and masked. I had masked the smbd and nmbd post the migration, have masked the winbind now. Have edited samba and bind as per your suggestion, changed the named.conf.options and krb5.conf Rebooted the server post the changes and tried to join a windows 7

On Mon, 6 May 2019 07:35:07 +0000 Praveen Ghimire <PGhimire at sundata.com.au> wrote: > Hi Rowland, > > I get the same error messages even with the following smb.conf, > generated by the migration process. > > [global] > workgroup = LIN > realm = LIN.COM > netbios name = LINSERVER01 > server role = active directory domain

Hi Rowland, I did that initially and that came with Failed to connect to ldap URL 'ldap://lin-pdc.lin - LDAP client internal error: NT_STATUS_BAD_NETWORK_NAME Hence I removed the whole ldap:// bit After your email I tried again but using ldap://localhost and it seems to have worked. Not sure what the issue is with the fqdn. I could run ldap queries when using fqdn. Regards, Praveen

Hai Praveen, > -----Oorspronkelijk bericht----- > Van: Praveen Ghimire [mailto:PGhimire at sundata.com.au] > Verzonden: donderdag 27 juni 2019 13:46 > Aan: samba at lists.samba.org > CC: 'L.P.H. van Belle' > Onderwerp: RE: [Samba] Reverse DNS > > Hi Guys, > > Thank you for your emails. Here is the info > > /etc/apparmor.d/local/usr.sbin.dhcp >

Hi, We are having some replication issues between the our PDC and BDC LDAP servers. Here are the details Servers: Name: LIN-PDC1.LIN Role: PDC SLAPD: openldap-2.4.28 Samba: 3.6.25 Name: LIN-PDC2.LIN Role: BDC SLAPD: 2.4.31 Samba: 4.3.11 LDAP Method: cn=config with smbldap tools Database: HDB Management: PHPLAMDIN Replication Method: refreshAndPersist Replication: After importing the LDIFs

Hi Guys, We're trying to add a BDC in Samb4 classic domain setup. The Samba 3 How -To and Samb3 by Example covers this but uses the old slapd.conf option, we are using the slapd.d config. I couldn't find a similar document for Samba4 Can you please advise that the following steps will work? LDAP in the existing PDC is working using the smbldap tools - Setup the LDAP in BDC

On Mon, 6 May 2019 11:12:17 +0000 Praveen Ghimire <PGhimire at sundata.com.au> wrote: > Hi Rowland, > > Sorry about the confusion. It is Ubuntu 18.04 with Samba 4.7.6 > > I have a script that installs the following > > apt-get install -y acl attr autoconf bind9utils bison build-essential > \ debhelper dnsutils docbook-xml docbook-xsl flex gdb libjansson-dev \ >

Hi, We did a classicupgrade of our Ubuntu Server (4.3.11, TDB), the server DC5 also host shares. Post the migration we are seeing some permission issues. When trying to give permission to a domain group/user to folder/file we get the following chown "LIN\\myadmin:LIN\\adgroup" adtest/ chown: invalid user: 'LIN\\myadmin:LIN\\adgroup' wbinfo --ping-dc : checking the NETLOGON

On 26/06/2019 11:32, Praveen Ghimire wrote: > Hi Rowland, > > I have tried putting the whole rev-domain name. The following is the dhcpd.conf zone definition > > subnet 192.168.14.0 netmask 255.255.255.0 { > authoritative; > ddns-update-style standard; > option netbios-name-servers 192.168.14.10; #14.10 is the AD box > option

On 26/06/2019 04:38, Praveen Ghimire via samba wrote: > Hi Louis, > > Thank you for that > > I have made the changes as per below , some items might have duplicated. I then reload apparmor restarted the samba-ad-dc and bind9 services and get the same issue. Every time the forward DNS update works but the reverse doesn't > > I found a really interesting samba post going

Hi , We migrated to AD account in a Ubuntu 16.04 (Samba 4.3.11)and came across issues with user shares. Some of the users were able to access the shares and some were not. The server in question has both AD and File and we followed the samba wiki to enable the Windows ACL To migrate , we ran the following samba-tool domain classicupgrade --dbdir=/var/lib/samba.PDC/dbdir --realm=lin.GROUP

Hi Rowland, The user's ID range would have been below 3600, the current max rid is 3506 The links have been setup following this link, then restarted the samba-ad-dc service https://wiki.samba.org/index.php/Libnss_winbind_Links I followed the following to configure the winbindd stuff, https://wiki.samba.org/index.php/Configuring_Winbindd_on_a_Samba_AD_DC template shell = /bin/bash

On Sun, 25 Mar 2018 08:01:57 +1300 Andrew Bartlett <abartlet at samba.org> wrote: > On Sat, 2018-03-24 at 12:50 +0000, Praveen Ghimire via samba wrote: > > Hi Rowland, > > > > I did that initially and that came with > > Failed to connect to ldap URL 'ldap://lin-pdc.lin - LDAP client > > internal error: NT_STATUS_BAD_NETWORK_NAME Hence I removed the

Harry, Thank you. Unfortunately we don't have the choice of upgrading LDAP due to distro not supporting the newer version. However we have managed to get it to work. A lot of fiddling around. I do have another question though ;). Now that we have LDAP replicating, how do I transfer the "samba classic " PDC role to our BDC. I have read that using the domain master=yes in smb.conf

Hi Rowland, Sorry about the confusion. It is Ubuntu 18.04 with Samba 4.7.6 I have a script that installs the following apt-get install -y acl attr autoconf bind9utils bison build-essential \ debhelper dnsutils docbook-xml docbook-xsl flex gdb libjansson-dev \ libacl1-dev libaio-dev libarchive-dev libattr1-dev libblkid-dev libbsd-dev \ libcap-dev libcups2-dev libgnutls28-dev libjson-perl \