Re: clients are registered with different domain name
Hi:
Actually it is transaltion in regard when the proper domain name is not
reachable. I can join client to domain but when it is joined some computers
get xxxxx.cm and some xxxx.com. I have checked the primary dns suffix on all
some .cm and some .com.
actually answer is clear how shall i change all my DCs and workstations to
one domain name which is .com.
I did chage primary dns suffix of one DCs than that stop replication and
many more errors.
thanks
--
Essa
"Harvey Colwell" wrote:
> You have confused me. It must be something in the translation.
>
> You can not join a client to a "domain" xxxxxx.cm, unlesss a DC exists in
> that domain.
>
> They would not try to register in the xxxxxx.cm zone unless they have a
> "Primary Dns Suffix" or a "Connection Speciffic Dns Suffix" of xxxxxx.cm.
>
> How many DCs are there?
>
> Have you checked the "Primary Dns Suffix" on each one?
>
>
>
>
> "Muhammad Essa" <MuhammadEssa@discussions.microsoft.com> wrote in message
> news:254FF0D7-6F1D-41D8-8EDA-CEA16A16A352@microsoft.com...
> > Hi
> > Once again thanks for reply.
> > As additional domain is created so it copies or replicated with its
> > primary
> > doamin controller so here addtional domains cannot be promoted, only while
> > creating child or secondary those can be promoted with different domain
> > names. The problem is from the date when the doamin is created the
> > information in DHCP is correct. From first day it was slow for the users
> > and
> > some of the users were joined as xxxxx.com and some of them as xxxxx.cm so
> > after creating the .cm forward lookup zone in DNS the problem of being
> > slow
> > is solved and now when additional domain are registered after replication
> > there DNS entries most of them are .cm such as A recored etc. And even
> > some
> > of them cannot be recongized itself by the primary domain becuase it
> > cannot
> > initiat replication even right after replication is finished and new
> > additional domain is created. So there is no question of any DC promoted
> > with
> > wrong domain name and if i delete the .cm forward lookup zone i need to
> > demote all the additional DCs and recreate them. The TCP/IP settings for
> > some are xxxxx.com and for some xxxxx.cm.
> > So this is the story which made me confused.
> >
> > thanks
> > --
> > Essa
>
>
>
|