Announcement

Collapse
No announcement yet.

Ex.2003 DC server weekly fail

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

  • Ex.2003 DC server weekly fail

    Hi all,

    I'm having a weekly problem with my Exchange 2003 server.

    Win2003 Std. all Updates.
    Exchange2003 Std. all Updates.
    Server is also DC and DNS server.

    Every week, at some point over the weekend, the server starts failing, for want of a better word. The first sign I get, is that all mobile devices can no longer connect to the server. This also means OWA isn't available, nor is the intranet sites on that server. DNS is correct and working fine.

    DCDIAG returns an LDAP error 58: Win32 Error 58 - Machine could not be contacted due to bad net response.
    NETDIAG returns a couple of errors about Out of Memory, tho the machine has about a gig and a bit still free, NP etc all looks ok too.

    When trying to use ESM I get:
    Code:
    The server is not operational.
    Facility: Win32
    ID No: 8007203a
    Exchange System Manager
    Usually its so urgent that I just restart the server and all seems fine and then try to investigate, but that never shows any relevant errors in the logs or any indication of anything being wrong. So this time I am leaving it in its reduced state to try and troubleshoot.

    Any ideas what to look at, as I am completely stumped now on what to do next?
    James
    MCP

  • #2
    Re: Ex.2003 DC server weekly fail

    How many mailboxes are on the server? How many mobile devices? How much memory is available when this occurs? Are there any events in the Event Log? Have a look here for troubleshotting performance issues:

    http://technet.microsoft.com/en-us/l...EXCHG.65).aspx

    Comment


    • #3
      Re: Ex.2003 DC server weekly fail

      k thanks, but having looked into this further, i'm not sure its an Exchange issue, but more of a Server issue. I cannot connect to AD, getting a "network path cannot be found" error. It all kinda points to DNS, but DNS seems to be working fine... I'm sooo confused...
      James
      MCP

      Comment


      • #4
        Re: Ex.2003 DC server weekly fail

        Make sure that DNS is configured correctly.
        NO external DNS servers anywhere in the network configuration. It should be pointing to domain controllers ONLY for DNS.

        Simon.
        --
        Simon Butler
        Exchange MVP

        Blog: http://blog.sembee.co.uk/
        More Exchange Content: http://exchange.sembee.info/
        Exchange Resources List: http://exbpa.com/
        In the UK? Hire me: http://www.sembee.co.uk/

        Sembee is a registered trademark, used here with permission.

        Comment


        • #5
          Re: Ex.2003 DC server weekly fail

          I have checked and triple checked DNS. I am 99% sure it is correct.
          James
          MCP

          Comment


          • #6
            Re: Ex.2003 DC server weekly fail

            Run the best practises tool against the server.
            What does the server do at the weekend that is different to during the week?
            Anything weekly scheduled?

            Simon.
            --
            Simon Butler
            Exchange MVP

            Blog: http://blog.sembee.co.uk/
            More Exchange Content: http://exchange.sembee.info/
            Exchange Resources List: http://exbpa.com/
            In the UK? Hire me: http://www.sembee.co.uk/

            Sembee is a registered trademark, used here with permission.

            Comment


            • #7
              Re: Ex.2003 DC server weekly fail

              OK, have run the tool. What exactly should I be looking for, as all seems pretty much normal and as it was before I was having problems

              The only thing that it does different over the weekend, is be used less! We only have about 3 or 4 people in over the weekend.

              Nothing Scheduled for weekly, and it is also random times at the weekend, I think the fact it is weekend is coincidence.
              James
              MCP

              Comment


              • #8
                Re: Ex.2003 DC server weekly fail

                Perhaps you have a failing NIC or a bad driver? Is it a VM or a physical box?
                GoogleFu is strong with this one ^

                Comment


                • #9
                  Re: Ex.2003 DC server weekly fail

                  Physical box. Dell Poweredge 1800, all latest drivers applied etc.

                  Out of curiosity, what makes you think failing NIC?
                  James
                  MCP

                  Comment


                  • #10
                    Re: Ex.2003 DC server weekly fail

                    In your original post you mentioned that the server has 1GB of RAM and "a bit still free", but you didn't specifiy how much is free. If it were me I'd be looking at this link (from the link to the article in my first response):

                    http://technet.microsoft.com/en-us/l...EXCHG.65).aspx

                    Comment


                    • #11
                      Re: Ex.2003 DC server weekly fail

                      Server has 4Gb in total, with currently 1.4Gb still showing as free. Page file is currently at 3.1Gb.

                      I will look thru your article posted, tho I'm pretty sure I've already been thru it. I've been thu what feels like Hundreds now! lol
                      James
                      MCP

                      Comment


                      • #12
                        Re: Ex.2003 DC server weekly fail

                        Originally posted by swfblade View Post
                        Physical box. Dell Poweredge 1800, all latest drivers applied etc.

                        Out of curiosity, what makes you think failing NIC?

                        "Every week, at some point over the weekend, the server starts failing, for want of a better word. The first sign I get, is that all mobile devices can no longer connect to the server. This also means OWA isn't available, nor is the intranet sites on that server. DNS is correct and working fine.

                        DCDIAG returns an LDAP error 58: Win32 Error 58 - Machine could not be contacted due to bad net response."

                        From your first post it states that certain things aren't accessible over the network. Can you access OWA from the exchange server itself when this happens?

                        A failing NIC can display many different sorts of issues. But so could bad RAM. A memtest would be a good thing to do.
                        GoogleFu is strong with this one ^

                        Comment


                        • #13
                          Re: Ex.2003 DC server weekly fail

                          Another thing you can do is to run the PAL tool and see if it detects any issues:

                          http://pal.codeplex.com/

                          Comment


                          • #14
                            Re: Ex.2003 DC server weekly fail

                            thanks guys.

                            stamandster, cheers. No when it happens all Exchange features stop working, ESM, OWA, OMA.... the lot!

                            joeqwerty, thanks again, I'll give that a go.
                            James
                            MCP

                            Comment


                            • #15
                              Re: Ex.2003 DC server weekly fail

                              Did you running CHKDSK to see if there's errors where the binaries are installed?
                              GoogleFu is strong with this one ^

                              Comment

                              Working...
                              X