dcdiag errors

  • Thread starter Thread starter James
  • Start date Start date
J

James

please help! below is my output from dcdiag. i've changed the server names
to generic ones though.

things that concern me are the test Advertising. server1.company.com was the
first
server in the forest/domain. i've transferred the fsmo roles to another
server and
i've recently demoted that server from being a global catalog. server2 is a
global catalog server
so why is it saying SERVER2 is not advertising as a global catalog? why is
it saying
its trying to reach server1 when we were actually trying to reach server2?
doesn't
make sense at all.

the last test where it says fsmocheck. why is it telling me all GC's are
down? how
can you tell if its up or down? my GC's has to be up because my exchange
server
is running fine and logons are being processed fine...

thanks in advance for any help!

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

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\SERVER2
Starting test: Connectivity
......................... SERVER2 passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\SERVER2
Starting test: Replications
......................... SERVER2 passed test Replications
Starting test: NCSecDesc
......................... SERVER2 passed test NCSecDesc
Starting test: NetLogons
......................... SERVER2 passed test NetLogons
Starting test: Advertising
Warning: DsGetDcName returned information for
\\server1.company.com, when we were trying to reach SERVER2.
Server is not responding or is not considered suitable.
Warning: SERVER2 is not advertising as a global catalog.
Check that server finished GC promotion.
Check the event log on server that enough source replicas for the
GC are available.
......................... SERVER2 failed test Advertising
Starting test: KnowsOfRoleHolders
......................... SERVER2 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... SERVER2 passed test RidManager
Starting test: MachineAccount
......................... SERVER2 passed test MachineAccount
Starting test: Services
......................... SERVER2 passed test Services
Starting test: ObjectsReplicated
......................... SERVER2 passed test ObjectsReplicated
Starting test: frssysvol
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... SERVER2 passed test frssysvol
Starting test: kccevent
......................... SERVER2 passed test kccevent
Starting test: systemlog
......................... SERVER2 passed test systemlog

Running enterprise tests on : company.com
Starting test: Intersite
......................... company.com passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
A Global Catalog Server could not be located - All GC's are down.
......................... company.com failed test FsmoCheck
 
Ok - for the advertising problem the issues may be related - they may not
be.

For problem 1 dcdiag has asked the dc locator to return a dc for the local
domain. Since you are running it on SERVER2 it is expecting SERVER2 to be
the name of the server returned.
http://support.microsoft.com/default.aspx?scid=kb;en-us;247811 has
information on how DCs are located in Windows. Try the steps listed in the
"Troubleshooting the Domain Locator Process" section to resolve it. It
could be a DNS issue. I'd also do a "net share" command and make sure the
SYSVOL is shared as that will also block advertising. dcdiag performs a
similar check to find a GC. Problem 2 is indicating when it queries it is
not finding the SERVER2 as a GC. Check the eventlog for possible errors.

Take care of Problem 1 and see if that resolves Problem 2 and the fsmocheck
problem. If not, post back on this thread.

Jason

Problem 1:
Starting test: Advertising
Warning: DsGetDcName returned information for
\\server1.company.com, when we were trying to reach SERVER2.
Server is not responding or is not considered suitable.


Problem 2:
Warning: SERVER2 is not advertising as a global catalog.
Check that server finished GC promotion.
Check the event log on server that enough source replicas for the
GC are available.
......................... SERVER2 failed test Advertising
 
Back
Top