Failed advertising Test

[DJ]

Archived from groups: microsoft.public.win2000.dns (More info?)

Hello,

I have a problem on my DC. I have attatched the DCDIAG log. It is in the
section related to advertising. Any ideas or suggestions are appreciated.
Many thanks,
DJ

DCDIAG
Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

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

Doing primary tests

Testing server: Default-First-Site\MELYX1
Starting test: Replications
......................... MELYX1 passed test Replications
Starting test: NCSecDesc
......................... MELYX1 passed test NCSecDesc
Starting test: NetLogons
......................... MELYX1 passed test NetLogons
Starting test: Advertising
Warning: DsGetDcName returned information for \\MELYX.HCCWIN.local,
when we were trying to reach MELYX1.
Server is not responding or is not considered suitable.
......................... MELYX1 failed test Advertising
Starting test: KnowsOfRoleHolders
......................... MELYX1 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... MELYX1 passed test RidManager
Starting test: MachineAccount
......................... MELYX1 passed test MachineAccount
Starting test: Services
......................... MELYX1 passed test Services
Starting test: ObjectsReplicated
......................... MELYX1 passed test ObjectsReplicated
Starting test: frssysvol
......................... MELYX1 passed test frssysvol
Starting test: kccevent
......................... MELYX1 passed test kccevent
Starting test: systemlog
......................... MELYX1 passed test systemlog

Running enterprise tests on : HCCWIN.local
Starting test: Intersite
......................... HCCWIN.local passed test Intersite
Starting test: FsmoCheck
......................... HCCWIN.local passed test FsmoCheck

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

I'm assuming you've already done a netdiag /fix.

dcdiag expects the DC you're it running on to be the response to the domain locator call. The advertising test failure is telling
you that another DC answered instead (I'm assuming here that MELYX is another real DC in your domain and not some type of alias name
you've defined for MELYX1 - that would likely be the problem if so.)

So, start with this KB article on how how to troubleshoot DC location problems:

http://support.microsoft.com/default.aspx?scid=kb;en-us;247811

Unfortunately it is a rather tedious process, but no choice.

Steve Duff, MCSE, MVP
Ergodic Systems, Inc.

"DJ" <DJ@discussions.microsoft.com> wrote in message news:06062005-F83F-4DAF-ADDD-EDA42728612E@microsoft.com...
> Hello,
>
> I have a problem on my DC. I have attatched the DCDIAG log. It is in the
> section related to advertising. Any ideas or suggestions are appreciated.
> Many thanks,
> DJ
>
> DCDIAG
> Domain Controller Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: Default-First-Site\MELYX1
> Starting test: Connectivity
> ......................... MELYX1 passed test Connectivity
>
> Doing primary tests
>
> Testing server: Default-First-Site\MELYX1
> Starting test: Replications
> ......................... MELYX1 passed test Replications
> Starting test: NCSecDesc
> ......................... MELYX1 passed test NCSecDesc
> Starting test: NetLogons
> ......................... MELYX1 passed test NetLogons
> Starting test: Advertising
> Warning: DsGetDcName returned information for \\MELYX.HCCWIN.local,
> when we were trying to reach MELYX1.
> Server is not responding or is not considered suitable.
> ......................... MELYX1 failed test Advertising
> Starting test: KnowsOfRoleHolders
> ......................... MELYX1 passed test KnowsOfRoleHolders
> Starting test: RidManager
> ......................... MELYX1 passed test RidManager
> Starting test: MachineAccount
> ......................... MELYX1 passed test MachineAccount
> Starting test: Services
> ......................... MELYX1 passed test Services
> Starting test: ObjectsReplicated
> ......................... MELYX1 passed test ObjectsReplicated
> Starting test: frssysvol
> ......................... MELYX1 passed test frssysvol
> Starting test: kccevent
> ......................... MELYX1 passed test kccevent
> Starting test: systemlog
> ......................... MELYX1 passed test systemlog
>
> Running enterprise tests on : HCCWIN.local
> Starting test: Intersite
> ......................... HCCWIN.local passed test Intersite
> Starting test: FsmoCheck
> ......................... HCCWIN.local passed test FsmoCheck
>