DCDIAG /A only tests DC's in one site???

[bdoub1eu]

Hi all...I am in the process of preparing to upgrade AD from 2000 to 2003. We have one domain and two sites. Under Site A, I have two DC's and under Site B, I have one DC. Site A servers are 10.3.100.x and Site B server is 10.3.101.x.

In running the DCDIAG /A tool on one of the servers in Site A, it only tests those two servers in site A...NOT the server in Site B...And vice versa, when I run it on the server in Site B, it doesn't check the servers in Site A...Is this normal? Other than that, replication is fine...

 

[mlichstein]

If you run dcdiag /? you will see that /a only test servers in a site.

/e will test all servers in the enterprise.

 

[bdoub1eu]

You beat me to it...I was about to say the same thing...Found out about /e on another site...

Thanks!

 

[bdoub1eu]

I do receive the 1060 error when I ran dcdiag on one of the servers...

Testing server: Harrisburg\STARFLEET
Starting test: Replications
......................... STARFLEET passed test Replications
Starting test: NCSecDesc
......................... STARFLEET passed test NCSecDesc
Starting test: NetLogons
......................... STARFLEET passed test NetLogons
Starting test: Advertising
......................... STARFLEET passed test Advertising
Starting test: KnowsOfRoleHolders
......................... STARFLEET passed test KnowsOfRoleHolders
Starting test: RidManager
......................... STARFLEET passed test RidManager
Starting test: MachineAccount
......................... STARFLEET passed test MachineAccount
Starting test: Services
Could not open SMTPSVC Service on [STARFLEET]:failed with 1060: The specified service does not exist as an installed service.
......................... STARFLEET failed test Services
Starting test: ObjectsReplicated
......................... STARFLEET passed test ObjectsReplicated
Starting test: frssysvol
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
......................... STARFLEET passed test frssysvol
Starting test: kccevent
......................... STARFLEET passed test kccevent
Starting test: systemlog
......................... STARFLEET passed test systemlog




Any idea what the 1060 is referring to?

 

[mlichstein]

That is a bug with dcdiag on 2000 DCs:

http://support.microsoft.com/?kbid=321869

If you aren't using SMTP for AD replication, you can ignore it.

 

[bdoub1eu]

SMTP for AD replication??? This may sound like a stupid question, but how would I know?

Also in the log, I saw:
Starting test: frssysvol
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting

As far as I know, we don't use FRS...

 

[mlichstein]

Yes, you can use SMTP for replication:

http://www.microsoft.com/resources/...to_what.asp?FRAME=True#w2k3tr_repto_what_nfjw

And yes, you use FRS. A server is not a domain controller until it shares the sysvol directory. The data in this directory is replicated between DCs using FRS.

I dont think you have any problems with FRS, but you can run a 'net share' command from the cmd prompt to check for sysvol and netlogon.

 

[bdoub1eu]

Here's what I got when I ran the net share on this DC:


Share name Resource Remark


-------------------------------------------------------------------------------
IPC$ Remote IPC

D$ D:\ Default share

connect$ C:\exchsrvr\connect "Access to gateway connectors"

C$ C:\ Default share

ADMIN$ C:\WINNT Remote Admin

E$ E:\ Default share

Add-ins C:\exchsrvr\add-ins "Access to EDK objects"

Address C:\exchsrvr\address "Access to address objects"

NETLOGON C:\WINNT\SYSVOL\sysvol\chemspec.com\SCRIPTS
Logon server share

Resources C:\exchsrvr\res "Event logging files"

SYSVOL C:\WINNT\SYSVOL\sysvol Logon server share

tracking.log C:\exchsrvr\tracking.log "Exchange message tracking logs"

VPHOME C:\PROGRA~1\SAV Symantec AntiVirus

VPLOGON C:\PROGRA~1\SAV\logon Symantec AntiVirus
The command completed successfully.

 

[mlichstein]

That looks good.

 

[bdoub1eu]

Wonder why I get that error if the FRS is fine...

 

[mlichstein]

It's not really an error, it's just saying theres no record of FRS.

My guess is that there isn't a 13516 event in the FRS log (maybe the log was cleared?) and that is what dcdiag looks for.

If you stop and start the ntfrs service and re-run dcdiag, the 'error' will probably go away.

 

[bdoub1eu]

Will stopping and starting the ntfrs service affect anything?

 

[mlichstein]

No, it will only mean there will be no file replication between that DC and any other DC for that brief period. This would only be a problem if you were changing the sysvol directory, like if you were editing a group policy, or adding a script.

 

[bdoub1eu]

Thanks so much for the insight! You sure know your stuff!