none
Cannot ping DC RRS feed

  • Question

  • Dear All,

    I have a very strange issue with my Exchange 2010 Server and Windows Server 2003 DC.

    Currently, we have 1 DC(PDC) damaged with motherboard burn-out. We have assigned another Windows Server 2003 DC to take over the PDC FSMO role with seized. However, the Exchange 2010 Server is being unstable after the PDC damaged. Sometimes, it cannot open EMC and cannot ping the new PDC for about 5-10mins, and then it can open EMC and ping the new PDC again. However, all the clients can ping all the DC and Exchange Server at anytime.

    Anyone have ideas about this strange case? Thank you very much.

    Wednesday, December 29, 2010 3:47 AM

Answers

  • Make sure Exchange is pointing to the new DC.  Did you transfer all FSMO roles to this new DC?  How many DCs do you have?  Please run Netdom Query FMSO command and post the result here.

     

    Also, please post the IPCONFIG/ALL result from your DC and Exchange here. 


    Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX

    Blogs - http://blogs.sivarajan.com/
    Articles - http://www.sivarajan.com/publications.html
    Twitter: @santhosh_sivara - http://twitter.com/santhosh_sivara

    This posting is provided AS IS with no warranties, and confers no rights.
    • Marked as answer by Bruce-Liu Friday, February 4, 2011 9:35 AM
    Wednesday, December 29, 2010 4:59 AM
    Moderator
  • Be sure DNS host records are configured with the correct IP addresses. As Awinish indicated in a reply, be sure the Exchange server is pointing to the current PDC's IP address ONLY for DNS via network interface card TCP/IP settings.

    Be sure that atleast one of the exisiting domain controllers are configured as a global catologe server.

    Have you verified the Windows firewall or security/AV software settings on the PDC are not filtering the ICMP Echo Reply? Also, be sure to check that packet filtering is not enabled on network interface card settings.

     

    • Marked as answer by Bruce-Liu Friday, February 4, 2011 9:36 AM
    Thursday, December 30, 2010 3:47 AM

All replies

  • Make sure Exchange is pointing to the new DC.  Did you transfer all FSMO roles to this new DC?  How many DCs do you have?  Please run Netdom Query FMSO command and post the result here.

     

    Also, please post the IPCONFIG/ALL result from your DC and Exchange here. 


    Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX

    Blogs - http://blogs.sivarajan.com/
    Articles - http://www.sivarajan.com/publications.html
    Twitter: @santhosh_sivara - http://twitter.com/santhosh_sivara

    This posting is provided AS IS with no warranties, and confers no rights.
    • Marked as answer by Bruce-Liu Friday, February 4, 2011 9:35 AM
    Wednesday, December 29, 2010 4:59 AM
    Moderator
  • Could this dc be a multihomed DC?

    As already requested please post an ipconfig /all for the DC.

     

    --
    Paul Bergson
    MVP - Directory Services
    MCITP: Enterprise Administrator
    MCTS, MCT, MCSE, MCSA, Security+, BS CSci
    2008, Vista, 2003, 2000 (Early Achiever), NT4
    http://www.pbbergs.com    Twitter @pbbergs

    Please no e-mails, any questions should be posted in the NewsGroup This
    posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, December 29, 2010 5:14 AM
    Moderator
  • Did you check the event viewer of any error events on exchange as well as on DC?

    Did you change the dns address in Exchanger server to point to working domain controller as primary address.

    Did you make other DC as GC too?

     

    This posting is provided AS IS with no warranties, and confers no rights.


    Awinish Vishwakarma | TA - DS/Exchange
    Wednesday, December 29, 2010 8:43 AM
    Moderator
  • Be sure DNS host records are configured with the correct IP addresses. As Awinish indicated in a reply, be sure the Exchange server is pointing to the current PDC's IP address ONLY for DNS via network interface card TCP/IP settings.

    Be sure that atleast one of the exisiting domain controllers are configured as a global catologe server.

    Have you verified the Windows firewall or security/AV software settings on the PDC are not filtering the ICMP Echo Reply? Also, be sure to check that packet filtering is not enabled on network interface card settings.

     

    • Marked as answer by Bruce-Liu Friday, February 4, 2011 9:36 AM
    Thursday, December 30, 2010 3:47 AM
  • You can give a try to reset TCP/IP stack & i have seen many times issues with corruption in tcp stack, resetting solves the issue.

     

    http://support.microsoft.com/kb/299357


    Awinish Vishwakarma | TA - DS/Exchange
    Thursday, December 30, 2010 3:52 AM
    Moderator
  • Hello,

    make sure the other DC is also Global catalog server, Exchange MUST have at least one available GC. Also make sure DNS servers are available. As already requested please post the output from "netdom query fsmo" and the ipconfig /all from the DC and the Exchange server.

    Which SP is installed on the Windows server 2003 DC, minimum requirement is SP1?


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Thursday, December 30, 2010 11:56 AM