Auth to second domain failing


we have 2 windows server 2008 r2 domains on our network. domain a, have pdc , bdc. pdc @ different location , offline months (not choice). has been stable.  yesterday afternoon pdc brought in house , attached network.  @ time, users domain b not able logon servers in domain a.

i have shutdown pdc.  checking system log on bdc, see event id 28 seems related issue: when generating cross realm referal domain b the kdc not able find suitable key verify ticket. ticket key version in request 30 , available key version 29. common reason error delay in replicating keys. in order remove problem try forcing replication or wait replication of keys occur.

when trying on bdc domain a, resolution offered here not help: http://technet.microsoft.com/en-us/library/dd348743(v=ws.10).aspx

i not sure if not working because 1) shutdown pdc , that's option force replication to, or 2) it's domain b needs replication , domain not referenced here.

how out of mess?  tia ...

thank help.

i ended making sure current dc (apparently forest in w2k3 mode), seized fmso roles it, , then demoted /forceremoval the problematic dc.

to correct issue of auth other domain, had follow step seemed correct it:
http://blogs.technet.com/b/askpfeplat/archive/2012/11/23/fixing-when-your-domain-traveled-back-in-time-the-great-system-time-rollback-to-the-year-2000.aspx#_2av)_troubleshooting_error

i seeing these errors on place when trying correct lingering objects and replication errors.

for cleaning metadata /forceremoval dc, guide follow:
http://www.petri.co.il/delete_failed_dcs_from_ad.htm

finally, reinstalled bad dc scratch.  happy now.

thanks again!



Windows Server  >  Directory Services



Comments

Popular posts from this blog

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

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

Azure MFA with Azure AD and RDS