similar to: Internal DNS migrate to Bind9_DLZ

On Thu, 01 Nov 2018 15:25:42 +0100 Jiří Černý via samba <samba at lists.samba.org> wrote: > Hello, > sorry, but I cannot find start of this discussion thread, so my > question may be stupid. Is your domain classicupgraded from Samba 3 > or provisioned from scratch? > > I have similar problem with our domain which is upgraded. If I > provision the new domain everything

>When you provision a new domain, it is set 3000000, but, seemingly, when you run the classicupgrade it gets sets to a lower number (never actually run a classicupgrade) based on what is in your old domain. > Not sure what to suggest here, do you feel up to sending me (offlist) a copy of your idmap.ldb ? > >Rowland Thank you again, Rowland, for your time. I think that different ID

@Rowland, The application can export in multiple file formats, ldif as well. Would you like a sample of the entire domain or only the schema or any specific? Okay, now I'm with you, I am aware of how to update samba. We have been updating Samba the normal way using the repository. We have been doing updates as should from version 4 moving up slowly to version 4.9.4, not all in a go but

Yes I have added "server services = -dns" to my smb.conf file and also removed "dns forwarder =" I've done the same setup but on Samba 4.7.7, RHEL6, named 9.8 and this works perfect. On Mon, Jul 30, 2018 at 11:18 AM Rowland Penny via samba < samba at lists.samba.org> wrote: > On Mon, 30 Jul 2018 10:57:11 +0200 > Eben Victor <eben.victor at gmail.com>

Hello Rowland, Please see below installed samba packages. # rpm -qa | grep samba sernet-samba-client-4.8.3-11.el7.x86_64 sernet-samba-common-4.8.3-11.el7.x86_64 sernet-samba-libsmbclient0-4.8.3-11.el7.x86_64 sernet-samba-4.8.3-11.el7.x86_64 sernet-samba-ad-4.8.3-11.el7.x86_64 sernet-samba-libs-4.8.3-11.el7.x86_64 sernet-samba-winbind-4.8.3-11.el7.x86_64 ldb is installed with the samba packages.

