Archived from groups: microsoft.public.win2000.active_directory (
More info?)
try doing a netdiag /fix
http://support.microsoft.com/default.aspx?scid=kb;en-us;219289
--
Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA
This posting is provided "AS IS" with no warranties, and confers no rights.
"Genbar" <Genbar@discussions.microsoft.com> wrote in message
news:7D8D1D48-1DEC-45D2-A405-FA7ED53F1E59@microsoft.com...
>I am having the same problem and it was suggested that I view this posting
> string. when I run dcdiag i get the following result.
> D:\I386>dcdiag
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: Default-First-Site-Name\MCS_SERVER2
> Starting test: Connectivity
> MCS_SERVER2's server GUID DNS name could not be resolved to an
> IP address. Check the DNS server, DHCP, server name, etc
> Although the Guid DNS name
> (f7e23a0a-e7f4-4d97-be3f-47abec878a50._msdcs.MCS) couldn't be
> resolved, the server name (MCS_SERVER2.MCS) resolved to the IP
> address
> (192.168.0.4) and was pingable. Check that the IP address is
> registered correctly with the DNS server.
> ......................... MCS_SERVER2 failed test Connectivity
>
> Doing primary tests
>
> Testing server: Default-First-Site-Name\MCS_SERVER2
> Skipping all tests, because server MCS_SERVER2 is
> not responding to directory service requests
>
> Running enterprise tests on : MCS
> Starting test: Intersite
> ......................... MCS passed test Intersite
> Starting test: FsmoCheck
> ......................... MCS passed test FsmoCheck
> I dont know if the same thing is going on for both of us but it sounds
> close.
> Thanks for any help you can give.
>
> Gene Baron, MCSE
>
> "Paul Bergson" wrote:
>
>> Ok it sounds like you might not have a fsmo role holder that is currently
>> up
>> and running.
>>
>> per the KB
http://support.microsoft.com/Default.aspx?kbid=839879 get the
>> info but hold off on the resolution
>>
>> basically I'm wondering about your rid master for starters, post the rid
>> feedback in here. I will be gone for a couple of hours but will check up
>> on
>> it when I get back.
>>
>> --
>>
>>
>> Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>> "b_vankur" <bvankur@discussions.microsoft.com> wrote in message
>> news:26F12C5A-8700-426C-8C92-876996AA21BE@microsoft.com...
>> > here are the results
>> >
>> > script had errors and would not run so i tried it one line at a time
>> > dcdiag found
>> > passed replications
>> > passed topology
>> > pased cutoffservers
>> > passed NCSecCesc
>> > passed netlogons
>> > failed test KnowsOfRoleHolders (found reference to an old dc that was
>> > removed years ago) ?????????
>> > failed RidManager (same reference to old dc )gave me a CID number do i
>> > need
>> > to delete this from the registry?????????
>> > passed MachineAcount
>> > a few services are stopped (IsmServ,TrkWks,TrkSvr,IISADMIN and
>> > SMTPSVC)
>> >
>> > all other tests passed
>> > netdiag.exe [FATAL] Failed to get system information of this machine
>> > repadmin.exe gave a usage error [did not like the syntax or something]
>> >
>> > thanks
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > "b_vankur" wrote:
>> >
>> >> thanks paul i give it a try
>> >>
>> >> "Paul Bergson" wrote:
>> >>
>> >> > Try running netdiag, repadmin and dcdiag. Look for fail, error and
>> >> > warning
>> >> > errors.
>> >> >
>> >> > If you don't have the tools installed load them from your install
>> >> > disk.
>> >> >
>> >> > d:\i386\adminpak.msi (Server tools for remote management of
>> >> > servers)
>> >> > d:\support\tools\setup.exe (Server Utilities)
>> >> >
>> >> > Copy the following to a cmd file and run look for error, fail and
>> >> > warn
>> >> > within the reports. Post any errors you can't figure out. make sure
>> >> > you
>> >> > modify DC_Name to the name of a dc in your domain.
>> >> >
>> >> >>
>> >> >
>> >> > Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA
>> >> >
>> >> > This posting is provided "AS IS" with no warranties, and confers no
>> >> > rights.
>> >> >
>> >> >
>> >> > "b_vankur" <bvankur@discussions.microsoft.com> wrote in message
>> >> > news:4CB96105-FF7E-4331-8D20-106436306C88@microsoft.com...
>> >> > >I am tryinig to move my 2k dc to a 2003k dc i read that you have to
>> >> > >run
>> >> > > adprep before trying to dcpromo to the 2003 server i ran the
>> >> > > adprep
>> >> > > /forestprep and had no problems but when i try to run the adprep
>> >> > > /domainprep
>> >> > > i get the error "adprep was unable to check the domain update
>> >> > > status"
>> >> > > and
>> >> > > ""adprep encountered an LDAP error {Error code: 0x20. Server
>> >> > > extended
>> >> > > error
>> >> > > code 0x208d, Server error message:0000208D: nameErr:
>> >> > > DISID-031001bd ,
>> >> > > problem
>> >> > > 2001 (NO_OBJECT), data 0, best match of:
>> >> > > CN=Servers,CN=Default-First-Site,
>> >> > > CN=Sites, CN=Configuration, DC=abccorp, DC=abc DC=com' so what is
>> >> > > this
>> >> > > telling me????????? i tried to run adprep /forestprep again but
>> >> > > isaid
>> >> > > that
>> >> > > it has allready run so it stoped any help would be greatly
>> >> > > apreicated.
>> >> > > what
>> >> > > i want to do is add the 2003k as a backup dc then than transfer
>> >> > > the
>> >> > > FSMO
>> >> > > roles and remove the old system from the domain
>> >> > > thanks in advance for any help.
>> >> >
>> >> >
>> >> >
>>
>>
>>
C_Name /f:c:\dcdiag.log
Facebook
Twitter
Instagram