Announcement

Collapse
No announcement yet.

"preparing network connections" is too slow

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

  • "preparing network connections" is too slow

    I study Domain Controller and Cluster via virtual machine VMWare:
    - Create 2 VMWare servers Windows 2003
    - Install Active Directory as new domain controller in Node 1
    - IP/DefaultGateway/DNS Node1 is 192.168.1.101/192.168.1.101/null
    - Install Active Directory as addition domain controller of Node 1 in Node 2
    - IP/DefaultGateway/DNS Node2 is 192.168.1.102/192.168.1.101/192.168.1.101
    - After that I install Cluster for 2 Nodes

    The problem is when I restart server, step "preparing network connections" is too slow

    Please help me
    Thanks

  • #2
    Re: "preparing network connections" is too slow

    How slow is "slow"?
    What are your hardware specs (Physical and Virtual)?

    Are you saying you created two separate domain controllers and then clustered them?
    Reading some of the links here http://www.google.co.uk/search?hl=en...meta=&aq=f&oq= suggests clustering DCs is not a good idea (but not impossible)
    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: "preparing network connections" is too slow

      Originally posted by Ossian View Post
      How slow is "slow"?
      What are your hardware specs (Physical and Virtual)?

      Are you saying you created two separate domain controllers and then clustered them?
      Reading some of the links here http://www.google.co.uk/search?hl=en...meta=&aq=f&oq= suggests clustering DCs is not a good idea (but not impossible)
      Dear Ossian

      I mean "slow" is very longtime than Windows without DC before. I create one DC for 2 servers, same role Domain Controller

      Then I create Cluster for 2 Nodes

      Comment


      • #4
        Re: "preparing network connections" is too slow

        Yes, but what is "very long time"?
        Years? Hours?
        "Slow" is relative so for some 10 seconds is too slow, for others a few minutes is fine
        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


        • #5
          Re: "preparing network connections" is too slow

          Originally posted by thang_ngo_2002 View Post
          I study Domain Controller and Cluster via virtual machine VMWare:
          - Create 2 VMWare servers Windows 2003
          - Install Active Directory as new domain controller in Node 1
          - IP/DefaultGateway/DNS Node1 is 192.168.1.101/192.168.1.101/null
          - Install Active Directory as addition domain controller of Node 1 in Node 2
          - IP/DefaultGateway/DNS Node2 is 192.168.1.102/192.168.1.101/192.168.1.101
          - After that I install Cluster for 2 Nodes

          The problem is when I restart server, step "preparing network connections" is too slow

          Please help me
          Thanks
          Rebooting a DC can sometimes be slow and as Ossian mentions, an idea of time would be good. The hardware you have installed the VMs on will also be a factor, especially the memory allocated to the VMs.

          Comment


          • #6
            Re: "preparing network connections" is too slow

            The virtual Hardware is: 1G RAM, CPU Dual core 2.5G, 5G HDD

            Before install AD, this server restarts during 3-5 min.
            After install AD, this server restarts during 10-15 min.

            Comment


            • #7
              Re: "preparing network connections" is too slow

              Did you happen to notice how long it took to restart with AD but before clustering?

              What is the physical hardware?

              Anything unusual in event logs?
              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


              • #8
                Re: "preparing network connections" is too slow

                Apologies if I'm missing the comment somewhere but what AD domain is it? For example, I don't think 5GB is enough space for a w2k8 one.

                Comment


                • #9
                  Re: "preparing network connections" is too slow

                  When the first DC boots on the domain and there are no other DC's it always takes a very long time to get the point when you can login. The DC is looking to make sure it's the master browser. It get's compounded when it's clustered.

                  This should give you some idea on what's going on with the authentication portion, it's possible that's slowing it down.

                  http://technet.microsoft.com/en-us/l...12(WS.10).aspx
                  Last edited by stamandster; 27th May 2009, 15:05.
                  GoogleFu is strong with this one ^

                  Comment


                  • #10
                    Re: "preparing network connections" is too slow

                    @Ossian:
                    Physical hardware is CPU Dual core 2.5G, 4GRAM, HDD 500G
                    The event log of DNS Directory Service is:
                    Active Directory could not resolve the following DNS host name of the source domain controller to an IP address. This error prevents additions, deletions and changes in Active Directory from replicating between one or more domain controllers in the forest. Security groups, group policy, users and computers and their passwords will be inconsistent between domain controllers until this error is resolved, potentially affecting logon authentication and access to network resources.

                    @Virtual: I use Win2003, more over I already increase from 5G to 8G

                    @stamandster: I think it's reasonable, and I'll try to read your article

                    Comment


                    • #11
                      Re: "preparing network connections" is too slow

                      Try and set the Netlogon service to wait for DNS to startup. It's possible that's whats screwing it up.

                      HKLM\System\CurrentControlSet\Services\Netlogon
                      Key Name = DependOnService
                      Type = Reg_Multi_SZ
                      Value =
                      LanmanWorkstation
                      LanmanServer
                      DNS
                      GoogleFu is strong with this one ^

                      Comment


                      • #12
                        Re: "preparing network connections" is too slow

                        I changed registry as your idea but it is not better

                        Comment


                        • #13
                          Re: "preparing network connections" is too slow

                          Can you time it to let us know how long exactly it takes to get to the login screen?
                          GoogleFu is strong with this one ^

                          Comment


                          • #14
                            Re: "preparing network connections" is too slow

                            This screen shows nearly 10 min.

                            Comment


                            • #15
                              Re: "preparing network connections" is too slow

                              That's actually not too bad for the first DC of a domain to startup.
                              GoogleFu is strong with this one ^

                              Comment

                              Working...
                              X