XP Boots Fast, But Logs On Really Slow

  • Thread starter Thread starter Bobby
  • Start date Start date
B

Bobby

Hi there,

I'll be quick and straight to the point with as much detail as possible so
this does not become a long email. We have a Win2K domain here. We've got
several XP and Win2K clients on the domain. Recently a new HP NW series
laptop was purchased with XP Pro on it. Default factory software was left
on the laptop. The laptop was not wiped clean (at one point I was
considering wiping clean the laptop and starting fresh as this may very well
be the root of my problem). The laptop has two mapped network drives (one
to the domain controller and one to our terminal file server). The laptop
has a built in wireless NIC and bluetooth adapter. Both can be
enabled/disabled with a touch of a button. Laptop obtains IP address
automatically as it goes to several differet sites to access internet, both
wired and wireless. Now whenever this user logs on, the boot up is fast
HOWEVER, as he is about to enter his credentials XP takes its "sweet time"
which is approximately 5-8 minutes just sitting there. After that he can go
ahead and enter his credentials and can use the computer normally. Now let
me stress that this happens both ON and OFF the network, whether it's at the
office, at home, in the park, at the mall...etc...you get the idea now. A
short term temporary fix will not float my boat as this laptop user is very
critical and can not have absolutely any down time (which is impossible, but
it has to be kept to a strict minimum).

Any help would be much appreciated.

Thanks in advance,

Bobby
 
In
Bobby said:
Hi there,

I'll be quick and straight to the point with as much detail as
possible so this does not become a long email. We have a Win2K
domain here. We've got several XP and Win2K clients on the domain.
Recently a new HP NW series laptop was purchased with XP Pro on it.
Default factory software was left on the laptop. The laptop was not
wiped clean (at one point I was considering wiping clean the laptop
and starting fresh as this may very well be the root of my problem).
The laptop has two mapped network drives (one to the domain
controller and one to our terminal file server). The laptop has a
built in wireless NIC and bluetooth adapter. Both can be
enabled/disabled with a touch of a button. Laptop obtains IP address
automatically as it goes to several differet sites to access
internet, both wired and wireless. Now whenever this user logs on,
the boot up is fast HOWEVER, as he is about to enter his credentials
XP takes its "sweet time" which is approximately 5-8 minutes just
sitting there. After that he can go ahead and enter his credentials
and can use the computer normally. Now let me stress that this
happens both ON and OFF the network, whether it's at the office, at
home, in the park, at the mall...etc...you get the idea now. A short
term temporary fix will not float my boat as this laptop user is very
critical and can not have absolutely any down time (which is
impossible, but it has to be kept to a strict minimum).

Any help would be much appreciated.

Thanks in advance,

Bobby

What do you see in the event logs?
 
Bobby, I would definitely check the Event logs. In addition to that I
would run msconfig from the Run prompt. In here you can see everything
that happens during startup. Microsoft was pretty slick with Windows
XP, they allow a fast boot but most services start during your logon.
If you have many items in the Startup tab that don't necessarily have
to be running then that could be your problem.

Good Luck,

John
 
Hi everyone,

I apologize for taking so long to update this posting. I haven't had access
to the laptop in question for a while now. I did look at the event viewer
and well discovered several events. Keep in mind this is all happening even
though the laptop is set to obtain an IP address dynamically. Here are the
event IDs discovered in the application log only, slowdowns not only
occurred during the logon but also whilst the computer is running (briefly
though):

ERROR - event ID 1054: DNS server unreachable or not valid. Domain
controller could not be located

ERROR - event ID 15: automatic certificate enrollment for local system
failed to contact the active directory. the specidified domain either does
not exisr or could not be contacted. enrollment will not be performed

WARNING - event ID 11165: system failed to register hosta (a) resource
records (RRs) for network adapter...

ERROR - event ID 29: the time provider NtpClient is configured to acquire
time from one or more time sources, however none of the sources are
currently accessible. no attempt to contact a source will be made for 14
minutes...

These are some of the events that I think are relevant to the situation
here. If anyone can come up with suggestions or remedies that would be
greatful. I've tried Msconfig and that isn't of much help in this situation
(I know it can be very helpful at times though).

Thanks in advance,

Bobby
 
It sounds like the laptop is configured for the wrong DNS server or a
firewall is blocking access to the DNS server.

Kerry
 
But this only happens when the laptop is off site (out of office areas) such
as at someone's house, or a cafe, or wherever it may be and regardless if it
is wireless or not. Would it still be the same conclusion?

Bobby
 
Bobby said:
But this only happens when the laptop is off site (out of office
areas) such as at someone's house, or a cafe, or wherever it may be
and regardless if it is wireless or not. Would it still be the same
conclusion?

Bobby

This is different information from your original post. You originally said
it happened at the office as well. Misconfigured DNS problems usually show
up as a long pause during "Applying network settings" before you get the
logon prompt. The errors in the logs however point to a DNS problem. This
makes me believe it may be a problem with a firewall or some other program
or service that starts up after logon.

Check the TCP/IP settings and see if there is a manually configured DNS
server. Is the laptop using a 3rd party firewall or the XP SP2 firewall?
From msconfig try a diagnostic startup or try safe mode with networking and
see what happens.

Kerry
 
Kerry,

When the DNS is configured manually, but IP is set to be obtained
automatically then there are no logon problems whatsoever (since it finds
the DNS server and resolves). This does not help when the user leaves the
office and tries to connect to a network outside because then they would
have to remove the DNS configuration and set it to automatic (this would not
be a problem for someone who is computer savvy, such is not the case
unfortunately). So let's say DNS config is set to automatic, that is when
the logon problems occur (i.e. right when it's saying applying network
settings or even when it's done that and it asks you to enter credentials).

The laptop does have XP SP2 Firewall enabled. I thought it was disabled as
last time I was the one who disabled it. However, I will try what you
recommended, disabling the XP native firewall, safe mode with networking and
a diagnostic startup using Msconfig. I'll post an update soon.

Thanks

Bobby
 
Bobby said:
Kerry,

When the DNS is configured manually, but IP is set to be obtained
automatically then there are no logon problems whatsoever (since it
finds the DNS server and resolves). This does not help when the user

When configured for DHCP at the office does it get the same DNS server as
you configure it manually?
leaves the office and tries to connect to a network outside because
then they would have to remove the DNS configuration and set it to
automatic (this would not be a problem for someone who is computer
savvy, such is not the case unfortunately). So let's say DNS config
is set to automatic, that is when the logon problems occur (i.e.
right when it's saying applying network settings or even when it's
done that and it asks you to enter credentials).

OK this is different yet again from your other posts.
The laptop does have XP SP2 Firewall enabled. I thought it was
disabled as last time I was the one who disabled it. However, I will
try what you recommended, disabling the XP native firewall, safe mode
with networking and a diagnostic startup using Msconfig. I'll post
an update soon.

Let us know hat happens.

Kerry
 
Back
Top