search for: roleowners

Hi >I take it that Administrator exists (hasn't been renamed or removed) and you are using the correct password, Administrator exists and marcio too. Passwords is correct: samba-tool fsmo transfer --role=domaindns -Uadministrator * The 'domaindns' role does not have an FSMO roleowner samba-tool fsmo transfer --role=domaindns -'U administrator' * The 'domaindns'

Greetings - On our samba 4 (4.3.3) AD controller I just noticed something odd. When I run 'samba-tool fsmo show' I get an error: # samba-tool fsmo show ERROR(ldb): uncaught exception - No such Base DN: CN=Infrastructure,DC=DomainDnsZones,DC=biostat,DC=washington,DC=edu File "/usr/local/samba/lib64/python2.6/site-packages/samba/netcmd/__init__.py", line 175, in _run

Hi, This way don't works too. root at samba4-dc:~# samba-tool fsmo transfer --role=forestdns -Uadministrator Password for [EMPRESA\administrator]: ERROR: Failed to add role 'forestdns': LDAP error 53 LDAP_UNWILLING_TO_PERFORM - <000020AE: SvcErr: DSID-03152BF7, problem 5003 (WILL_NOT_PERFORM), data 0 > <> root at samba4-dc:~# samba-tool fsmo transfer --role=domaindns

...tly, what should be >> done to address it? >> >> thanks, >> -r >> > > OK, as for how did you get to here, how was the domain provisioned ?? Provisioning was a 'classicupgrade' of a samba 3 domain with LDAP backend. > You are actually missing two fsmo roleowners, your ldbsearch should > return these as well as the other 5: > > dn: CN=Infrastructure,DC=DomainDnsZones,DC=biostat,DC=washington,DC=edu > dn: CN=Infrastructure,DC=ForestDnsZones,DC=biostat,DC=washington,DC=edu > > Do the 'DNs' exist ? > > try this: > > ldbsea...

...N=RID Manager$,CN=System,DC=biostat,DC=washington,DC=edu > > What might explain this anomaly, and more importantly, what should be > done to address it? > > thanks, > -r > OK, as for how did you get to here, how was the domain provisioned ?? You are actually missing two fsmo roleowners, your ldbsearch should return these as well as the other 5: dn: CN=Infrastructure,DC=DomainDnsZones,DC=biostat,DC=washington,DC=edu dn: CN=Infrastructure,DC=ForestDnsZones,DC=biostat,DC=washington,DC=edu Do the 'DNs' exist ? try this: ldbsearch --cross-ncs -H /usr/local/samba/private/s...

Maybe the output of 'samba-tool fsmo transfer --help' should include the -U parameter... > (...) if you enter 'samba-tool fsmo transfer --help' it prints amongst > the output: > > --role=ROLE?????????? The FSMO role to seize or transfer. > ??????????????????????? ....................... > ??????????????????????? ..................... >

On 04/08/2019 18:17, Marcio Demetrio Bacci wrote: > Hi, > > > Maybe the output of 'samba-tool fsmo transfer --help' should include > the > -U parameter and its purpose in the current context... > > I've done this > > samba-tool fsmo transfer --role=domaindns -Uadministrator > * The 'domaindns' role does not have an FSMO roleowner > That is

...t; OK, as for how did you get to here, how was the domain provisioned ?? > > Provisioning was a 'classicupgrade' of a samba 3 domain with LDAP > backend. I don't suppose you can remember the actual command you ran to upgrade ? > >> You are actually missing two fsmo roleowners, your ldbsearch should >> return these as well as the other 5: >> >> dn: CN=Infrastructure,DC=DomainDnsZones,DC=biostat,DC=washington,DC=edu >> dn: CN=Infrastructure,DC=ForestDnsZones,DC=biostat,DC=washington,DC=edu >> >> Do the 'DNs' exist ? >> &gt...

...dir=/var/tmp/dbdir/ --use-xattrs=yes --realm=biostat.washington.edu --dns-backend=BIND9_FLATFILE --option="interfaces=lo eth0" --option="bind interfaces only=yes" /var/tmp/dbdir/smb.conf (output is appended below) > >> >>> You are actually missing two fsmo roleowners, your ldbsearch should >>> return these as well as the other 5: >>> >>> dn: CN=Infrastructure,DC=DomainDnsZones,DC=biostat,DC=washington,DC=edu >>> dn: CN=Infrastructure,DC=ForestDnsZones,DC=biostat,DC=washington,DC=edu >>> >>> Do the 'DNs...

...info in AD Please tell me that this domain is only a test domain and you can re-run the upgrade with '--dns-backend=BIND9_DLZ' or '--dns-backend=SAMBA_INTERNAL' Rowland > (output is appended below) > >> >>> >>>> You are actually missing two fsmo roleowners, your ldbsearch should >>>> return these as well as the other 5: >>>> >>>> dn: >>>> CN=Infrastructure,DC=DomainDnsZones,DC=biostat,DC=washington,DC=edu >>>> dn: >>>> CN=Infrastructure,DC=ForestDnsZones,DC=biostat,DC=washingto...

>>> Are you using Bind9 >> No using internal bind > > I take it that means the internal dns server and not a separate dns > server. Yes you are correct sorry . Samba's internal DNS > > Hmm, so it isn't in the 'Default-First-Site-Name' site, I wonder if > this is the problem ? Let me go and have a read of the code and get > back to you. >

...n't ideal but we haven't encountered any problems until now. Couldn't we simply add the missing DNs (along with corresponding DNS records, if necessary)? >> (output is appended below) >> >>> >>>> >>>>> You are actually missing two fsmo roleowners, your ldbsearch should >>>>> return these as well as the other 5: >>>>> >>>>> dn: >>>>> CN=Infrastructure,DC=DomainDnsZones,DC=biostat,DC=washington,DC=edu >>>>> dn: >>>>> CN=Infrastructure,DC=ForestDnsZones,D...

On 03/01/16 06:00, JS wrote: > <=?windows-1252?Q?L.P.H._van_Belle?=> writes: > >> Ok, >> >> > Hi Louis, > > Thank you again for taking the time to help me out, I do appreciate it, and > I hope you had a safe and Happy New Year's eve. I'm going to work my way > through the questions/comments in your response from top to bottom: > >>

<=?windows-1252?Q?L.P.H._van_Belle?=> writes: > > Ok, > > Hi Louis, Thank you again for taking the time to help me out, I do appreciate it, and I hope you had a safe and Happy New Year's eve. I'm going to work my way through the questions/comments in your response from top to bottom: > First things is see. > > NTP > drwxr-x--- 2 root root

Fail! :-( root at gteste2:~# samba-tool fsmo transfer --role=all -UAdministrador FSMO transfer of 'rid' role successful FSMO transfer of 'pdc' role successful FSMO transfer of 'naming' role successful FSMO transfer of 'infrastructure' role successful FSMO transfer of 'schema' role successful ERROR(<type 'exceptions.UnboundLocalError'>):