Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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

Is it possible to join domains via FQDN rather than the Netbios name? Reason I ask is that with netbios character limit of 15, we have two hosts with the same netbios shortened name. Meaning we can join one computer to the domain, but if we join the second it overwrites the computer account of the first.

Any ideas? Will disabling Netbios on all computers allow you to join an AD domain and have its computer account associated with it's FQDN?


share|improve this question
up vote 4 down vote accepted

No, unfortunately - as far as I'm aware, uniqueness in a Computer account's NetBIOS name is absolutely enforced, regardless of whether or not you're actually using NetBIOS at all.

This is because, like user accounts, the sAMAccountName attribute of the object (which for computers contains the NetBIOS name) must be unique in the domain.

share|improve this answer
Thanks knew there must have been something else relying on it. Maybe we can hope for this to be included in Windows 2024 :) – floyd Oct 24 '12 at 19:32
@floyd And, because it's not mentioned in Shane's answer, the sAMAccountName attribute is what's often actually used when applying certain domain settings and policies to computer objects. Because using the account's UID would make too much sense, or something. So even if you could get around it, you wouldn't want to, because one of those computers would not be properly treated by the domain anyhow. – HopelessN00b Oct 24 '12 at 20:00

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.