Slow Win2K network client boot since 09-16

  • Thread starter Thread starter Jack Johnson
  • Start date Start date
J

Jack Johnson

I've seen several mentions in this newsgroup of the problem of extremely
long boot times for Win2K network clients starting on September 16. A couple
of my clients are experiencing this problem, and so far I haven't been able
to determine the cause.

This is pretty puzzling, since as far as I know no updates/patches were
applied to the servers or clients in this timeframe, no changes made to DNS
or DHCP, no viruses detected, etc. I am not seeing this problem on my
in-house network.

Has anybody else come across any clues as to the source of the problem, or
better yet, a solution?

Thanks,

Jack Johnson
Cyberworlds Inc.
http://www.cyberworlds.com/
http://www.swidgets.com/
http://www.passphrasekeeper.com/
608-362-0318
 
Could it be related to Verisign changing the root DNS servers to redirect
all traffic for unregistered domain names to their SiteFinder service? If
so, then your clients are not pointing to the correct DNS server. All your
clients should be pointing to the internal DNS server ONLY (and not to the
ISP DNS servers). Then configure your DNS server to forward the queries to
the ISP DNS server.

--
Thanks.

This posting is provided "AS IS" with no warranties, and confers no rights.
OR if you wish to include a script sample in your post please add "Use of
included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm"
 
Rakesh said:
Could it be related to Verisign changing the root DNS servers to
redirect all traffic for unregistered domain names to their
SiteFinder service? If so, then your clients are not pointing to the
correct DNS server. All your clients should be pointing to the
internal DNS server ONLY (and not to the ISP DNS servers). Then
configure your DNS server to forward the queries to the ISP DNS
server.
Click to expand...
<SNIP>

That is what occurred to me this afternoon as I thought about what external
events could be affecting such widely separated networks. I'll have a chance
to check this out during a site visit this weekend. Here's hoping!
--
Jack Johnson
Cyberworlds Inc.
http://www.cyberworlds.com/
http://www.swidgets.com/
http://www.passphrasekeeper.com/
608-362-0318
 
Jack said:
<SNIP>

That is what occurred to me this afternoon as I thought about what
external events could be affecting such widely separated networks.
I'll have a chance to check this out during a site visit this
weekend. Here's hoping!
Click to expand...

Looks like that was the likely issue, since the change took place in the
same timeframe as the onset of the problem, and the affected systems were
NOT pointing at the internal DNS server! Once I reset those systems to use
DHCP (which points them at the internal forwarding DNS server) the problem
went away.
--
Jack Johnson
Cyberworlds Inc.
http://www.cyberworlds.com/
http://www.swidgets.com/
http://www.passphrasekeeper.com/
608-362-0318
 
Back
Top