Domain controller issue
Lance Soller
Starting test: LocatorCheck
Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1707
A Global Catalog Server could not be located - All GC's are down.
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1707
A Primary Domain Controller could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(TIME_SERVER) call failed, error 1707
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1707
A Good Time Server could not be located.
Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1707
A KDC could not be located - All the KDCs are down.
......................... domain.local failed test LocatorCheck
Starting test: Intersite
......................... domain.local passed test Intersite
Thank You,
Lance Soller
Tristate Computers, Inc.
“An issue without a ticket is an issue that never happened”
Michael B. Smith
1707 means “The network address is invalid.”
I’d be checking DNS.
--
You received this message because you are subscribed to the Google Groups "ntsysadmin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
ntsysadmin+...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ntsysadmin/CAJ6FWM2A_wQpt-oU%2B1tzmBstK%3D4KD1myu%3DWLM4-hwH%3Do4Jkt3w%40mail.gmail.com.
Lance Soller
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/b047b7afa6d24c3baeb2ad250cc6ef30%40smithcons.com.
Aakash Shah
No personal experience with this specific error, but it could be missing SRV records. My guess would be to check on this since it mentions Global Catalog:
_ldap._tcp.gc._msdcs.<domain FQDN>
If so, check the DNS configuration on the PDC and then restart the Netlogon service so it can recreate the SRV records. Consider running a Best Practices Analyzer in “AD DS” and “DNS” from Server Manager since this may help point out misconfigurations too.
-Aakash Shah
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/CAJ6FWM0ggvJQj0Pz%3Dg2sv%3DHfydKN%2ByE1r95YN4woYZsjOcXcsQ%40mail.gmail.com.
Philip Elder
Did you test the DNS AD GUID for resolution?
Philip Elder MCTS
Senior Technical Architect
Microsoft High Availability MVP
E-mail: Phili...@mpecsinc.ca
Phone: +1 (780) 458-2028
Web: www.mpecsinc.com
Blog: blog.mpecsinc.com
Twitter: Twitter.com/MPECSInc
Skype: MPECSInc.
Please note: Although we may sometimes respond to email, text and phone calls instantly at all hours of the day, our regular business hours are 8:00 AM - 5:00 PM, Monday thru Friday.
From: 'Lance Soller' via ntsysadmin <ntsys...@googlegroups.com>
Sent: Monday, June 3, 2024 08:07
To: ntsys...@googlegroups.com
Subject: Re: [ntsysadmin] Domain controller issue
all pings correctly and resolves so don't thin it's DNS
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/CAJ6FWM0ggvJQj0Pz%3Dg2sv%3DHfydKN%2ByE1r95YN4woYZsjOcXcsQ%40mail.gmail.com.
Lance Soller
Thank You,
Lance Soller
Tristate Computers, Inc.
“An issue without a ticket is an issue that never happened”
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/8305e53c12944d9ba382bed96752bc57%40MPECSInc.Ca.