Answer the question
In order to leave comments, you need to log in
Why are there no NETLOGON balls on one of the CDs?
For some reason, when I raise a new CD (domain controller) in the domain, the NETLOGON ball does not appear on it, and SYSVOL replication is normal, all folders are synchronized. The SYSVOL sphere appears, but there is no NETLOGON, the scripts folder is present in the system where NETLOGON usually refers.
I did a restore through the BurFlags D2 registry, it does not help, the ball does not appear. Scanned for open ports on both CDs, all ports needed for AD to work are open.
Port 53 (TCP) Port 88 (TCP) Port 135 (TCP) Port 139 (TCP) Port 389 (TCP) Port 445 (TCP) Port 464 (TCP) Port 593 (TCP) Port 636 (TCP) Port 3268 (TCP) Port 3269 (TCP)
dcdiag swears that the NETLOGON ball is missing.
Run check: NetLogons
Unable to connect to NETLOGON share. (\\MASTERAD\netlogon)
[MASTERAD] net use or LsaPolicy operation failed with error 67, Network name not found..
........................ MASTERAD - NetLogons check failed
By hostname servers see each other, ping by hostname passes, nslucap also sees them.
I do not know colleagues, where to dig?
I even installed a clean version of Windows on a virtual machine, and joined the CD to the domain, the same thing, there is no logon.
We have a forest of the 2003 level, since we have one CD 2003 R2 Windows, and two CD 2012 R2 Windows are on them.
And by the way, when I came here, I saw that in the netlogon folder there is a 1c distribution kit for installation over the network.
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question