Displaying 5 results from an estimated 5 matches for "sc_reset".
2020 Jun 02
1
several dns issues after switching fsmo roles to samba-dc
...this way:
1. I could reproduce the issue by restarting NETLOGON service on the Windows DC.
Also the following commands failed with "Connection Status = 1311 0x51f
ERROR_NO_LOGON_SERVERS":
nltest.exe /dsregdn
nltest /query
2. After some googling, I've found the fixing command:
nltest /sc_reset:domain.com
After that, all vm-dc1 records were registered in the AD w/o issues
using "nltest.exe /dsregdn" command.
Unfortunately, it's failing again after restarting NETLOGON service.
--
Best regards,
Alex
2020 Feb 13
3
Failover DC did not work when Main DC failed
...don't have any CNAMES or domain overrides pointing to a single
DC? Perhaps Bind is pointing to another internal DNS server, and then to a
public DNS?
----
Here's a way to test failover from a Windows client:
You can switch logon servers with "nltest /server:<clientcomputer>
/sc_reset:<domain\dc>"
https://www.technipages.com/windows-how-to-switch-domain-controller
So try this -- (I just did this on one of my DC's):
* Switch a Windows Client to DC4
* Verify with "nltest /dsgetdc:<domain>" and "nltest /sc_query:<domain>"
C:\WINDOWS\...
2020 Feb 16
0
Failover DC did not work when Main DC failed
...a single DC"?
I have DHCP handing out both DNS servers as 192.168.0.218 and 192.168.0.219 and they both work as nameservers perfectly.
> Here's a way to test failover from a Windows client:
>
> You can switch logon servers with "nltest /server:<clientcomputer>
> /sc_reset:<domain\dc>"
> https://www.technipages.com/windows-how-to-switch-domain-controller
>
> So try this -- (I just did this on one of my DC's):
> * Switch a Windows Client to DC4
> * Verify with "nltest /dsgetdc:<domain>" and "nltest /sc_query:<doma...
2020 Feb 13
2
Failover DC did not work when Main DC failed
On 13/02/2020 16:28, Paul Littlefield wrote:
> On 13/02/2020 15:17, Rowland penny via samba wrote:
>> The various ways have already been mentioned, but are all your DCs
>> listed as nameservers (NS) in the SOA's for the forward and reverse
>> zones ?
>
>
> I think so...
>
>
> root at dc3.mydomain.com ~ $ (screen) samba-tool dns query dc3
>
2020 Jun 01
2
several dns issues after switching fsmo roles to samba-dc
Hello,
I've finally decided to switch all FSMO roles from Windows 2008 R2 DC (vm-dc1)
to one of the two Samba 4.12.3 DCs (vm-dc3). Here are several issues I've faced
after that:
1. After connecting DNS Manager to the all DCs, I've found that the SOA record
for my domain and msdcs zones still point to the former PDC - vm-dc1.
Is that OK?
2. So, I've changed the SOA manually