Announcement

Collapse
No announcement yet.

W2K users log on wrong DC

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

  • W2K users log on wrong DC

    Hi,

    All of my users logs on the wrong DC (the backup one) I know the concept on PDC and BDC do not exist anymore in W2K. But here is the case...

    ServerA = DC/AD, Exchange 2000, DNS, WINS ans DHCP
    ServerB = DC/AD, Backup software
    ServerC = member server (File/Print)

    We have installed the ServerB as DC/AD backup and run the backup software on it. This serveur is turning slow something due to the high Disk/Tape access.

    All users are authenfying on the ServerB all the time and it should be on ServerA. When backups run the uses are not able to log on the domain due to slow response of ServerB.

    I did verify the Browser and the 3 servers are Master Browser.

    Ran NetDiag and DSdiag and everything looks fine!

    Regards

    Anormand

  • #2
    Hi all,

    Here some mores details.....

    After changing the priority on the DNS Default Sites MSDC. ServerA to 0 and ServerB to 1. The DNS add itself entries for ServerB to 0....

    This morning running usrstat to find out where user get authenticated.
    33 were on serverA
    23 were on serverB

    In addition to all these one user didn't get the script run. But I found he was authenticated on both server at the same time 08:49:05.

    If you have any ideas or suggestion it will be really appreciated before I depromote serverB and dcpromote a ServerC to see if the problem persist.

    Regards

    Comment


    • #3
      clients chooses self to which DC they will connect...
      i thought it works on who is the first DC that responded...

      so you can't control it, like you requested it.
      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


      • #4
        Thanks Marcel,

        What I do not understand is one client authenticated on both server at the same times. Also the serverB seams to hand on RPC sometimes, ex. when I use ComputerManager to connect too it doesn't respond same thing for TS or Wins service. But I may able to ping it and browse its shares, so I am unable to use the shutdowngui to restart the server remotely.

        I really think to depromote this server from the domain and promote another one!

        Regards,

        anormand

        Comment


        • #5
          Are both DCs also GCs ?
          Do you have more than one subnet ?
          Do you have more than one site configured in AD Sites&Services ?
          Guy Teverovsky
          "Smith & Wesson - the original point and click interface"

          Comment


          • #6
            Are more details about my config....

            ServerA and ServerB are DC
            ServerA is GC
            Only one subnet
            Only one Site (Default-First-Site-Name)

            4 Servers all W2K SP4 updated (2 DC, 2 Members)
            2 Unix (NT4 Members)
            10 printers
            75 workstations (15xWin98, 40xW2kPro, 20xWinXPPro)
            1 Linux Proxy (DNS, Proxy, Squid, Firewall)
            1 HP Procurve switch serie 53xx

            All servers are Gigabits, all printers and static IP, all Wrks are DHCP.

            Regards

            anormand

            Comment


            • #7
              Hi all,

              My ServerB is running Brightstore ArcServe for all servers backup. It's also the DC "backup". With all the problem I have I seriously think of unpromoting this serverB.

              Here is my plan (because everything I tried didn't solve it and I have no errors in the replication but some problems like TS hanging).

              1a. Unpromote the ServerB to be a simple Member Server with Backup software.
              1b. Uninstall WINS, DNS from it
              1c. Wait a day or two to see if everything looks good and better
              2a. Install a good small serveur class computer as a ServerF
              2b. ServerF, install as backup WINS and backup DNS
              2c. Promote ServerF as DC

              What do you think of the "solution", any other suggestions are welcome.

              Thanks all

              anormand
              Canada

              Comment


              • #8
                Make the second DC a GC too.
                When client logs on, it has to contact not only a DC, but also a GC, hence all your clients go the the only GC in the AD.
                Guy Teverovsky
                "Smith & Wesson - the original point and click interface"

                Comment


                • #9
                  Hi Guyt,

                  Good suggestion but before granting the GC to ServerB. I did an additional test here the result.

                  After restarting ServerB everybody logs on ServerB (for 2 days in a row) and nobody on ServerA which is the DC/GC domain master running Exchange2000.

                  With this result it seams the ServerA do not respond in a respectable timeframe and let the "backup" DC do the job. But after a while the ServerB is on it seams to be slower to respond everyday causing users to logs on both servers.

                  My opinion is:

                  ServerA do not respond in a respectable timeframe due Exchange2000.
                  ServerB do not perform well with the new release of BrightStore 11.1.
                  ServerF may resolve the issue by have a role of DC/GC only!

                  Do you have more ideas or suggestions?

                  Regards,

                  ANormand
                  Canada

                  Comment


                  • #10
                    ...... I forgot this point.... The Wins Entries are completly different between the to servers, and they are replication partner. ServerB pull from ServerA and ServerA push to ServerB

                    ServerA 192.168.75.11
                    ServerB 192.168.75.12

                    ServerA (WINS Active Registration)
                    Workgroup 192.168.75.204 (Workstation, ComputerBrowser Off)
                    Domain Master Browser 192.168.75.11
                    Domain Controler 192.168.75.11
                    Normal Group Name 192.168.75.115 (Workstation, ComputerBrowser Off)

                    ServerB (WINS Active Registration)
                    Workgroup 192.168.75.12
                    Domain Master Browser 192.168.75.11
                    Domain Controler 192.168.75.12
                    Normal Group Name 192.168.75.113 (Workstation, ComputerBrowser Off)

                    Comment


                    • #11
                      ......... Is just restarted the WINS Service on ServerA:

                      Looking better here after the restart:

                      ServerA (WINS Active Registration)
                      Workgroup 192.168.75.11
                      Domain Master Browser 192.168.75.11
                      Domain Controler 192.168.75.11
                      Normal Group Name 192.168.75.11

                      Looking strange 5 minutes after:

                      ServerA (WINS Active Registration)
                      Workgroup 192.168.75.13 (File and Print Server, ComputerBrowserOn)
                      Domain Master Browser 192.168.75.11
                      Domain Controler 192.168.75.11
                      Normal Group Name 192.168.75.11


                      ServerB didn't change yet!

                      Comment

                      Working...
                      X