Large Delay logging on Windows XP Pro

[Dave]

I have a Windows 2000 server with about 5 Windows XP Pro
workstations. On all the workstations, it takes a number
of minutes to log into the network. I have confirmed the
DNS/DHCP as well as network cabling and switch. It seems
to take about 3-10 minutes to log in from a reboot. If
the system sits idle for number of hours (like overnight)
the network becomes unresponsive and requires a reboot.
The server and workstations have reciently been re-format
and re-installed fresh copies of the OS's. Any help would
be greatly appreciated. Thanks!

-- Dave

 

[Ron Lowe]

I have a Windows 2000 server with about 5 Windows XP Pro
workstations. On all the workstations, it takes a number
of minutes to log into the network. I have confirmed the
DNS/DHCP as well as network cabling and switch. It seems
to take about 3-10 minutes to log in from a reboot. If
the system sits idle for number of hours (like overnight)
the network becomes unresponsive and requires a reboot.
The server and workstations have reciently been re-format
and re-installed fresh copies of the OS's. Any help would
be greatly appreciated. Thanks!

-- Dave

What have you confirmed about the DNS?
It needs to point to the server, not an ISP.
Does it?

This is almost always a DNS issue.

Please check your DNS configuration as follows:
XP differs from previous versions of windows in that it uses
DNS as it's primary name resolution method for finding domain
controllers:

How Domain Controllers Are Located in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314861

If DNS is misconfigured, XP will spend a lot of time waiting for it to
timeout before it tries using legacy NT4 sytle NetBIOS.
( Which may or may not work. )

1) Ensure that the XP clients are all configured to point to the local
DNS server which hosts the AD domain. That will probably be the
win2k server itself.
They should NOT be pointing an an ISP's DNS server.
An 'ipconfig /all' on the XP box should reveal ONLY the domain's
DNS server.

( you should use the DHCP server to push out the local DNS server
address. )

2) Ensure DNS server on win2k is configured to permit dynamic updates.

3) Ensure the win2k server points to itself as a DNS server.

4) For external ( internet ) name resolution, specify your ISP's DNS server
not on the clients, but in the 'forwarders' tab of the local win2k DNS
server.

On the DNS server, if you cannot access the 'Forwarders' and 'Root Hints'
tabs because they are greyed out, that is because there is a root zone (".")
present on the DNS server. You MUST delete this root zone to permit the
server to forward unresolved queries to yout ISP or the root servers.
Accept any nags etc, and let it delete any corresponding reverse lookuop
zones if it asks.


The following articles may assist you in setting up DNS correctly:

Setting Up the Domain Name System for Active Directory
http://support.microsoft.com/default.aspx?scid=kb;en-us;237675
HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202

 

[Guest]

What have you confirmed about the DNS?

It needs to point to the server, not an ISP.
Does it?

Yes.. The only DNS server on the network ins the domain
controller, and the DHCP server is pushing out that DNS
server only. I had previously had the primary DNS being
the ISP until I learned how to configure forwarders on
the primary AD controller. I believe this to be a DNS
issue as well, but for the life of me, I couldn't pin-
point it.. I will go over the links you provided and see
if it turns up some additional information.. Thank you
kindly for your time.


-- Dave