server 2003 - Multiple domain controllers

I am getting this message and my 2003 Server is rebooting on the hour

Multiple domain controllers running Windows Server 2003 for Small
Business Server have been detected in your domain. To prevent this
computer from shutting down in the future, you must remove all but one
of these from the domain.

How do identify the Multiple domain controllers?

I am using advance IP scanner and cant find the offending domain controller.
BrogrimInformation Systems Development ManagerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Will SzymkowskiSenior Solution ArchitectCommented:
Use the following command below...
netdom query dc

Open in new window

Also use the following below to query the FSMO role holder...

netdom query fsmo

Open in new window

Make sure that you run this from a domain controller itself. Unless you have RSAT installed on your workstation

Radhakrishnan RSenior Technical LeadCommented:

There are few places where you can check how many DC's are there in the network

1) DsQuery Server -domain or DSQUERY Server

2) nltest /

If still you unable to find the DC and would like to investigate bit more as detailed then go for metadata cleanup procedure but don't complete the process (I.e - Perform the steps 1 -11 list servers in site  and quit the process).

Hope this helps.
BrogrimInformation Systems Development ManagerAuthor Commented:
I have no idea what the above means, when i ran the command the command box only briefly appeared
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

Radhakrishnan RSenior Technical LeadCommented:

In the first command,

DsQuery Server -domain yourdomainname

Replace "yourdomainname" with your exact internal domain name.

Second command;

Just type the command in command prompt


Third one;

nltest / (Replace with your actual domain name).

Let me know if you need any clarification on this.
Will SzymkowskiSenior Solution ArchitectCommented:
You need to open the command prompt window..

Then type the commands i have illustrated

netdom query dc


netdom query fsmo

BrogrimInformation Systems Development ManagerAuthor Commented:
Thanks for the update

Are these ran in a command line or run?

1) DsQuery Server -domain or DSQUERY Server

2) nltest /

Thnaks for your patience, Im a novice.
Radhakrishnan RSenior Technical LeadCommented:

Open command prompt and run the commands :)
BrogrimInformation Systems Development ManagerAuthor Commented:
Am i bad, it is actually a 2008 Windows Server with the multiple domain controllers.
Radhakrishnan RSenior Technical LeadCommented:
Still the command valid for 2008 server as well.
Lee W, MVPTechnology and Business Process AdvisorCommented:
I'd say forget all the advice you've been given.  At some point within the last month, you added a new server to your network OR someone transferred the FSMO roles from the server that HAD been holding them to a new/different server.  Your network is small... running these commands, I think is too technical for a small environment and someone with (based on your comments so far) a skillset such as yours.

You're using SBS 2008 or SBS 2011 - you are NOT using Windows Server.  SBS has a small list of ABSOLUTE REQUIREMENTS:
1. It MUST be a Global Catalog server in AD
2. It MUST hold ALL the FSMO roles (google this if you don't know what they are).
3. It CANNOT have trusts to other domains
4. It CANNOT have more than 75 clients (hence you have a small network).

If you change it so that #1 or #2 is NOT as it should (it simply won't let you do #3) then it shuts down every hour or so.

I SUSPECT you've added a Windows Server 2012 Essentials system OR tried adding a new domain controller running 2012 and decided to transfer the FSMO roles.  Essentials systems have the SAME REQUIREMENTS - you CANNOT have an SBS Server AND an ESSENTIALS server on the same Windows domain at the same time.  (There is a grace period for migrations, but after that's over, it shuts down).

You CAN - I REPEAT - YOU CAN have other DCs and other servers, but they CANNOT be "Small Business Server" or "Essentials" servers.  They must be full versions of Windows Server 2012 (or 2008) Standard or Data Center Editions.  And if you want to make them DCs that's fine too... PROVIDED that you leave the FSMO roles on the SBS Server.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Radhakrishnan RSenior Technical LeadCommented:

I just want to say that I am disappointed with this comment  "I'd say forget all the advice you've been given".

Actually the questions was "How do identify the Multiple domain controllers?"

For that, I and Will given the correct command to identity the DC's in the network, if that is the case, how come our comment is irrelevant?

We all know you very well and you are the one of the topper in EE community. In fact, i was following you for few years  but this comment is not fair i would say personally.

We all joined EE for sharing our knowledge and helping others. If this is going to override other experts suggestion then definitely it's discouraging experts who is actively participating in EE like me.

Cris HannaSr IT Support EngineerCommented:
While you may not agree with the "tone" of Lee W's comment, he got to the heart of the matter pretty quickly.  The error the author was getting is unique to SBS environments.  And SBS has some pretty unique requirements and restrictions
Lee W, MVPTechnology and Business Process AdvisorCommented:
@Radhakrishnan Rajayyan

I'm sorry if you felt offended.  I thought I was pretty clear - I didn't say any of the prior comments were wrong, just that, in my opinion, based on my analysis of the asker's question and apparent skill level, the answers being offered were too complicated.  With significant experience and understanding of SBS the problem, in my opinion is clear as is what the answer is really going to have to be.  

A LOT of people try to answer the question as asked - I often try to answer the problem as I see it - which may not always be exactly what was asked.  And sometimes I mess up too.  I can offer solutions that miss or even ignore some key points that make my answers wrong.  

You are, as is everyone, welcome to your opinion - this was my reasoning.
Radhakrishnan RSenior Technical LeadCommented:
That's fine Lee W :)

Apologies if i said anything wrong!
BrogrimInformation Systems Development ManagerAuthor Commented:
Spot on a "skillset such as yours", beginner stuff. Thanks
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.