>On Wed, 06 Sep 2017 11:24:17 +0200>Jiří Černý via samba <samba at lists.samba.org ( https://lists.samba.org/mailman/listinfo/samba) > wrote:>>> I feel this all has something to do with the classicupgrade, the>> command works for me, does 'wbinfo --sid-to-gid="S-1-5-32-544"'>> work ?>> Yes. Take a look:wbinfo

Hello Rowland, selinux has been disabled, I also ran th follow # systemctl stop sernet-samba-ad # samba_upgradedns --dns-backend=BIND9_DLZ # named -d3 -f -g -u named Which then still fails, see below smb.conf [global] workgroup = DOMAIN realm = DOMAIN.CORP netbios name = PDC server role = active directory domain controller idmap_ldb:use rfc2307 = yes

Hai, > > > > have rejoined all my DC's with new names, see below. > >;; ANSWER SECTION: > ><domain>.corp. 3600 IN NS psad101zatcrh.<domain>.corp. -> New > >rebuild, new hostname, RHEL6 to RHEL7 upgrade .... > > > > Led me to believe this is your problem. However, you say it works on > > one DC, but not with multiple

Hi Rowland, I didn't build samba, I'm running the sernet packages, # rpm -qa | grep sernet sernet-samba-libsmbclient0-4.8.6-16.el7.x86_64 sernet-samba-ad-4.8.6-16.el7.x86_64 sernet-samba-libs-4.8.6-16.el7.x86_64 sernet-samba-client-4.8.6-16.el7.x86_64 sernet-samba-winbind-4.8.6-16.el7.x86_64 sernet-samba-common-4.8.6-16.el7.x86_64 sernet-samba-4.8.6-16.el7.x86_64 I don't mind having

> I feel I can tell you this without breaking any confidences, the OP sent me their idmap.ldb and the problem boiled down to these three DNs>> CN=S-1-5-32-545> CN=S-1-5-32-544> CN=S-1-5-32-546> > The classicupgrade seems to set these to 'ID_TYPE_GID' instead of 'ID_TYPE_BOTH'.>> RowlandI can confirm this. After changing 'ID_TYPE_GID' to

Hello, I hope that someone can perhaps assist me or just guide me in the right direction. I've been following all the steps for setting up and migrating my Samba Internal DNS to Bind9_DLZ. https://wiki.samba.org/index.php/Setting_up_a_BIND_DNS_Server https://wiki.samba.org/index.php/BIND9_DLZ_DNS_Back_End But this doesn't seem to work for me, I can get bind started up 100% when I remove

Hello Rowland, See below as requested. /etc/named.conf # Global Configuration Options include "/var/lib/samba/bind-dns/named.conf"; options { dump-file "/var/named/data/cache_dump.db"; statistics-file "/var/named/data/named_stats.txt"; memstatistics-file "/var/named/data/named_mem_stats.txt"; auth-nxdomain yes; directory

> I feel this all has something to do with the classicupgrade, the command works for me, does 'wbinfo --sid-to-gid="S-1-5-32-544"' work ?Yes. Take a look:wbinfo --sid-to-gid="S-1-5-32-544" 15538wbinfo --gid-info=15538 BUILTIN\administrators:x:15538: > I haven't received it yet, but will examine and comment on it when I do.I sent it to <rpenny at

It is part of the Sernet packages and is currently on 1.3.4 /usr/lib64/samba/libldb.so.1.3.4 We started using sernet-samba-ad from v4 using the internal dns and updated as versions were released. We have now recently updated from 4.8.2 to 4.8.3 and still using internal dns. Our DNS is working as it should, it's only been since recently that we have to migrate to bind9. On Mon, Jul 30, 2018

Well, we are getting somewere...;) >It is probably 'greyed' out because no Windows tools use it or will add it. You will probably need to use Unix tools (ldb or ldap) to remove>them, but you can if you so wish ignore them. What you should never do is to rely on them being there, because they may or may not be there.Ok, I'll let it be there> You need to remove the gidNumber

To Rowland: > This was perfectly common, nobody thought this would ever be a problem,mainly because you had to have a user or group in /etc/passwd> or /etc/group mapped to a Samba. Now with AD, you do not need a user or group in /etc/passwd or /etc/group, so any user or group that uses the RID as a Unix ID is> probably too low and is denying the use of any local Unix users Yes, but where

Thank you very much for clarifying the ID mapping "magic";) > You do not need 'posixgroup', it is an auxiliary objectclass of group, you can add any of the rfc2307 attributes without it. Well, is there any option to remove it? Because "posixgroup" is on every group that was migrated from Samba 3. And I cannot edit this attribute in ADUC (delete button is grayed).

Hello Rowland, I have already checked and the DN's are in AD, see attached. SOA: <domain>.corp. 3600 IN SOA psad102zadprh.<domain>.corp. . 9766 3600 600 86400 3600 See below NS, but the 1st NS (zatprdc001) doesn't exsit, and I cannot find it anywhere. NS: <domain>.corp. 3600 IN NS zatprdc001.<domain>.corp. <domain>.corp. 3600

> You may get away with using the 'rid' backend, but this will have to be> your choice, but whatever you choose, I am sure we can help you get to> a working domain.> > RowlandSo I have an example. We have file and print server based on CentOS 7 with Samba 4.4.4. As wiki said (https://wiki.samba.org/index.php/Setting_up_Automatic_Printer_Driver_Downloads_for_Windows_Clients)

Hello everyone. In our company we use Samba 4 for about 3 years (classic upgraded from Samba 3.5 + LDAP to Sernet Samba 4.2). We used CentOS 6 for domain controllers and with Bind bundled in this distro was impossible to use dynamic DNS updates. And because I don't like using compiled SW on production servers, we used Samba internal DNS, which worked well (dynamic updates). With one non