Announcement

Collapse
No announcement yet.

Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355

    Hi All,

    Please help me on this problem. When i am running "dcdiag" on my PDC server i get a message like above. Also i came to know that it has failed to advertise it as a time server , but at the same time when i am running "netdom query fsmo" command it is giving me correct answer and all roles are working fine.

    Please help me . below is the out put of "dcdiag" command.

    Microsoft Windows [Version 5.2.3790]
    (C) Copyright 1985-2003 Microsoft Corp.

    C:\Documents and Settings\dcadmin>dcdiag

    Domain Controller Diagnosis

    Performing initial setup:
    Done gathering initial info.

    Doing initial required tests

    Testing server: APJ-MUMBAI\JMADC
    Starting test: Connectivity
    ......................... JMADC passed test Connectivity

    Doing primary tests

    Testing server: APJ-MUMBAI\JMADC
    Starting test: Replications
    ......................... JMADC passed test Replications
    Starting test: NCSecDesc
    ......................... JMADC passed test NCSecDesc
    Starting test: NetLogons
    ......................... JMADC passed test NetLogons
    Starting test: Advertising
    Warning: JMADC is not advertising as a time server.
    ......................... JMADC failed test Advertising
    Starting test: KnowsOfRoleHolders
    ......................... JMADC passed test KnowsOfRoleHolders
    Starting test: RidManager
    ......................... JMADC passed test RidManager
    Starting test: MachineAccount
    ......................... JMADC passed test MachineAccount
    Starting test: Services
    ......................... JMADC passed test Services
    Starting test: ObjectsReplicated
    ......................... JMADC passed test ObjectsReplicated
    Starting test: frssysvol
    ......................... JMADC passed test frssysvol
    Starting test: frsevent
    There are warning or error events within the last 24 hours after the
    SYSVOL has been shared. Failing SYSVOL replication problems may cause
    Group Policy problems.
    ......................... JMADC failed test frsevent
    Starting test: kccevent
    ......................... JMADC passed test kccevent
    Starting test: systemlog
    An Error Event occured. EventID: 0x0000165B
    Time Generated: 09/28/2011 12:04:39
    Event String: The session setup from computer 'ADMIN-PC' failed
    An Error Event occured. EventID: 0x000016AD
    Time Generated: 09/28/2011 12:06:44
    Event String: The session setup from the computer ADMIN-PC
    ......................... JMADC failed test systemlog
    Starting test: VerifyReferences
    ......................... JMADC passed test VerifyReferences

    Running partition tests on : ForestDnsZones
    Starting test: CrossRefValidation
    ......................... ForestDnsZones passed test CrossRefValidation

    Starting test: CheckSDRefDom
    ......................... ForestDnsZones passed test CheckSDRefDom

    Running partition tests on : DomainDnsZones
    Starting test: CrossRefValidation
    ......................... DomainDnsZones passed test CrossRefValidation

    Starting test: CheckSDRefDom
    ......................... DomainDnsZones passed test CheckSDRefDom

    Running partition tests on : Schema
    Starting test: CrossRefValidation
    ......................... Schema passed test CrossRefValidation
    Starting test: CheckSDRefDom
    ......................... Schema passed test CheckSDRefDom

    Running partition tests on : Configuration
    Starting test: CrossRefValidation
    ......................... Configuration passed test CrossRefValidation
    Starting test: CheckSDRefDom
    ......................... Configuration passed test CheckSDRefDom

    Running partition tests on : jmf
    Starting test: CrossRefValidation
    ......................... jmf passed test CrossRefValidation
    Starting test: CheckSDRefDom
    ......................... jmf passed test CheckSDRefDom

    Running enterprise tests on : jmf.com
    Starting test: Intersite
    ......................... jmf.com passed test Intersite
    Starting test: FsmoCheck
    Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
    A Time Server could not be located.
    The server holding the PDC role is down.
    Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355
    A Good Time Server could not be located.
    ......................... jmf.com failed test FsmoCheck

  • #2
    Re: Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355

    Can you tell us more about your environment?
    Is this the only DC?
    Have you confirmed the FSMOs are located where you think?
    Can you transfer the PDC Emulator FSMO to another DC and then back?
    Have you reviewed this: http://support.microsoft.com/kb/816042?
    Tom Jones
    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
    PhD, MSc, FIAP, MIITT
    IT Trainer / Consultant
    Ossian Ltd
    Scotland

    ** Remember to give credit where credit is due and leave reputation points where appropriate **

    Comment


    • #3
      Re: Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355

      Hi,

      There are 20 DCs in domain. I have run the command on same server which holds PDC role.
      FSMOs are correct.

      pls help

      Comment

      Working...
      X