Forum Discussion
RPC server is unavailable
- BAMAZAD01 is DHCP assigned which should never happen for a domain controller, should always be static!
- On BAMAZAD01 I'd add the server's own static ip address (10.100.5.4) listed for DNS, then do ***ipconfig /flushdns, ipconfig /registerdns***, restart the ***netlogon*** service
- On BAMTORDC02 I'd add the server's own static ip address (10.10.10.182) listed for DNS, then do ***ipconfig /flushdns, ipconfig /registerdns***, restart the ***netlogon*** service
- bardrdc02.txt file is for BAMDRDC02
- dcdiag was run from BAMTORDC02 which seems to have a lot of problems. I'd check the event logs for related errors. Better run from BAMTORDC01
BAMTORDC01 is the problematic server that we can't connect to from ADUC or any active directory services.
I'm getting a lot of this on BAMTORDC01
Starting test: KccEvent
* The KCC Event log test
A warning event occurred. EventID: 0x800004C0
Time Generated: 08/31/2021 16:21:41
Event String:
Internal event: An LDAP client connection was closed because of an error.
I'm not sure if moving the DC away from DC OU caused a lot of this issue or not. I just found this out a few minutes ago.
- Dave PatrickAug 31, 2021MVP
I'd make the corrections, check the event logs and if problems persist put up a new set of files to look at.
- seyah96Aug 31, 2021Copper Contributor
I'm not able to connect to BAMTORDC01. I can connect from BAMTORDC01 to other DC from ADUC though. I also tested dcdiag netlogons and BAMTORDC01 failed.
I have uploaded full test result I ran from BAMTORDC01 on the same onedrive link.
Please let me know your thoughts.
Thanks!
- Dave PatrickSep 01, 2021MVP
- A lot of these possibly because of problematic site to site connectivity.
An LDAP client connection was closed because of an error. 1236 The network connection was aborted by the local system.
- I'd work through this one for the Kerberos errors
https://social.technet.microsoft.com/wiki/contents/articles/2064.kerberos-error-code-0x7-kdc-err-s-principal-unknown-dsforum2wiki.aspx- The oldest domain controller is 2012 R2 so when you get the domain healthy I'd get the old FRS replication technology migrated to DFSR
https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405