Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top
What a load of garbage. – John Gardeniers Jul 9 '10 at 9:54
Note that forum post is from 2002, and references a Win 2000 domain. Hopefully the vast majority of people are running at least 2003 DCs, ideally with AD and DNS linked, in which case AD is resolved via straight to DNS/DHCP and workgroup just queries the local subnet. – GAThrawn Jul 13 '10 at 15:52
Please help us in building a clean knowledge base. So, don't use the answer box to comment or add details to your question. Thanks! – splattne Aug 15 '10 at 13:36
up vote 1 down vote accepted

If a workgroup and a Windows domain have the same name, and are on the same network then you'll have name resolution problems when looking for the domain.

If the names are different there shouldn't be a problem.

share|improve this answer
How so? I have a domain and a workgroup at home with the same name and have no problems. I do this so that I can browse all machines from the network. My workgroup doesn't cause problems for my domain and my domain doesn't cause problems for my workgroup. – joeqwerty Jul 9 '10 at 13:19
Yeaah, I also was in doubt because domain and workgroup names are resolved quite differently and independently – Gennady Vanin Геннадий Ванин Jul 9 '10 at 15:38
I know that there used to be master browser issues because the machines in the workgroup could try and take over as the master browser for the domain. This may have been fixed by name. With a small domain you may not see the problems if they haven't been fixed by Microsoft. – mrdenny Jul 9 '10 at 23:52

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.