Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Do not switch to the second DC
- Thread starter azzurri
- Start date
How many GCs do you have?
Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
If this is secondary DC is not a global catalog also then your users will not be able to logon. Go to AD Sites and Services, click on the second DC. On the right hand of the screen, right click on NTDS settings and ensure that the Global Catalog is checked and click on OK. Hope this helps.
- Thread starter
- #4
- Thread starter
- #5
What errors do clients get when they try to log on after the first DC 'crashed'?
Is DNS running on the second DC?
Do you use DHCP? What DNS addresses are you handing out via DHCP?
Anything in the event logs on the second DC?
Paul
MCSE 2003
"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein
- Thread starter
- #7
Errors: the clients cannot login or if they are already logged in they cannot use outlook, and so on
DNS is running on the second DC
We use DHCP for clients only ( of course)
Events logs on second DC ? not really
I can log in locally on the "crashed" DC but I do not see the rest of the network, I must reboot the server
regards
azzurri
DNS is running on the second DC
We use DHCP for clients only ( of course)
Events logs on second DC ? not really
I can log in locally on the "crashed" DC but I do not see the rest of the network, I must reboot the server
regards
azzurri
- Thread starter
- #8
sorry I've found something.....
The File Replication Service is having trouble enabling replication from DCCHLA07 to DCCHLA04 for c:\winnt\sysvol\domain using the DNS name dcchla07.INDUSTRIE.AMMANN.INTRA. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name dcchla07.INDUSTRIE.AMMANN.INTRA from this computer.
[2] FRS is not running on dcchla07.INDUSTRIE.AMMANN.INTRA.
[3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that
The DCCHLA07 is the "crash" W2K3 DC
The DCCHLA04 is the second DC, W2K
azzurri
The File Replication Service is having trouble enabling replication from DCCHLA07 to DCCHLA04 for c:\winnt\sysvol\domain using the DNS name dcchla07.INDUSTRIE.AMMANN.INTRA. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name dcchla07.INDUSTRIE.AMMANN.INTRA from this computer.
[2] FRS is not running on dcchla07.INDUSTRIE.AMMANN.INTRA.
[3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that
The DCCHLA07 is the "crash" W2K3 DC
The DCCHLA04 is the second DC, W2K
azzurri
Check that the File Replication service is running on both DCs
Check you can ping each server from the other one by its dns name?
Paul
MCSE 2003
"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein
Check you can ping each server from the other one by its dns name?
Paul
MCSE 2003
"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein
- Thread starter
- #10
- Status
Similar threads
- Locked
- Question
- Locked
- Question