similar to: Samba NT4 to AD- LDAP

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

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 whole ldap:// bit > > After your email I tried again but using ldap://localhost and it seems to have worked. Not

Hi Rowland, I have another samba box on the same classic domain. That box is just a member server and used for file sharing. Once we migrate the PDC to AD, what do we need to do the member server? Do we need to change smb.conf and add the realm name? Regards, Praveen Ghimire -----Original Message----- From: samba [mailto:samba-bounces at lists.samba.org] On Behalf Of Praveen Ghimire via

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

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

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

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

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 running test migration on the following environment in preparation for the prod migration. Any suggestions will be grealty appreciated. OS: Ubuntu18.04 Hypervisor: Proxmox Container (LXC) Samba Version 4.6.7 DNS: BIND9_DLZ AD and File server in the same server. Have gone through the Samba documentation regarding this We get the following when adding a machine (Windows 7) to the

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

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

On Sat, 24 Mar 2018 11:59:38 +0000 Praveen Ghimire via samba <samba at lists.samba.org> wrote: > Hi All, > > Following the link, tried to migrate NT4 to AD using LDAP but came > across some issues. > https://wiki.samba.org/index.php/Migrating_a_Samba_NT4_Domain_to_Samba_AD_(Classic_Upgrade) > > I have done this step multiple times using TDB as the backend and it >

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

2 things. Hai, Change [homes] to [users] and create the folder /home/LIN AD-DC's dont like [homes] Share /home/LIN as [users] Now, in the AD DC smb.conf, the templates settings are used by default. template homedir = /home/%D/%U Which results in your case to : /home/LIN/testhome2 That should do it, but rethink this part of you setup. You might need to change the pam part a bit, but

Hi, We have some issue with the reverse DNS in Samba AD. We're running Bind9_DLZ on Ubuntu 18.04. The DHCP server(Ubuntu 16.04) is different to the AD server and not in the same AD domain. The DHCP scope points to the Samba AD server as the DNS server When a machine with DHCP assigned address tries to update the DNS record, it is able to update the forward zone but not the reverse zone. The

Hai, You posted the correct things here, for a quick fix i I'm buzzy with something else atm but i saw that /dev/urandom part. Add in the bind9 (named) apparmor profile # Samba DLZ /{usr/,}lib/@{multiarch}/samba/bind9/*.so rm, /{usr/,}lib/@{multiarch}/samba/gensec/*.so rm, /{usr/,}lib/@{multiarch}/samba/ldb/*.so rm, /{usr/,}lib/@{multiarch}/ldb/modules/ldb/*.so rm,