How can i reset all settings to default?

Go to Bottom
Forums > General Discussion > How can i reset all settings to default? > Page 2
Pages: < < Previous - 1 , 2 , 3 - Next > >
Post #16
4auHer

Group: Members
Posts: 15 Joined: 26 Oct 2022 Location: IP: 195.239.---
Posted:
Have a problem during migration from Resara:

Joining an existing domain.
Checking domain passwords.
Passwords matches.
Using 192.168.128.1 as DNS server..
Update DNS Service.
Start DNS Service..
Run command to create DNS record for new DC:

/i  created A record for sdc already/

Testing for DNS records in the domain.
sdc.local.net has address 192.168.128.3
Done.
Also use 192.168.128.1 for DNS.
Enable samba on boot...Done
Start Samba service...Done
Failed to start.
Set permissions on '/etc/krb5.conf'.
Copy '/usr/local/samba/private/krb5.conf'  to '/etc/krb5.conf'.
Enable DNS on boot...Done
Errors were detected! You can click here to reset and try again, or ignore this and continue with the link below.

And... no link below.
Post #17
razdc

Group: Admins
Posts: 197 Joined: 23 Apr 2021 Location: Reynolds, ND IP: 24.111.---
Posted:
usually it displays a link that just does a reset. If that link is not appearing the script was truncated for some reason. You can just reload the page and see if it lets you log into the console. From here you can login and run a reset from the system menu. In the mean time, I will setup a Resara server and test the new version of samba against the migration instructions and see if I can duplicate the problem. Something might have changed since the previous samba build prior to the 22H2 supported version. I will report back once I have reached the point of provisioning.
Bryan King
Post #18
razdc

Group: Admins
Posts: 197 Joined: 23 Apr 2021 Location: Reynolds, ND IP: 24.111.---
Posted:
I see you posted "Enable DNS on boot...Done" so I am curious if before provision, did you selected 'samba_internal' for DNS type? I have a Resara migration document here: https://razdc.com/cgi-bin/account/secure.pl?f=HOWTO&t=3 you can review.
Bryan King
Post #19
4auHer

Group: Members
Posts: 15 Joined: 26 Oct 2022 Location: IP: 195.239.---
Posted:
I did everything exactly according to these instructions.
Yes, i selected 'samba_internal' for DNS type.
Thanx for answer.
Post #20
razdc

Group: Admins
Posts: 197 Joined: 23 Apr 2021 Location: Reynolds, ND IP: 192.168.---
Posted:
I just performed a clean isntall of resara and razdc and was able to join as secondary for migration without issues. Did you setup Razdc to use Resara as the DNS server?

 Joining an existing domain.
Checking domain passwords.
Passwords matches.
Using 192.168.19.194 as DNS server..
Update DNS Service.
Start DNS Service..
Run command to create DNS record for new DC:
echo '**************' |sudo  /usr/local/samba/bin/samba-tool dns add 192.168.19.194 resara.local dc2 A 192.168.19.96 -U administrator@resara.local
Provision secondary domain controller for: resara.local
NO DNS zone information found in source domain, not replicating DNS Adding CN=DC2,OU=Domain Controllers,DC=resara,DC=local Adding CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=resara,DC=local Adding CN=NTDS Settings,CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=resara,DC=local Adding SPNs to CN=DC2,OU=Domain Controllers,DC=resara,DC=local Setting account password for DC2$ Enabling account Calling bare provision Provision OK for domain DN DC=resara,DC=local Starting replication Replicating critical objects from the base DN of the domain Done with always replicated NC (base, config, schema) Committing SAM database
Testing for DNS records in the domain.

    dc2.RESARA.LOCAL  has address 192.168.19.96

Done.
Also use 192.168.19.194 for DNS.
Enable samba on boot...Done
Start Samba service...Done
Starting samba was successful.
Set permissions on '/etc/krb5.conf'.
Copy '/usr/local/samba/private/krb5.conf'  to '/etc/krb5.conf'.
Enable DNS on boot...Done
Bryan King
Post #21
razdc

