Announcement

Collapse
No announcement yet.

Netdiag and Dcdiag Errors

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

  • Netdiag and Dcdiag Errors

    Let me start by giving a brief overview of what we are trying to accomplish. Our current Exchange server has reach the end of its lifecycle and we would like to replace it with a completely new server along with a fresh install of Exchange and a new machine name. The old Exchange Server also acts as one of our DNS servers, and a second domain controller. The new server would assume these roles and we plan on demoting and removing the old Exchange server from the network.

    DC1 - Windows Server 2003
    DC2 - Windows Server 2003 - Current Exchange Server - Remove after 3rd DC and Exchange are stable:
    DC3 - New Exchange Server

    The new server has been built and added to the network as a third DC, adprep and forestprep went through without error. Before installing Exchange we ran NETDIAG and DCDIAG as is recommended before installing Exchange and received the following warnings/errors:

    NETDIAG:

    1. [Warning] The system volume has not been completely replicated to the local machine. This machine is not working properly as a DC.

    DCDIAG:

    1. Testing server: Default-First-Site\SWCOXXM0001
    Starting test: Replications
    REPLICATION LATENCY WARNING
    ERROR: Expected notification link is missing.
    Source CVCFILE
    Replication of new changes along this path will be delayed.
    This problem should self-correct on the next periodic sync.
    REPLICATION LATENCY WARNING
    ERROR: Expected notification link is missing.
    Source CVCMAIL
    Replication of new changes along this path will be delayed.
    This problem should self-correct on the next periodic sync.

    2. Starting test: Netlogins
    Unable to connect to the NETLOGON share! (\\DC3\netlogon)
    [DC3] An net use or LsaPolicy operation failed with error 1203,
    No network provider accepted the given network path..
    .................... DC failed test NetLogons
    3.Starting test: Advertising
    Warning: DsGetDcName returned information for \\DC1.domain,local,
    when we were trying to reach DC1.
    Server is not responding or is not considered suitable.
    .................... DC3 failed test Advertising

    Any help with clearing these errors would be greatly appreciated. Are these errors typical when adding a new DC? Will I have problems with my new Exchange install if I continue without fixing these errors?
    Thanks for your time!

  • #2
    Re: Netdiag and Dcdiag Errors

    For what its worth, MS strongly recommends you do not have Exchange on a DC
    IMHO you would be better to make your new server Exchange only (\\EX1), then decommission and rebuild your current Exchange server as a brand new DC (\\DC3)
    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: Netdiag and Dcdiag Errors

      So strongly they ship exchange with SBS

      So I guess DC1 and DC3 are using the DNS of DC2?
      Exchange 2003? SP?
      Please remember to leave positive reputation points (The Ying Yang Icon) if someone helps you.

      Comment


      • #4
        Re: Netdiag and Dcdiag Errors

        [QUOTE=']SK[;114673']So strongly they ship exchange with SBS
        [\QUOTE]

        SBS is, of course, a law unto itself!
        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

        Working...
        X