Hi:
Since i have created domain controller where name is xxxxx.com but when i
join computer to domain those are registered as xxxxx.cm and when users login
it takes much time to intiate login session. Then i created a new forward
lookup zone with xxxxx.cm now users can login properly. Now additional doamin
controller and computer all are registered some times as xxxxx.com and some
of them as xxxxx.cm. I can't delete the later created lookup zone becuase it
will create many problems.I really don't understand how to solve this
problem, i searched in many microsoft documents i was unable to find any
thing. If any one have understood the question and have idea please guide me
through.

Thanks
--
Essa

You have a type-o in either the manual configuration or the DHCP
configuration for the PC's default Domain Name. It's taking so long to log
on because DNS has to time out looking for the wrong domain (xxxxxx.cm).
Change the .cm to .com in the appropriate location.

Manual Config
System Properties
"Computer Name" Tab
"Change" Button
"More" Button
"Primary DNS Suffix of this Computer" Text Box

DHCP
SCOPE Options (Could be Server Options or Reservation Options)
Option "015 DNS Domain Name"

"Muhammad Essa" <MuhammadEssa@discussions.microsoft.com> wrote in message
news1F795D4-1B1B-4471-BC44-A5B2C90FC894@microsoft.com...
> Hi:
> Since i have created domain controller where name is xxxxx.com but when
> i
> join computer to domain those are registered as xxxxx.cm and when users
> login
> it takes much time to intiate login session. Then i created a new forward
> lookup zone with xxxxx.cm now users can login properly. Now additional
> doamin
> controller and computer all are registered some times as xxxxx.com and
> some
> of them as xxxxx.cm. I can't delete the later created lookup zone becuase
> it
> will create many problems.I really don't understand how to solve this
> problem, i searched in many microsoft documents i was unable to find any
> thing. If any one have understood the question and have idea please guide
> me
> through.
>
> Thanks
> --
> Essa

Hi:
Thanks for reply. I followed the steps and these mentioned steps were
followed before as well now the main problem is with additional domain
controllers where primary AD recognize some of them as .cm and some of them
as .com ( Registered as ). How to solve the problem from the root so this may
not occur next time. But from the initail point before creating another
forward lookup zone.How a domain can pickup wrong domain name?

thanks
--
Essa


"Harvey Colwell" wrote:

> You have a type-o in either the manual configuration or the DHCP
> configuration for the PC's default Domain Name. It's taking so long to log
> on because DNS has to time out looking for the wrong domain (xxxxxx.cm).
> Change the .cm to .com in the appropriate location.
>
> Manual Config
> System Properties
> "Computer Name" Tab
> "Change" Button
> "More" Button
> "Primary DNS Suffix of this Computer" Text Box
>
> DHCP
> SCOPE Options (Could be Server Options or Reservation Options)
> Option "015 DNS Domain Name"
>
> "Muhammad Essa" <MuhammadEssa@discussions.microsoft.com> wrote in message
> news1F795D4-1B1B-4471-BC44-A5B2C90FC894@microsoft.com...
> > Hi:
> > Since i have created domain controller where name is xxxxx.com but when
> > i
> > join computer to domain those are registered as xxxxx.cm and when users
> > login
> > it takes much time to intiate login session. Then i created a new forward
> > lookup zone with xxxxx.cm now users can login properly. Now additional
> > doamin
> > controller and computer all are registered some times as xxxxx.com and
> > some
> > of them as xxxxx.cm. I can't delete the later created lookup zone becuase
> > it
> > will create many problems.I really don't understand how to solve this
> > problem, i searched in many microsoft documents i was unable to find any
> > thing. If any one have understood the question and have idea please guide
> > me
> > through.
> >
> > Thanks
> > --
> > Essa
>
>
>

Muhammad Essa wrote:
> Hi:
> Thanks for reply. I followed the steps and these mentioned steps
> were followed before as well now the main problem is with additional
> domain controllers where primary AD recognize some of them as .cm and
> some of them as .com ( Registered as ). How to solve the problem from
> the root so this may not occur next time. But from the initail point
> before creating another forward lookup zone.How a domain can pickup
> wrong domain name?
>
> thanks
>
>> You have a type-o in either the manual configuration or the DHCP
>> configuration for the PC's default Domain Name. It's taking so long
>> to log on because DNS has to time out looking for the wrong domain
>> (xxxxxx.cm). Change the .cm to .com in the appropriate location.
>>
>> Manual Config
>> System Properties
>> "Computer Name" Tab
>> "Change" Button
>> "More" Button
>> "Primary DNS Suffix of this Computer" Text Box
>>
>> DHCP
>> SCOPE Options (Could be Server Options or Reservation Options)
>> Option "015 DNS Domain Name"
>>
>> "Muhammad Essa" <MuhammadEssa@discussions.microsoft.com> wrote in
>> message news1F795D4-1B1B-4471-BC44-A5B2C90FC894@microsoft.com...
>>> Hi:
>>> Since i have created domain controller where name is xxxxx.com
>>> but when i
>>> join computer to domain those are registered as xxxxx.cm and when
>>> users login
>>> it takes much time to intiate login session. Then i created a new
>>> forward lookup zone with xxxxx.cm now users can login properly. Now
>>> additional doamin
>>> controller and computer all are registered some times as xxxxx.com
>>> and some
>>> of them as xxxxx.cm. I can't delete the later created lookup zone
>>> becuase it
>>> will create many problems.I really don't understand how to solve
>>> this problem, i searched in many microsoft documents i was unable
>>> to find any thing. If any one have understood the question and have
>>> idea please guide me
>>> through.

Post the ipconfig /all from the DC and the AD domain name in ADU&C.
(unedited)

--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This s
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oe.com/OEBackup/Default.aspx
===================================

