- Strange logon problem, takes minutes to logon to Windows XP SP2
- Posted by Bash on January 18th, 2006
Hi All,
Since last week I have 2 computers in my organization that suddenly takes up
to 5 minutes before the user is logged on. Everything looks fine when the
computer boots and the user logs on and it just sits there applying the
computer settings. I opened a ping to the computers and get a request timed
out the whole time until all of a sudden (after minutes) I get a reply and
the user finally logs on and can get to work.
We found a work around by disabling the “Network Location Awareness (NLA)”
service. If we do that everything looks fine. But this is not a solution
because we need that service for our group policies.
Anybody seen this behavior before?
Thanks
BasH
- Posted by Katrina on January 18th, 2006
If you log in to those computers as somebody else, does it have the same
delay? If not, re-create the user profiles that have the delay.
--
Katrina
"Bash" wrote:
- Posted by Bash on January 18th, 2006
I logged on with my domain account but by then we applied the workaround so
the logon went smoothly and quick, when I enabled the Network Location
Awareness service again and rebooted I tried it again as myself and it took
many minutes again. I forgot to mention that if these machines boot without a
network cable plugged in I can logon normal (quick) with cashed credentials.
I am clueless…..
Thanks
BasH
"Katrina" wrote:
- Posted by Chip1035 on March 31st, 2006
I have the same issue. After either reboot or power on, logon's with any
user takes 2-5 minutes to pass the login screen. When network cable is
disconnected, login goes right in, same as if the network adaptor is disabled.
I found that the system is trying to retrieve an IP address from the DHCP
server. That is causing the delay. Static IP does the same thing, pauses
2-5 minutes tring to just connect to the server.
Is there a way to have the system log right in while looking for an IP?
Tried a full format/reload, bare minimum Windows and only the network
drivers, same thing.
Drivers updated, even tried old drivers.
--
-Chip
=)
"Bash" wrote: