S
Steele
I have a newer Windows XP laptop that works fine when it is in the office
and connected to the LAN. When the user takes the laptop at home, they log
in as their domain user account, which is cached.
There is a great deal of hesitation when the laptop is connected to the home
network. The CPU is normal, and the mouse responds fine, but there is often
an agonizing delay between trying to open something and when it responds.
For example, many times, if the user clicks on the Start button, they will
have to wait 45 seconds or so before the start menu will appear.
This problem does not occur at the office at all.
This problem does not occur on the home network IF the laptop is connected
to the office network through VPN.
This problem does not occur on the home network IF all of the network cards
are turned off.
This problem does not occur on the home network IF the user is logged on as
a local user instead of a cached domain user.
This problem does not occur for any other identical laptops for other users.
It almost seems like the laptop is attempting to contact the domain
resources for something, although I cannot find what. Does anyone have any
thoughts on what may be happening or how to track this down?
Many thanks.
and connected to the LAN. When the user takes the laptop at home, they log
in as their domain user account, which is cached.
There is a great deal of hesitation when the laptop is connected to the home
network. The CPU is normal, and the mouse responds fine, but there is often
an agonizing delay between trying to open something and when it responds.
For example, many times, if the user clicks on the Start button, they will
have to wait 45 seconds or so before the start menu will appear.
This problem does not occur at the office at all.
This problem does not occur on the home network IF the laptop is connected
to the office network through VPN.
This problem does not occur on the home network IF all of the network cards
are turned off.
This problem does not occur on the home network IF the user is logged on as
a local user instead of a cached domain user.
This problem does not occur for any other identical laptops for other users.
It almost seems like the laptop is attempting to contact the domain
resources for something, although I cannot find what. Does anyone have any
thoughts on what may be happening or how to track this down?
Many thanks.