I have an issue when attempting to logon to a domain controller while the domain controller hosting all FSMO roles is down...
The environment...1 2003 Small Business Server, 1 additional domain controller running 2003 R2 Standard, and other miscellaneous servers. Both DC's are running Active Directory Integrated DNS. Both DC's have themselves listed 1st for DNS Server in the TCP properties and the other DC listed as secondary DNS.
When the SBS is down (for reboot in this case), I am unable to logon to the other DC. I get the message that the domain can't be contacted and is unavailable. Once the other DC (hosting FSMO roles) comes back up, I can get in fine. It is my understanding I should be able to logon to the additional DC when the SBS is down...
The customer is asking me why we can't logon when the SBS is down....Is there a misconfiguration here or am I misunderstanding something about accessibility to Active Directory when the FSMO server can't be reached? If someone could clarify this for me it would be greatly appreciated...
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Check that each machine a global catalog server, go to Administrative Tools, Active Directory Sites and Services, Expand ,Sites, Default first site and Servers. Right click on the new server and select properties and tick the Global Catalog checkbox. (Global catalog is essential for logon as it needs to be queried to establish Universal Group Membership)
Assuming that you were using Active Directory Integrated DNS on the first Domain Controller, DNS will have replicated to the new domain controller along with Active Directory when you installed the second.
If you are using DHCP you should spread this across the domain controllers, In a simple single domain this is easiest done by Setting up DHCP on the second Domain controller and using a scope on the same nnetwork that does not overlap with the existing scope on the other Domain Controller. Dont forget to set the default gateway (router) and DNS Servers. and authousise the DHCP servers
The DNS settings for clients (and the domain controllers themselves) need to have their Preferred DNS server set to one domain controller, and the Alternate DNS to the other, that way if one of the DNS Servers fails, the clients will automatically use the other,
Both Domain Controllers by this point will have Active Directory, Global Catalog, DNS and DHCP. and the domain could should any one of them fail.
It sounds like your DNS SRV records didn't replicate to the member server. Look in it's DNS and make sure that there is a forward lookup zone for _msdcs.domain.local. Also make sure that with the _msdcs, _sites, _tcp and _udp SRV records are all registered within the domain.local forward lookup zone.
If they aren't, then please review this article which will describe how to use the replication monitor to keep tabs on DNS replication: http://articles.techrepubl
Jeff
TechSoEasy
Business Accounts
Answer for Membership
by: dons6718Posted on 2007-06-14 at 09:55:15ID: 19285125
If the Domain can't be connected, it is usually a Client DNS issue. Do you have the DNS of the R2 server listed as the secondary DNS in all the clients?