Announcement

Collapse
No announcement yet.

Slow logon on Win2k Server BDC when PDC is down

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

  • Slow logon on Win2k Server BDC when PDC is down

    Hi!

    We have a pretty peculiar issue as we are running an AD with 2 Win2k Servers (PDC and BDC).

    Whenever the PDC is offline (shut-down) and the BDC is the only server running we should (to my understanding) still be able to use the network as always.

    However, when we try to log on from workstations (WinXPsp2) the username and passwords are verified correctly but the logon takes VERY long time. It says "Loading computer settings" and then stalls for some 5 min. After that everything works ok.

    We have shared the DHCP pool over both servers. PDC is using 10.0.0.20 - 10.0.0.49 and BDC is using 10.0.0.50 - 10.0.0.80.

    What could be the reason for this "stall"??

  • #2
    Do you have DNS configured on the second DC ?
    Is the second DC also a GC ?
    Guy Teverovsky
    "Smith & Wesson - the original point and click interface"

    Comment


    • #3
      Originally posted by Guy (Antid0t)
      Do you have DNS configured on the second DC ?
      Is the second DC also a GC ?
      No, DNS is not configured... Should it be the same as the PDC?
      No, the BDC is not a GC.

      Comment


      • #4
        well both answers are given now..

        make the other DC also a DNS service (as a secondary or Ad integrated) and make him also a GC.
        Marcel
        Technical Consultant
        Netherlands
        http://www.phetios.com
        http://blog.nessus.nl

        MCITP(EA, SA), MCSA/E 2003:Security, CCNA, SNAF, DCUCI, CCSA/E/E+ (R60), VCP4/5, NCDA, NCIE - SAN, NCIE - BR, EMCPE
        "No matter how secure, there is always the human factor."

        "Enjoy life today, tomorrow may never come."
        "If you're going through hell, keep going. ~Winston Churchill"

        Comment


        • #5
          Originally posted by Dumber
          well both answers are given now..

          make the other DC also a DNS service (as a secondary or Ad integrated) and make him also a GC.
          The GC has been installed.
          What do you mean by "(as a secondary or Ad integrated)"? Should I install it so it looks similar to the PDC?

          Comment


          • #6
            Don't exactly know for sure what I did but it's working great now.
            I will try to document it at place it here as I think more people might need this.

            Should be here in a few days or so.

            Comment


            • #7
              well you already have installed you're other dns service so, is it installed as primary or ad integrated?
              Marcel
              Technical Consultant
              Netherlands
              http://www.phetios.com
              http://blog.nessus.nl

              MCITP(EA, SA), MCSA/E 2003:Security, CCNA, SNAF, DCUCI, CCSA/E/E+ (R60), VCP4/5, NCDA, NCIE - SAN, NCIE - BR, EMCPE
              "No matter how secure, there is always the human factor."

              "Enjoy life today, tomorrow may never come."
              "If you're going through hell, keep going. ~Winston Churchill"

              Comment


              • #8
                FYI - In Win2K AD and higher, DCs are no longer PDCs or BDCs. They are all pretty much equal with exception to their roles and/or services.

                Make sure both DCs are both Global Catalogs and DNS servers and you should not have a problem. Also, make sure the NetLogon service is functioning without errors.

                Comment


                • #9
                  Thank goodness that someone has pointed out 'There is no PDC/BDC on Win2k and above'. There are so many people using those terms in this context. Worrying.
                  Server 2000 MCP
                  Development: ASP, ASP.Net, PHP, VB, VB.Net, MySQL, MSSQL - Check out my blog http://tonyyeb.blogspot.com

                  ** Remember to give credit where credit is due and leave reputation points sigpic where appropriate **

                  Comment

                  Working...
                  X