15-Min Logon

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

I have a problem with one of my client PCs, it has Windows 2000, and my
server is windows 2003. The strange thing is that the client of windows 2000
it tkaes exactly 15-mins to log on, with any password, be this admin, or a
user I created.

Any ideas, I have tried with the same password on other clients and got no
problems. Also all there info and docs, etc. is stored on each machine not on
the server. And restrictions on to what they can enter is unlimited, so there
should be no problem, but it still takes 15 min on that especific machine.

Any help would be nice. Thank you.
 
I would check the DNS settings first. It is better to use an internald DNS instead of ISP DNS.

windows slow issues Slow file write from win2k to NT 4 server Slow logon to windows domain ... Slow opening Windows explorer. Q: When I logon my laptop with domain account at ...
www.chicagotech.net/winslow.htm


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Hi,

I have a problem with one of my client PCs, it has Windows 2000, and my
server is windows 2003. The strange thing is that the client of windows 2000
it tkaes exactly 15-mins to log on, with any password, be this admin, or a
user I created.

Any ideas, I have tried with the same password on other clients and got no
problems. Also all there info and docs, etc. is stored on each machine not on
the server. And restrictions on to what they can enter is unlimited, so there
should be no problem, but it still takes 15 min on that especific machine.

Any help would be nice. Thank you.
 
In
Robert L said:
I would check the DNS settings first. It is better to use an
internald DNS instead of ISP DNS.

In fact, if you want AD to run properly, you *have* to do it that way
(internal DNS server IPs only).
 
This is virtually always misconfigured DNS on either the server or the
client end.

....kurt
 
Hello,

I've encountered this issue a couple times for machines built for the
domain. I've not found an exact cause or fix, but a quick workaround is
to remove the NIC in Device Manager and reboot to allow PnP to add back
the NIC (I've not always had same level of success adding it back
without a reboot). I've not noticed this to be a chronic issue.

- Steve H
 
Back
Top