AD namespace problem?

  • Thread starter Thread starter Ryan Birkenholz
  • Start date Start date
R

Ryan Birkenholz

I'm having problems with my AD not working. Is it because I have a dyjoined
namespace? I ran 'set userd' and it returned:
Userdnsdomain = PROASU.COM
Userdomain = PRO-ASU

Do these two values have to be the same and might that be what is causing my
problem with the AD telling me no authority could be found? Any solutions?
 
Hi Ryan,

Remember that every Domain will have two different names. One will be the
Fully Qualified Domain Name (as PROASU.com) and the other will be the
NetBIOS name of the Domain (as PRO-ASU). This is not a bad thing and when
properly registered, you should be able to ping them both (showing
resolution in the DNS).

As mentioned before by Paul, you can have different DNS domains than your AD
Domains. These are often the same due to the strong tie between AD and DNS
but they needn't be. In this case, don't confuse should be with must be.

If you are having AD problems, dollars to doughnuts its a DNS problem --
though, from what you've posted, nothing looks necessarily amiss.

You have asked some very specific questions but, maybe we've had our
propeller beanies on too tight and should have asked you a better question.
What problems are you seeing with your AD implementation to make you ask
these questions and what specific errors are you getting in your event logs?

Are you showing problems in DCDiag, Netdiag, and replmon?

What does your environment look like?? One server? One domain? 200 sites
with several child domains?
 
Back
Top