2012 R2 standard Replica DC cant connect to the main DC to be promoted

-

hi everyone,

i have strange issue adding additional dc replica/backup, dc might need hardware maintenance , not sure how long out of order. 

both servers 2012 r2 standard, , when installed 1 trying add replica, had evaluation. have not been able it, converted full retail standard version key, , tried promote it, didnt work. keeps saying there communication. 

the servers added domain, can ping main dc, can nslookup, cant open connection using ldp port 398.

dns added advanced settings of ipv4, ipv6 disabled, saw in other posts try, firewall not blocking because tried , without firewall. server has static ip, has dns role installed (also suggested other post), keep getting same error when trying promote 1 dc. event viewer time time gives netlogon error of not being able contact dc. communication there, can see it, blocking being recognized when run dcpromo wizard.

hi

 you should check port accessibility , dns config,run "ipconfig /all" on both , can check ports portqryui ; https://www.microsoft.com/en-us/download/details.aspx?id=24009

also should check dcpromo log's "%systemroot%\debug\dcpromo.log" to analyse issue.                            

<button class="play_button" disabled="disabled" id="top-playbutton" type="button"></button>

this posting provided no warranties or guarantees,and confers no rights. best regards burak uğur



Windows Server  >  Directory Services



Comments

Post a Comment

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

-
looking options resolve error , prevent in future. thanks help. hardware: 2 node dell hv cluster running2012r2 dc 8 nic/ea in multiplex mode 4x hyper-v 4x hosts storage: 2x synology nas, accessed through iscsi hosts , cluster relevant logs: log name:      microsoft-windows-failoverclustering/diagnostic source:        microsoft-windows-failoverclustering date:          event id:      2050 task category: none level:         warning keywords:       user:          system computer:      l description: [dcm] filter wimmount found @ unsafe altitude 180700 log name:      system source:        microsoft-windows-failoverclustering date:         event id:      5125 task category: cluster shared volume level:         warning keywords:       user:          system computer: description: cluster shared volume 'volume1' ('cluster disk 1') has identified 1 or more active filter drivers on device stack interfere csv operatio
Read more

Failed to delete the test record dcdiag-test-record in zone test.com

-
ps c:\users\administrator.test> dcdiag /test:dns directory server diagnosis performing initial setup:    trying find home server...    home server = dc02    * identified ad forest.    done gathering initial info. doing initial required tests    testing server: default-first-site-name\dc02       starting test: connectivity          ......................... dc02 passed test connectivity doing primary tests    testing server: default-first-site-name\dc02       starting test: dns          dns tests running , not hung. please wait few minutes...          ......................... dc02 passed test dns    running partition tests on : forestdnszones    running partition tests on : domaindnszones    running partition tests on : schema    running partition tests on : configuration    running partition tests on : test    running enterprise tests on : test.com       starting test: dns          test results domain
Read more

Azure MFA with Azure AD and RDS

-
i have setup following lab in azure , need help. a server (domain controller) , remote desktop services. and server multi factor authentication server. i have setup following one http://www.rdsgurus.com/uncategorized/step-by-step-using-windows-server-2012-r2-rd-gateway-with-azure-multifactor-authentication/ and when im connecting got following error. the user "domain\username", on client computer "xxx.xxx.xxx.xxx", did not meet connection authorization policy requirements , therefore not authorized access rd gateway server. authentication method used was: "ntlm" , connection protocol used: "rpc-http". following error occurred: "23003". also on security log i've got following authentication details: connection request policy name: ts gateway authorization policy network policy name: - authentication provider: radius proxy authentication server: test.test.local authentication type: - eap t
Read more