[jm78]

We have several notebooks (XP SP2) that are all members of our domain. The
people who use them use domain user accounts to login to the notebooks. When
these notebooks are used in the office login takes no time at all and the
notebooks basically respond as our workstations do.

Whenever these notebooks have a "non-corporate LAN" network connection (ie.
wireless at home, etc) connected before initial login, XP hangs for ~90
seconds before displaying the desktop and icons.

With the network connection disabled or unplugged, login takes less than 20
seconds.

Does anyone know of a way in Windows to decrease this delay?

Thanks

[Chuck]

On Tue, 21 Jun 2005 08:23:09 -0700, "jm78" <jm78@discussions.microsoft.com>
wrote:

>We have several notebooks (XP SP2) that are all members of our domain. The
>people who use them use domain user accounts to login to the notebooks. When
>these notebooks are used in the office login takes no time at all and the
>notebooks basically respond as our workstations do.
>
>Whenever these notebooks have a "non-corporate LAN" network connection (ie.
>wireless at home, etc) connected before initial login, XP hangs for ~90
>seconds before displaying the desktop and icons.
>
>With the network connection disabled or unplugged, login takes less than 20
>seconds.
>
>Does anyone know of a way in Windows to decrease this delay?
>
>Thanks

Windows XP uses DNS for name resolution, and will work best in a domain that's
setup for that. Domains setup to support older versions of Windows, and home
workgroups, work differently.
<http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html>

Check for gratuitous protocols, that will cause excessive network traffic, too.
<http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not a problem - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.

[jm78]

Thanks for the response but our DNS server is setup like you suggest on your
site and we only use the essential protocols for network connection on our
workstations and notebooks.

The problem is really when the notebooks have a network connection that is
not our corporate LAN at initial login. XP sits for ~90 seconds, I believe
looking for our domain (which it can't because the notebook isn't connected
to it).

I would like to find a way to decrease this timeout period at login.


"Chuck" wrote:
>
> Windows XP uses DNS for name resolution, and will work best in a domain that's
> setup for that. Domains setup to support older versions of Windows, and home
> workgroups, work differently.
> <http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html>
>
> Check for gratuitous protocols, that will cause excessive network traffic, too.
> <http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
>
> --
> Cheers,
> Chuck
> http://nitecruzr.blogspot.com/
> Paranoia is not a problem - it's a normal response from experience.
> My email is AT DOT
> actual address pchuck sonic net.

[Chuck]

On Tue, 21 Jun 2005 08:55:01 -0700, "jm78" <jm78@discussions.microsoft.com>
wrote:

>"Chuck" wrote:
>>
>> Windows XP uses DNS for name resolution, and will work best in a domain that's
>> setup for that. Domains setup to support older versions of Windows, and home
>> workgroups, work differently.
>> <http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html>
>>
>> Check for gratuitous protocols, that will cause excessive network traffic, too.
>> <http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>

>Thanks for the response but our DNS server is setup like you suggest on your
>site and we only use the essential protocols for network connection on our
>workstations and notebooks.
>
>The problem is really when the notebooks have a network connection that is
>not our corporate LAN at initial login. XP sits for ~90 seconds, I believe
>looking for our domain (which it can't because the notebook isn't connected
>to it).
>
>I would like to find a way to decrease this timeout period at login.

AFAIK, not all timings in Windows come with an adjustable time period. Maybe
you will find a useful adjustment in here:
<http://support.microsoft.com/?id=314053>

If there is a registry key involved, you might identify it by using Regmon
(free) from <http://www.sysinternals.com/ntw2k/source/regmon.shtml>. Regmon
will let you export the output to a log file, if you have 90 seconds of registry
accesses to sift thru, that might be a good idea.

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not a problem - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.

[Richard G. Harper]

We handle this in our network by using an "offsite" login, created on the
local computer, and instruct users to select the machine name (not the
domain) and log on with the offsite credentials.

--
Richard G. Harper [MVP Shell/User] rgharper@gmail.com
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"jm78" <jm78@discussions.microsoft.com> wrote in message
news:DA243DFF-31F6-423B-9F30-F34B2DFB6194@microsoft.com...
> We have several notebooks (XP SP2) that are all members of our domain.
> The
> people who use them use domain user accounts to login to the notebooks.
> When
> these notebooks are used in the office login takes no time at all and the
> notebooks basically respond as our workstations do.
>
> Whenever these notebooks have a "non-corporate LAN" network connection
> (ie.
> wireless at home, etc) connected before initial login, XP hangs for ~90
> seconds before displaying the desktop and icons.
>
> With the network connection disabled or unplugged, login takes less than
> 20
> seconds.
>
> Does anyone know of a way in Windows to decrease this delay?
>
> Thanks