Have DNS on the second DC then.
Actually, yes they can, but I needed to sort out the DNS on the clients first(as our primary dns was also on the server that failed).Originally Posted by Grommit
Have DNS on the second DC then.
I've never suceeded in getting users to log onto the network when the main DC fails no matter what I do the roles. The second DC is functioning fine, just seems reluctant to take on any of the roles when the otherone's not available.
I see our second DC as more of a 'live backup' of our main one, that will need a bit of tweeking to bring it online in an emergency. Our network manages fine with 1 DC doing all the work.
i have this issue tooOriginally Posted by maniac
however our other dc is a different domian (ADMIN DOMIAN)
the circ domian has only on DC and is the dhcp server for the two domians.
The two servers have zone transfer setup but when the circ server goes down them admin users cannot login. (our circ server is now 6 years old and supporting twice the number of clients too)
It's active directory. You have DNS on ALL domain controllers. DNS is how ADOriginally Posted by FN-Greatermanchester
replication is held together.
But you have to install DNS on the second domain controller it isn't installed by default.
I agree... but I hear people saying the reson for having 2 or more Domain Controllers so that if the a DC falls over the others will take it's place...Originally Posted by projector1
Yet I have never been able to get another DC to take it's place..
How come Ranger gets installed on 2 DCs so that if one falls over the other will allow users to log on... yet it never seems to work..
My 3 DCs have AD, DNS, Printing roles installed..
You also need a split DHCP really.
We've been through this before at some stage and I remember actually testing it during the holidays. You can log on if the Global Catalogue is missing, so the most important thing (from the client point of view) is to have a DNS server and a DHCP server available.
Yep as long as you have a backup DNS and your clients point towards it you should be able to log on fine. That's why there is a secondary DNS field on the clients network configs.
You also have to think about things like DHCP, Wins and in our case the global policies all couldn't be edited so we had to recreate those which took a few hours.
The SYSVOL folder is supposed to be replicated so its worth checking that on your backup server as well.
SYSVOL, NETLOGON and AD are the main three that are replicated.
Make sure any logon scripts/profiles etc that point to your main DC use the %logonserver% variable instead of a path to the main DC. EG a logon script in NETLOGON folder may be set as \\LOGON1\\NETLOGON\Script1.bat when it's best to use %logonserver%\NETLOGON\Script1.bat since it will obviously not work if LOGON1 is down. Using this variable means that it will pull it from whichever server your user is logged into at the time.
Our machines seem to be spilt roughly down the middle as to which they log into. I'm not sure how it does this but it seems to spread the load quite well.
We have 2 DCs and we recently tested our setup by pulling the network lead from DC1 to see if things were working OK (after school I hasten to add). All we had to do was log off then back on again to pick up all the replicated stuff (re-directed menus etc).
We have DNS on both the DCs and the second part of a split DHCP scope on DC2. I also keep all of the DHCP reservations in a Netsh dump file for easy import if I need it.
I don't think you really need DHCP redundancy, when we lost ours it only took 5 mins to setup from scratch again.
Agreed - hence the script to import the settings.Originally Posted by ittech
you could always have it installed and set-up but only active on one server (DHCP that is).
I have DHCP across three servers with each server dishing out a third of each subnet's IP addresses.
The three Domain Controllers also have DNS and the server roles split between them.
Two of the servers have WINS and two have NPS.
It works fine and I can easily take a server down for updates, etc.
However, we did have an issue a while back that trashed Active Directory - so I used it as an oportunity to completely rebuild AD from scratch (up until then it had just "evolved" over a few years)
There are currently 1 users browsing this thread. (0 members and 1 guests)