Group: Admins
Posts: 197 Joined: 23 Apr 2021 Location: Reynolds, ND IP: 192.168.---
Posted:
Once RazDC was joined, I was able to see all user data sync. I ran FSMO migration tool to move all roles. Then I ran "dnsmig" from the raz command list to move samba_internal DNS to bind9_dlz. I updated the RazDC DNS to use itself rather than Resara and ran all diagnostics. RazDC held all FSMO roles, DNS server, was resolving itself and domain. I was then able to decommission the resara server without errors.
Bryan King
Post #22
4auHer

Group: Members
Posts: 15 Joined: 26 Oct 2022 Location: IP: 195.239.---
Posted:
Could the problem be that I added an A record to Resara's DNS through the interface but not command line?
Post #23
razdc

Group: Admins
Posts: 197 Joined: 23 Apr 2021 Location: Reynolds, ND IP: 24.111.---
Posted:
No, adding the DNS record to Resara using the interface is one of the steps. I was asking if you configured RazDC DNS1 to use the Resara server IP. I would review this how-to guide carefully.
https://razdc.com/cgi-bin/account/secure.pl?f=HOWTO&t=3
Bryan King
Post #24
4auHer

Group: Members
Posts: 15 Joined: 26 Oct 2022 Location: IP: 195.239.---
Posted:
Join failed - cleaning up :((( Why can it be?

Joining an existing domain.
Checking domain passwords.
Passwords matches.
Using 192.168.130.1 as DNS server..
Update DNS Service.
Start DNS Service..
Run command to create DNS record for new DC:
echo '---------------' |sudo  /usr/local/samba/bin/samba-tool dns add 192.168.130.1 local.net razdc A 192.168.130.109 -U administrator@local.net
Provision secondary domain controller for: local.net
NO DNS zone information found in source domain, not replicating DNS Adding CN=RAZDC,OU=Domain Controllers,DC=local,DC=net Adding CN=RAZDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=local,DC=net Adding CN=NTDS Settings,CN=RAZDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=local,DC=net Adding SPNs to CN=RAZDC,OU=Domain Controllers,DC=local,DC=net Setting account password for RAZDC$ Enabling account Calling bare provision Provision OK for domain DN DC=local,DC=net Starting replication Replicating critical objects from the base DN of the domain Join failed - cleaning up Deleted CN=RAZDC,OU=Domain Controllers,DC=local,DC=net Deleted CN=NTDS Settings,CN=RAZDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=local,DC=net Deleted CN=RAZDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=local,DC=net
Testing for DNS records in the domain.
razdc.local.net has address 192.168.130.109
Done.
Also use 192.168.130.1 for DNS.
Enable samba on boot...Done
Start Samba service...Done
Starting samba was successful.
Set permissions on '/etc/krb5.conf'.
Copy '/usr/local/samba/private/krb5.conf'  to '/etc/krb5.conf'.
Enable DNS on boot...Done
Post #25
razdc

Group: Admins
Posts: 197 Joined: 23 Apr 2021 Location: Reynolds, ND IP: 192.168.---
Posted:
Resara IP is 192.168.130.1? Or is this your gateway?
Bryan King
Post #26
4auHer

Group: Members
Posts: 15 Joined: 26 Oct 2022 Location: IP: 195.239.---
Posted:
Yes, it's Resara. Gate - 130.100.
Post #27
razdc

Group: Admins
Posts: 197 Joined: 23 Apr 2021 Location: Reynolds, ND IP: 24.111.---
Posted:
I have tested the Resara to RazDC migration many times and I am unable to duplicate the error if I follow the guide. I can only conclude this is an error in the setup or possibly an older version of Resara with broken DNS or corruption in Resara DNS. You can definitely try to perform the migration manually rather than relying on the automated setup but this depends on your technical ability since both of these are just Samba4 and Bind9 all of the commands are openly available.

Configure  the initial RazDC network as per the instructions for Resara migration.

Then switch to command line and perform setup manually..

Create Record in Resara:
sudo /usr/local/samba/bin/samba-tool dns add 192.168.130.1 local.net razdc A 192.168.130.109 -U administrator@local.net

Join Domain:
sudo /usr/local/samba/bin/samba-tool domain join local.net DC -U "LOCAL\administrator" --dns-backend=SAMBA_INTERNAL

At this point you should be able to login to RazDC and complete the FSMO migration/takeover.

Once  this is complete, use raz cli to perform the dns upgrade to BIND9_DLZ.

Resara can be decommissioned.
Bryan King
Post #28
4auHer

Group: Members
Posts: 15 Joined: 26 Oct 2022 Location: IP: 188.244.---
Posted:
End of log during Join Domain:

Analyze and apply schema objects
Partition[CN=Configuration,DC=local,DC=net] objects[402/1695] linked_values[0/0]
Partition[CN=Configuration,DC=local,DC=net] objects[804/1695] linked_values[0/0]
Partition[CN=Configuration,DC=local,DC=net] objects[1206/169S] linked_values[0/0]
Partition[CN=Configuration,DC=local,DC=net] objects[1608/169S] linked_values[0/0]
Partition[CN=Configuration,DC=local,DC=net] objects[1695/1695] linked_values[297/0]
Replicating critical objects from the base DN of the domain
Partition [DC=local,DC=net]  objects[98/98] linked_values[359/0]
Failed to commit objects: WERR_DS_DRA_MISSING_PARENT
Join failed - cleaning up
Deleted CN=RAZDC,OU=Domain Controllers,DC=local,DC=net
Deleted CN=NTDS Settings,CN=RAZDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=local,DC=net
Deleted CN=RAZDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=local,DC=net
ERROR(runtime): uncaught exception - (8160, "Failed to process 'chunk' of DRS replicated objects: WERR_DS_DRA_MISSING_PARENT")
  File "/usr/local/samba/lib64/python3.6/site-packages/samba/netcmd/__init__.py",  line 186, in _run
    return self.run(*args, **kwargs)
  File "/usr/local/samba/lib64/python3.6/site-packages/samba/netcmd/domain.py",  line 672, in run
    backend_store_size=backend_store_size)
  File "/usr/local/samba/lib64/python3.6/site-packages/samba/join.py",  line 1558, in join_DC
    ctx.do_join()
  File "/usr/local/samba/lib64/python3.6/site-packages/samba/join.py",  line 1448, in do_join
    ctx.join_replicate()
  File "/usr/local/samba/lib64/python3.6/site-packages/samba/join.py",  line 992, in join_replicate
    replica_flags=ctx.domain_replica_flags)
  File "/usr/local/samba/lib64/python3.6/site-packages/samba/drs_utils.py",  line 333, in replicate
    raise e
  File  "/usr/local/samba/lib64/python3.6/site-packages/samba/drs_utils.py", line 320, in replicate
    self.process_chunk(level, ctr, schema, req_level, req,first_chunk)
  File "/usr/local/samba/lib64/python3.6/site-packages/samba/drs_utils.py",  line 214, in process_chunk
    schema=schema, req_level=req_level, req=req)

What can i try to do anymore?

"possibly an older version of Resara with broken DNS or corruption in Resara DNS" (c)
version 1.1.2 from sourceforge.
Corruption in DNS - look like a true. How can i fix it?
Post #29
razdc

Group: Admins
Posts: 197 Joined: 23 Apr 2021 Location: Reynolds, ND IP: 192.168.---
Posted:
If you have a secondary DC you attempt to join that one. Otherwise if you have a previous backup of resara config you could try a restore first to a clean new install. Otherwise your best bet might to just rebuild from scratch depending on your number of clients. On second thought, simple reboot might do the trick.. DNS isn't responding so it could just be the sockets are all full or zombied.
Bryan King
Post #30
4auHer

Group: Members
Posts: 15 Joined: 26 Oct 2022 Location: IP: 195.239.---
Posted:
I succeeded join into Resara domain Windows Server 2003. WS2003 appeared in Domain Controllers on Resara. I see all domain records: computers, users, groups... even can manage it and all operations replicate to Resara. But... DNS i see also but can't manage FLZ records, just PTR.
Can i transfer FSMO roles to WS2003 and then shutdown Resara?
Also i need transfer Forward Lookup Zones in DNS to WS2003 for they can be managed. Is it right? What are You think about this? Can it work?
May be after this i can migrate from WS2003 to RazDC?
Pages: < < Previous - 1 , 2 , 3 - Next > >
Back to Top