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