Re: Deleted server #1

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Make sure you don't have some lingering DNS records pointing to these
servers.

--
Hope it helps

dw

_______________________________
Don Wilwol
donwilwol(DELETE)@yahoo.com
http://spaces.msn.com/members/wilwol/


"Glenn" <Glenn@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4739E1E9-279E-4CAE-8815-7708D3B5822F@xxxxxxxxxxxxxxxx
>I wonder if someone can help me I have been trying to figure this out for a
> week.
>
> I have a 2000/20003 domain I demoded 2 servers that were servers 2000 OS (
> DC's) from the domain, the dcpromo.log shows all went ok the servers were
> removed from the active directory and now member servers. I also after a
> week
> made the 2 servers as workgroup.
>
> Now here is the problem both these servers show up when you run repmon
> this
> is the log of the error
> Partner Name: **DELETED SERVER #1
> Partner GUID:
> Last Attempted Replication: 8/28/2005 11:45:05 AM (local)
> Last Successful Replication: 8/23/2005 10:21:38 AM (local)
> Number of Failures: 122
> Failure Reason Error Code: 8524
> Failure Description: The DSA operation is unable to proceed
> because of a DNS lookup failure.
> Synchronization Flags:
> DRS_WRIT_REP,DRS_INIT_SYNC,DRS_PER_SYNC
> USN of Last Property Updated: 10969162
> USN of Last Object Updated: 10969162
> Transport:
>
> when I run repadmin /showreps I get this error
> Default-First-Site-Name\SABAHIYA_3\0ADEL:56c122ce-289c-4e72-9603-693725e90200
> (deleted DSA) via RPC DC object GUID:
> 5f7f4034-79a3-4eba-a111-8aebd7c40cb8
>
> I have tried the ndsutil, the lingringobject removal option using repadmin
> and adsiedit.
>
> Its' been 2 weeks now the error still shows. by the way thi is just the
> error of one of the servers just to keep the message short. can any one
> fiugure this out
>
> Thanks in advance
>


.

Relevant Pages

  • Re: Deleted server #1
    ... FSMO's roles if so did you complete a warm transfer before removing AD. ... > Make sure you don't have some lingering DNS records pointing to these ... the dcpromo.log shows all went ok the servers were ... >> when I run repadmin /showreps I get this error ...
    (microsoft.public.windows.server.active_directory)
  • Re: Deleted server #1
    ... >> running repadmin shows only in the child domain default first site ... > You mean to say the list above does not show the servers that show up in the ... > metadata cleanup, it has to exist somewhere for repadmin to believe it still ... > remote into your machine using Terminal services. ...
    (microsoft.public.windows.server.active_directory)
  • Re: FRS errors 13508 and 13559
    ... Run dcdiag, netdiag and repadmin in verbose mode. ... All dc's are DNS and WINS servers. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Pro-active Maintenance
    ... It also depends upon how broadly you define "AD maintenance" ... So I would also add repadmin /showrepl (or /showutdvec if you're running ... > Support Tools on all of my servers (Domain Controllers, Exchange Servers, ...
    (microsoft.public.win2000.active_directory)
  • Re: AD not replicating
    ... It passes both test with itself but doesn't test any other servers. ... admin.pak) I get the response dcdiag or repadmin is not a recognised command. ... Randy ...
    (microsoft.public.windows.server.active_directory)