Announcement

Collapse
No announcement yet.

No GC? Cant Find Domain Controller? What the deuce?

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

  • No GC? Cant Find Domain Controller? What the deuce?

    Ok. I've looked hi and low for an actual answer.

    I have two sites.
    Site1 and Site2 and one domain connected via VPN.

    Site1 has SBS2008 (Exchange 2008 SP3 Rollup 3v2) (Vader), and a Windows Server 2008 R2 DC (Yoda) (2008 functionality)
    Site2 has a DC and Exchange 2008 (Chewbacca).

    Sites are configured properly, dcdiag /e give me nothing untoward.

    SITE1 (Head Office)
    Vader, being SBS is a DC with all the roles. Yet in exchange, it cant see itself. It can only see Yoda. If Yoda goes down, Vader dies.

    SITE2 (Remote Office)
    Chewbacca is a DC and Exchange 2007 SP3 Rollup 3v2 (I know I'm naughty installing Exchange on a DC) can only see Vader and Yoda for the DC and GC roles.

    Chewbacca is an SCR server in case the head office goes down. But if the office disappeared of the planet, then Exchange would surely fall over..
    What am I missing?
    All DNS Settings are correct. all servers are DNS Servers, and point to themselves first, and then to the other two DNS Servers/DCs.


    Some info that might help.

    From Vader!!!
    Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=4252). Exchange Active Directory Provider has discovered the following servers with the following characteristics:
    (Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)
    In-site:
    VADER.xxxxxxxx.local CDG 1 0 0 1 0 0 0 0 0
    yoda.xxxxxxxxxxxx.local CDG 1 7 7 1 0 1 1 7 1
    Out-of-site:
    CHEWBACCA.xxxxxxxxxxx.local CDG 1 7 7 1 0 1 1 7 1

    From Chewbacca!!!

    Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=500. Exchange Active Directory Provider has discovered the following servers with the following characteristics:
    (Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)
    In-site:
    chewbacca.xxxxxx.local CDG 1 0 0 1 0 0 0 0 0
    Out-of-site:
    VADER.xxxxxx.local CD- 1 6 7 0 0 1 1 7 1
    yoda.xxxxx.local CD- 1 6 7 0 0 1 1 7 1
    Please help..
    Thanks..
    Attached Files

  • #2
    Re: No GC? Cant Find Domain Controller? What the deuce?

    Having Exchange on a domain controller is probably the cause of the problem. Exchange only uses itself when it is installed on a domain controller and that goes for all other Exchange servers in the org as well. I think that is causing your problems.

    Getting Exchange off the domain controller in the second site is going to be the only option. Note I said take Exchange off, not remove the DC functionality. Running DCPROMO on a server with Exchange installed is not supported and usually breaks Exchange.

    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


    • #3
      Re: No GC? Cant Find Domain Controller? What the deuce?

      Thanks Sembee.
      What about the SBS2008 Exchange server unable to see itself?

      Comment


      • #4
        Re: No GC? Cant Find Domain Controller? What the deuce?

        As I have said, that is almost certainly because you have Exchange on another domain controller. Exchange does funny things in that scenario, which is why it isn't a recommended configuration, except for SBS, which is primarily designed as a single box solution.

        If you were to take Exchange off the domain controller in the second location, then that Exchange server will use the SBS server exclusively, even if that means coming across a WAN. Lose the WAN and that second Exchange server would be dead in the water.

        The bottom line is that if you want to run multiple Exchange servers in separate offices you should really be using full product on member servers.

        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: No GC? Cant Find Domain Controller? What the deuce?

          Exchange on the SBS 2008 server couldn't see itself after I did a rollup, not when I installed an Exchange server in another office..
          Ignoring the exchange server in the 2nd office; why cant exchange on the SBS server it itself for AD configuration etc...

          Comment


          • #6
            Re: No GC? Cant Find Domain Controller? What the deuce?

            Originally posted by ikenga View Post
            Exchange on the SBS 2008 server couldn't see itself after I did a rollup, not when I installed an Exchange server in another office..
            Ignoring the exchange server in the 2nd office; why cant exchange on the SBS server it itself for AD configuration etc...
            You can't ignore the server in the second office because it is running Exchange on a domain controller. That is the cause of your problems.

            What happened in the past doesn't mean it was working correctly. It is probably down to the way that you patched the servers, which caused the domain controller the Exchange org is using to change because the version numbers changed.

            The ONLY way to get things to work in a predictable manner is to move Exchange off that domain controller. It has to be done that way, running DCPROMO on an Exchange server is not supported and usually breaks Exchange.

            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: No GC? Cant Find Domain Controller? What the deuce?

              But understand my logic. Exchange on the SBS server couldnt see itself even before I installed a DC, and Exchange in the other office!

              And what other way is there to patch other than Windows Update..

              REINSTALL cant be the answer.. "AN" answer, maybe, but not "THE" answer..

              Comment


              • #8
                Re: No GC? Cant Find Domain Controller? What the deuce?

                If Exchange can't use a domain controller it is dead in the water.
                Therefore presuming that Exchange was working then you were mistaken.
                Now if Exchange wasn't working then you have a more serious problem, but if Exchange wasn't working then I would doubt that you would have been able to install the second server correctly.

                You may well have reached the point where your only option is to speak to Microsoft support, as they can look at the server setups and may well be able to see something that you cannot.
                You may well have a configuration that shouldn't be working, but for some reason is.

                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


                • #9
                  Re: No GC? Cant Find Domain Controller? What the deuce?

                  Well, thank god I didn't listen, and did a little more digging. THANKS GOOGLE!
                  Turns out that Exchange needs IPv6 active on the NIC..
                  All working beautifully now! And ecstatic customer; we dont have to rebuild the systems! WoopWoop.
                  http://blogs.technet.com/b/sbs/archi...-sbs-2008.aspx

                  Comment

                  Working...
                  X