very slow boot / logons when w2k/XP clients configured to logon to domain

[Hal Turnage]

Apparently I am missing something fundamental. This is my
scenario:

1. I have a Windows server setup as a domain controller.
I have tried this on W2k and W2k3. I have taken DNS and
DHCP off.

2. I have broadband run into office and use router for
DHCP.

3. Windows 98 clients no problem.

4. Windows 2k clients with static IP and have no internet
access no problem.

5. Windows 2k or XP Pro clients which receive IP from
router but try to logon to domain are very slow to logon
to network. On 1 W2k client it takes 40 min. to boot and
logon to network. Clients sits on "applying personal
settings" for a very long time. XP client takes at least
2-3 minutes.

6. I have not been able to find much information but here
are some of the things I tried.
a) Installing WINS on server
b) create forward lookups after enabling DNS on server
c) regedt32 add netlogon dependent on DNS

Any help would be greatly appreciated. I have been
pulling my hair for days on this one.


Hal Turnage

 

[Guest]

Have you tried to add the Servers IP address and server
name in the host file of the PC that is hanging?

 

[Lakshman]

On your server, have you enable forwarders on DNS to the
DNS address of your ISP?
On the Xp Machines set the DNS address to be that of the
server(your DC).Youcan either use static IPs and set the
DNS to be that of the server or use the DHCP on the server
not the router.In your scope options make sure you specify
the DNS to address to be assigned to be that of the
server.hope this helps.
Lakshman.