Forum Discussion

franco01's avatar
franco01
Copper Contributor
Oct 08, 2020

DCOM was unable to communicate with the computer

i ran dcdiag  on all my for dc 2,3,4,5   dc2 = windows 2016 dc3 = windows 2012 dc4 = windows 2012 dc5 = windows 2016   I get the following error DCOM was unable to communicate with the comput...
Active Directory
networking
windows server
Dave Patrick's avatar
Dave Patrick
MVP
Oct 08, 2020

If a single DC appears to be problematic it may be configuration and or some corruption. Might try standing up a new one as a test.

 

 

franco01's avatar
franco01
Copper Contributor
Oct 08, 2020

Dave Patrick \ is anyway to fix this it seems little bit overkill to setup another dc

 

  • Dave Patrick's avatar
    Dave Patrick
    MVP
    Oct 08, 2020

    - Each domain controller should also have its own static ip address listed for DNS on connection properties.
    - It looks like all of the "DCOM was unable to communicate" were caused by dcdiag.exe itself so you can safely ignore it.

    - I'd check that windows is patched to the latest cumulative update.
    - DC05 appears to be having some replication problems, you might try demote, reboot, promo it again (of course after roles transfer)
    - As to the ncap adapter you may want to ask the vendor about configuration on a domain controller

     

     

  • franco01's avatar
    franco01
    Copper Contributor
    Oct 08, 2020

    Dave Patrick  here the link in each folder contains unzip files

    https://onedrive.live.com/?id=2DE6AC03276854FD%211151&cid=2DE6AC03276854FD

     

     

  • Dave Patrick's avatar
    Dave Patrick
    MVP
    Oct 08, 2020

    Please run;

    - Dcdiag /v /c /d /e /s:%computername% >c:\dcdiag.log
    - repadmin /showrepl >C:\repl.txt
    - ipconfig /all > C:\dc1.txt
    - ipconfig /all > C:\dc2.txt
    - (etc. as other DC's exist)


    then put **unzipped** text files up on OneDrive and share a link.

     

     

     

     

Resources