search for: pdclan

...1-1411277624-4092985889-3405756581-2062 does not belong to our domain for every user ID. After I start the upgraded domain: # net getdomainsid SID for domain AD-LAN is: S-1-5-21-2473926874-590573496-2946143095 and on original Samba 3 domain controller: # net getdomainsid SID for local machine PDCLAN is: S-1-5-21-1411277624-402985889-3405756581 SID for domain LAN is: S-1-5-21-1411277624-4092985889-3405756581 I.e., the domains SID are different (which is expected). How do I make the groups/users be imported? The smb.conf used is below: --------------------------------- smb.conf below [global...

...with the following IP addresses: 10.1.0.1 10.1.0.5 - One or more of the following zones do not include delegation to its child zone: LAN . (the root zone) ============= details below /etc/samba/smb.conf: ============= smb.conf below [global] unix charset = UTF8 workgroup = LAN netbios name = PDCLAN server max protocol = NT1 server string = PDCLAN - LAN Samba PDC passdb backend =ldapsam:"ldap://127.0.0.1 ldap://10.1.0.10" username map = /etc/samba/smbusers interfaces = eth0 lo bind interfaces only = yes enable privileges = yes log level = 1 syslog = 0 log file = /var/log/samba/%m max...

...;> (-1073741722,The specified group does not exist.) >> >> for every group from existing LDAP backend of Samba 3, and >> >> sid S-1-5-21-1411277624-4092985889-3405756581-2062 does not belong to >> our domain >> > > Okay, I take it your PDC was called pdclan and the domain was called > 'LAN', I have no idea what the dns domain was. > > You have now created a new AD DC using the dns domain 'ad-lan.com' and > the new AD DC is called 'dc' > > So from my reading there are three Samba workgroup names in play: >...

...able to enumerate group members, > (-1073741722,The specified group does not exist.) > > for every group from existing LDAP backend of Samba 3, and > > sid S-1-5-21-1411277624-4092985889-3405756581-2062 does not belong to > our domain > Okay, I take it your PDC was called pdclan and the domain was called 'LAN', I have no idea what the dns domain was. You have now created a new AD DC using the dns domain 'ad-lan.com' and the new AD DC is called 'dc' So from my reading there are three Samba workgroup names in play: PDCLAN LAN AD-LAN I think this,...

...oes not exist.) > >> > >> for every group from existing LDAP backend of Samba 3, and > >> > >> sid S-1-5-21-1411277624-4092985889-3405756581-2062 does not belong > >> to our domain > >> > > > > Okay, I take it your PDC was called pdclan and the domain was called > > 'LAN', I have no idea what the dns domain was. > > > > You have now created a new AD DC using the dns domain 'ad-lan.com' > > and the new AD DC is called 'dc' > > > > So from my reading there are three Samba...

...;> >> >> for every group from existing LDAP backend of Samba 3, and >> >> >> >> sid S-1-5-21-1411277624-4092985889-3405756581-2062 does not belong >> >> to our domain >> >> >> > >> > Okay, I take it your PDC was called pdclan and the domain was called >> > 'LAN', I have no idea what the dns domain was. >> > >> > You have now created a new AD DC using the dns domain 'ad-lan.com' >> > and the new AD DC is called 'dc' >> > >> > So from my reading...

Rowland Penny via samba wrote 2018-09-06 14:37: > On Thu, 06 Sep 2018 12:22:11 +0700 > Konstantin Boyandin via samba <samba at lists.samba.org> wrote: > >> Rowland Penny via samba wrote 2018-09-05 15:56: >> > On Wed, 05 Sep 2018 15:26:30 +0700 >> > Konstantin Boyandin via samba <samba at lists.samba.org> wrote: >> >> >> >>