Win2k taking a long time to logon to new Win2k domain

[Guest]

Hi,
I've just offloaded all DHCP duties to my new Win2k domain DC.
I still have the old NT4 PDC running as backup DHCP.

I've added my laptop to the domain. When I logon, it takes over a couple
of minutes.... Is this a DNS issue?

What is it?

Thanks,

Do

 

[Do]

Hi:

So for every machine that is pointing to other wrong DNS servers,
it will affect the login process of one client machine that is using the
correct DNS server from
DHCP? And make it lag by a couple minutes?

What's going on in the background? Do you have any articles I can read on
this?

Do

"Ace Fekay [MVP]"

 

[Kevin D. Goodknecht Sr. [MVP]]

In

Hi:

So for every machine that is pointing to other wrong DNS servers,
it will affect the login process of one client machine that is using
the correct DNS server from
DHCP? And make it lag by a couple minutes?

What's going on in the background? Do you have any articles I can
read on this?

Here's a little FAQ on AD and DNS:
http://support.microsoft.com/?id=291382&FR=1

 

[Ace Fekay [MVP]]

More than likely it is a DNS issue. In AD, you MUST point to the internal
DNS only. No others. NT4 doesn;t support AD either. Make sure ALL internal
AD machines (DCs & Clients) point only to the internal DNS server hosting
the AD domain name.

If you want efficient Internet resolution, use a Forwarder. If the
Forwarding option is grayed out, delete the Root zone. This article shows
how to do both:
http://support.microsoft.com/?id=300202

More info on AD and it's DNS realiance:
http://support.microsoft.com/?id=291382

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory