DC's are having trouble replicating and we're getting "The target account is incorrect" errors all the time...

okay, think we've messed things time.

we've had 2 dc's running windows server 2003, and, until recently, they've been co-existing peacefully. then, on 1 of them (we'll call "dc1"), c: drive filled , admin supposed watching didn't notice (we don't use else other dc).

so, replication stopped happening dc2 dc1 because drive full. then, condition lasted longer tombstone lifetime, dc's stopped *trying* replicate until had dealt lingering objects. well, tried of ways of running repadmin /removelingeringobjects found on net, "invalid arguments" error, no explanation why.

so, couldn't remove lingering objects. wasn't bad, because our domain changes and, i've read, issue forcing replication lingering objects present deleted objects can come life in domain. well, wouldn't of issue, used registry tell dc1 go ahead , replicate, though tombstone lifetime had been exceeded.

and seemed work. now, we're seeing host of issues can't find way around. *big* problem our member pc's, when try connect shared folder on either of dc's, "logon failure: target account name incorrect.".

there still seem residual issues between 2 dc's. in effort resolve them, thought might able demote , re-promote  one of dc's. when tried demoting dc1 (the 1 who's drive filled up), refused because couldn't transfer of fsmo roles dc2.

things more strange when try demote dc2 (the 1 who's drive did not fill up): first, tells that, though we've indicated we're not last dc, cannot find other dc's domain. when tell don't care , should proceed anyway, stops saying couldn't find dc domain, ,  "the specified domain either not exist or not contacted".

so... thought add third dc might register other two. accept fsmo roles dc1, demote/promote it, , should findable dc2, demote/promote well. however, when try add third dc domain (not promote dc, mind you... add our domain), "the target account incorrect" error.

so, we're pretty stumped @ point. oh, , i've noticed dc2 has "sysvol" shared, dc1 doesn't. don't know how plays picture...

hi!

have seen following links?

 

use repadmin remove lingering objects:

http://technet.microsoft.com/en-us/library/cc785298(ws.10).aspx

 

cleaning lingering objects across forest repldiag.exe [part 2 of

4]:

http://blogs.technet.com/b/robertbo/archive/2010/11/07/cleaning-lingering-objects-across-the-forest-with-repldiag-exe-part-2-of-4.aspx

 

what message did received on dc1 while couldn't transfer

fsmo roles?

 

----------------------------------------------------------

 

enfo zipper

christoffer andersson – principal advisor

 

"jemenake" wrote in message news:62fd452a-ea90-4235-b5b0-645484c3d5d8...

 

okay, think we've messed things time.

 

we've had 2 dc's running windows server 2003, and, until recently, they've

been co-existing peacefully. then, on 1 of them (we'll call "dc1"),

c: drive filled , admin supposed watching didn't

notice (we don't use else other dc).

 

so, replication stopped happening dc2 dc1 because drive

full. then, condition lasted longer tombstone lifetime,

dc's stopped *trying* replicate until had dealt lingering

objects. well, tried of ways of running repadmin

/removelingeringobjects found on net,

"invalid arguments" error, no explanation why.

 

so, couldn't remove lingering objects. wasn't bad, because

our domain changes and, i've read, issue

forcing replication lingering objects present deleted

objects can come life in domain. well, wouldn't

of issue, used registry tell dc1 go ahead , replicate,

even though tombstone lifetime had been exceeded.

 

and seemed work. now, we're seeing host of issues

can't find way around. *big* problem our member pc's, when

they try connect shared folder on either of dc's,

"logon failure: target account name incorrect.".

 

there still seem residual issues between 2 dc's. in

effort resolve them, thought might able demote ,

re-promote 1 of dc's. when tried demoting dc1 (the 1 who's drive

filled up), refused because couldn't transfer of fsmo roles

dc2.

 

things more strange when try demote dc2 (the 1 who's drive did

not fill up): first, tells that, though we've indicated

we're not last dc, cannot find other dc's domain. when

tell don't care , should proceed anyway, stops

saying couldn't find dc domain, , "the specified

domain either not exist or not contacted".

 

so... thought add third dc might register

the other two. accept fsmo roles dc1,

demote/promote it, , should findable dc2,

demote/promote well. however, when try add third dc

to domain (not promote dc, mind you... add our

domain), "the target account incorrect" error.

 

so, we're pretty stumped @ point. oh, , i've noticed dc2

has "sysvol" shared, dc1 doesn't. don't know how plays

picture...

 

 

---

enfo zipper christoffer andersson – principal advisor

Windows Server  >  Directory Services