If I understand you correctly, it sounds like one or more domain controllers
were promoted into the xxxxxx.cm domain. I find this hard to believe, since
the same type-o would have to have been entered several times (while
promoting the DC(s) and while joining the PC(s) to the domain). I think that
DHCP is the much more likely culprit.

Questions:
What is your AD topology?
How many trees are in the AD forest?
How many domains/sudomains are in each tree?

----------
For now I'm going to assume that you have a single AD domain. Therefore, you
should be dealing with only one AD domain name.

Questions:
Is your AD domain name the same as your Internet domain name (i.e. email
address)?
How many DCs do you have?

Check the TCP/IP configuration on each DC (ipconfig /all).
What is the "Primary Dns Suffix" for the active /connected NIC?

I re-read your original post. So there is a xxxxxx.cm forward look up zone
on your DNS servers. Therefore, you must have accidentally promoted one or
more DCs into this domain. Once these DCs are found, and demoted, you will
be able to delete the xxxxxx.cm forward lookup zone.

If you find any DCs that have been promoted into xxxxxx.cm domain, you need
to demote them., verify their "Primary DNS Suffix of this Computer" setting,
and then re-promote them into the xxxxxx.com domain.




"Muhammad Essa" <MuhammadEssa@discussions.microsoft.com> wrote in message
news:BD6A1A64-6CE5-4D42-82FE-27F0D9CFE8AE@microsoft.com...
> Hi:
> Thanks for reply. I followed the steps and these mentioned steps were
> followed before as well now the main problem is with additional domain
> controllers where primary AD recognize some of them as .cm and some of
> them
> as .com ( Registered as ). How to solve the problem from the root so this
> may
> not occur next time. But from the initail point before creating another
> forward lookup zone.How a domain can pickup wrong domain name?
>
> thanks
> --
> Essa

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


"Harvey Colwell" wrote:

> If I understand you correctly, it sounds like one or more domain controllers
> were promoted into the xxxxxx.cm domain. I find this hard to believe, since
> the same type-o would have to have been entered several times (while
> promoting the DC(s) and while joining the PC(s) to the domain). I think that
> DHCP is the much more likely culprit.
>
> Questions:
> What is your AD topology?
> How many trees are in the AD forest?
> How many domains/sudomains are in each tree?
>
> ----------
> For now I'm going to assume that you have a single AD domain. Therefore, you
> should be dealing with only one AD domain name.
>
> Questions:
> Is your AD domain name the same as your Internet domain name (i.e. email
> address)?
> How many DCs do you have?
>
> Check the TCP/IP configuration on each DC (ipconfig /all).
> What is the "Primary Dns Suffix" for the active /connected NIC?
>
> I re-read your original post. So there is a xxxxxx.cm forward look up zone
> on your DNS servers. Therefore, you must have accidentally promoted one or
> more DCs into this domain. Once these DCs are found, and demoted, you will
> be able to delete the xxxxxx.cm forward lookup zone.
>
> If you find any DCs that have been promoted into xxxxxx.cm domain, you need
> to demote them., verify their "Primary DNS Suffix of this Computer" setting,
> and then re-promote them into the xxxxxx.com domain.
>
>
>
>
> "Muhammad Essa" <MuhammadEssa@discussions.microsoft.com> wrote in message
> news:BD6A1A64-6CE5-4D42-82FE-27F0D9CFE8AE@microsoft.com...
> > Hi:
> > Thanks for reply. I followed the steps and these mentioned steps were
> > followed before as well now the main problem is with additional domain
> > controllers where primary AD recognize some of them as .cm and some of
> > them
> > as .com ( Registered as ). How to solve the problem from the root so this
> > may
> > not occur next time. But from the initail point before creating another
> > forward lookup zone.How a domain can pickup wrong domain name?
> >
> > thanks
> > --
> > Essa
>
>
>

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

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
>
>
>

I still don't know how many DCs you have. So I can't judge how big of a
problem this is and how serious of a problem the solution will be.

You must find the affected DCs and demote them. There's no simple fix such
as using ADSIEdit to weed out this mistake from AD.

I actually encountered this problem once before. I was migrating a customer
from a Windows NT domain to a Windows 2000 AD domain. In the process they
wanted to changed the internal DNS name that they had been using. I forgot
to change the "Primary Dns Suffix" on a couple of servers that later became
DCs, It was quite a mess. I had to demote them, change the "Primary Dns
Suffix", then re-promote them. If there was a simpler solution, I never
found it.


"Muhammad Essa" <MuhammadEssa@discussions.microsoft.com> wrote in message
news:B0766C15-3271-4D6C-9F91-D14E5962CE3F@microsoft.com...
> 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
>>
>>
>>

HI:
I have more than ten DCs and the problem is not becuase of new DCs
created after primary DC , it is since the primary DCs is created. So there
is no need to demote any DC.
--
Essa


"Harvey Colwell" wrote:

> I still don't know how many DCs you have. So I can't judge how big of a
> problem this is and how serious of a problem the solution will be.
>
> You must find the affected DCs and demote them. There's no simple fix such
> as using ADSIEdit to weed out this mistake from AD.
>
> I actually encountered this problem once before. I was migrating a customer
> from a Windows NT domain to a Windows 2000 AD domain. In the process they
> wanted to changed the internal DNS name that they had been using. I forgot
> to change the "Primary Dns Suffix" on a couple of servers that later became
> DCs, It was quite a mess. I had to demote them, change the "Primary Dns
> Suffix", then re-promote them. If there was a simpler solution, I never
> found it.
>
>
> "Muhammad Essa" <MuhammadEssa@discussions.microsoft.com> wrote in message
> news:B0766C15-3271-4D6C-9F91-D14E5962CE3F@microsoft.com...
> > 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
> >>
> >>
> >>
>
>
>