+ Post New Thread
Results 1 to 9 of 9
Windows Server 2000/2003 Thread, BDC online but clients dont use it. in Technical; I finally added a Backup Domain Controller yesterday. I've got to be missing a step though. When I take down ...
  1. #1
    jmair's Avatar
    Join Date
    Aug 2007
    Posts
    274
    Thank Post
    58
    Thanked 9 Times in 9 Posts
    Rep Power
    16

    BDC online but clients dont use it.

    I finally added a Backup Domain Controller yesterday. I've got to be missing a step though. When I take down my primary Domain Controller (restart or just unplug the cat5) users can't log onto the domain.

    Other than adding the secondary domain controller to the network, is the something I need to do afterwords in order for it to be recognized by on the domain so clients can log in?
    (I've checked the both DCs and have seen that the records swap and that both servers are domain controllers.. or it appears to be that way anyhow.)

    I'll be happy to provide any info to help solve this little problem.. Thanks!

  2. #2
    ezzauk's Avatar
    Join Date
    Jul 2007
    Location
    Redditch
    Posts
    109
    Thank Post
    18
    Thanked 9 Times in 9 Posts
    Rep Power
    17
    Have you made the BDC a Global Catalog?

  3. #3
    jmair's Avatar
    Join Date
    Aug 2007
    Posts
    274
    Thank Post
    58
    Thanked 9 Times in 9 Posts
    Rep Power
    16
    NOPE! I'll look that up now.. and thank yuo for the quick reply!

  4. #4
    TheLibrarian
    Guest
    Ensure that it is listed as a DNS server in the DHCP options.

    If you only have the primary server as a DNS server and it goes missing...

  5. #5
    jmair's Avatar
    Join Date
    Aug 2007
    Posts
    274
    Thank Post
    58
    Thanked 9 Times in 9 Posts
    Rep Power
    16
    Global catalogue -CHECK
    DHCP and DNS Installed - CHECK
    DNS Replication - CHECK
    Able to see both servers from both servers in AD Sites/Services and DHCP (scope identical to primary dns)

    Still when I unplug the Primary DNS, clients cannot log into the domain. Shouldn't the BDC just take over transparently? I know I'm missing something, any ideas other ideas?

  6. #6

    ZeroHour's Avatar
    Join Date
    Dec 2005
    Location
    Edinburgh, Scotland
    Posts
    5,641
    Thank Post
    894
    Thanked 1,314 Times in 798 Posts
    Blog Entries
    1
    Rep Power
    444
    One thing to consider is that you can only run one instance of DHCP generally so you never really have a fail over option. If thats on your PDC and you reboot a PC it wont get dns ip's or anything really which would break it. To get around this at our end our DHCP is a clustered service in windows 2008 r2.

  7. Thanks to ZeroHour from:

    jmair (1st June 2010)

  8. #7
    jmair's Avatar
    Join Date
    Aug 2007
    Posts
    274
    Thank Post
    58
    Thanked 9 Times in 9 Posts
    Rep Power
    16
    I have to take the PCD down to make some serious changes, and to clean the dusty beast. What would you suggest to have the network functional while the PDC is offline?

  9. #8

    ZeroHour's Avatar
    Join Date
    Dec 2005
    Location
    Edinburgh, Scotland
    Posts
    5,641
    Thank Post
    894
    Thanked 1,314 Times in 798 Posts
    Blog Entries
    1
    Rep Power
    444
    I would probably move DHCP for now as per: How to move a DHCP database from a computer that is running Windows NT Server 4.0, Windows 2000, or Windows Server 2003 to a computer that is running Windows Server 2003 and then test the network then and if it all works continue with your maintenance. As for dead PDC situations you will have more pain then which is why we clustered the service.

  10. #9

    glennda's Avatar
    Join Date
    Jun 2009
    Location
    Sussex
    Posts
    7,799
    Thank Post
    272
    Thanked 1,134 Times in 1,030 Posts
    Rep Power
    349
    Quote Originally Posted by ZeroHour View Post
    One thing to consider is that you can only run one instance of DHCP generally so you never really have a fail over option. If thats on your PDC and you reboot a PC it wont get dns ip's or anything really which would break it. To get around this at our end our DHCP is a clustered service in windows 2008 r2.
    not sure if its the same with 2008 but we have two seperate DHCP servers and have no problems, aslong as you don't have the two servers giving out the same addresses for example my range is as follows 192.168.114.1 - 192.168.124.254. server one leases 114.1 to 119.255 and server 2 leases 120.1 to 124.254.

    in your dns ensure there is a record that says something "same as parent folder" with the address of the domain controller and the same for the secondary dc.

    aslong as the clients have the dns settings of the bdc you should be able to ping domainname.local which should resolve to either of your domain controllers
    Last edited by glennda; 1st June 2010 at 06:21 PM.

SHARE:
+ Post New Thread

Similar Threads

  1. Dont know who to vote for?
    By kevbaz in forum General Chat
    Replies: 10
    Last Post: 28th April 2010, 10:13 PM
  2. Dont like this sound of this...
    By Gatt in forum BSF
    Replies: 8
    Last Post: 21st February 2010, 06:00 PM
  3. Setting up a new DC and demoting the old un to BDC
    By speckytecky in forum Windows
    Replies: 6
    Last Post: 19th February 2008, 11:35 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •