Problems adding W2k8 (not R2) DC to W2k Domain


curious problem adding w2k8 dc existing w2k domain.

i have followed instructions of meinolf weber, e.g. netdiag, dcdiag, adprep, transferring fmso roles, establishing reliable external time server, etc.

on new w2k8 dc, when point dns existing dc, new dc performs well.  however, when point dns new dc , restart, dc not seem function correctly.

1. network properties no longer shows domain name network, instead shows "network"

2. event log contained numerous warnings after assigning local ip dns , restarting. see below: (i can provide details if needed)

warning    3/28/2015 8:59:33 am    dns-server-service    4013    none
error    3/28/2015 8:59:08 am    grouppolicy    1129    none
warning    3/28/2015 8:59:08 am    winlogon    6006    none
warning    3/28/2015 8:58:37 am    time-service    134    none
error    3/28/2015 8:58:28 am    dfsr    1202    none
warning    3/28/2015 8:58:24 am    lsasrv    40960    (3)
warning    3/28/2015 8:58:23 am    time-service    134    none
warning    3/28/2015 8:58:13 am    lsasrv    40960    (3)
warning    3/28/2015 8:58:09 am    lsasrv    40960    (3)
warning    3/28/2015 8:57:50 am    netlogon    3096    none
warning    3/28/2015 8:57:28 am    dns-server-service    4013    none
warning    3/28/2015 8:56:46 am    activedirectory_domainservice    2088    ds rpc client
warning    3/28/2015 8:56:10 am    winlogon    6005    none
warning    3/28/2015 8:55:23 am    dns-server-service    4013    none
warning    3/28/2015 8:55:18 am    kerberos-key-distribution-center    29    none

so far, have transferred fmso roles old server once , demoted new dc , removed ad completely.  reinstalled ad under different machine name , still experiencing same issue.

i @ loss , appreciate assistance.

thanks.

if it's not working when point new 2008 dc dns, tells me dns data not replicating. when installed dns on 2008 dc, has additional options 2000 has no idea are. if had administered 2008, may have introduced new options causing zone data not replicate.

the rule of thumb install dns on new dc, , continue administer dns oldes common denominator until rid of them or update them.

go dns on new one, right-click ad zone name, , tell me replication scope did set to.


ace fekay
mvp, mct, mcse 2012, mcitp ea & mcts windows 2008/r2, exchange 2013, 2010 ea & 2007, mcse & mcsa 2003/2000, mcsa messaging 2003
microsoft certified trainer
microsoft mvp - directory services
complete list of technical blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php

this posting provided as-is no warranties or guarantees , confers no rights.

facebook twitter linkedin



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