Slow logon with network connection in other network as normal doma

[Guest]

We are using windows xp laptops connected to a Win2003 domain, with offline
files configured.
When connected with a networkcable everything works fine. When not connected
at all working offline is also fine.
However when the laptop is connected to a network other than the workstation
network containing the domain controllers the logon is very slow.
This happens when the wireless adapter is enabled and connected to a guest
network, or when connected to a guest network with networkcable for instance.

It seems that the laptop detects a network link and tries to find the
domaincontroller.
Most of the time this takes some 10 to 15 seconds but sometimes it takes up
to 1 or 2 minutes before the laptop is logged in and available to the user
which is very annoying.

Is the timeout value changeable? Or is there another solution to this problem?

Regards,

Merijn

 

[Lanwench [MVP - Exchange]]

We are using windows xp laptops connected to a Win2003 domain, with
offline files configured.
When connected with a networkcable everything works fine. When not
connected at all working offline is also fine.
However when the laptop is connected to a network other than the
workstation network containing the domain controllers the logon is
very slow.
This happens when the wireless adapter is enabled and connected to a
guest network, or when connected to a guest network with networkcable
for instance.

It seems that the laptop detects a network link and tries to find the
domaincontroller.
Most of the time this takes some 10 to 15 seconds but sometimes it
takes up to 1 or 2 minutes before the laptop is logged in and
available to the user which is very annoying.

Is the timeout value changeable? Or is there another solution to this
problem?

Regards,

Merijn

My solution is: don't use offline files. Check out the shareware app at
www.centered.com - they have a 30 day eval. I hate offline files, and
SecondCopy 2000 has become part of my standard laptop build.

 

[Guest]

Thanks for your reply.
However the long wait time is seen just after entering the password. Like it
takes some time to conclude the domain controller is not available so the
local database should be used.

That doesn't seem to be connected to using offline files.

Regards,

Merijn

 

[Lanwench [MVP - Exchange]]

Thanks for your reply.
However the long wait time is seen just after entering the password.
Like it takes some time to conclude the domain controller is not
available so the local database should be used.

That doesn't seem to be connected to using offline files.

Ah - sorry, I misunderstood & jumped the gun.
So I suppose when you have *no* network connection whatsoever, all is fine?
I have heard of this before but unfortunately I don't have any KB articles
handy - sorry.

 

[Guest]

I am having the same problems. If we take a domain member laptop off the
network, plug it into a network which the domain controllers are not on
(including a cellular or wireless connection) I get an extremely slow logon
immediately after pressing enter at the logon box. Once logged on there is
a severe latency just to get the start menu to fly out or to browse c: in
explorer.

It seems to work fine when not plugged into any network. So, if it sees
there is no network connection it cancels contacting the DC and group policy
download. If it sees the LAN port is activated, it automatically tries
connecting to the DC to process Group Policy.

I've started with a completely new install of Windows XP Pro SP1 added to
the domain and got the same thing. I've played with many options found
throughout the internet including:

Slow Link Speed
Patch from Article ID 811525
Increase Domain Logon Timeout Article ID 163204
Fast Logon Optimization Article ID 305293
Ghosted Connections Article ID 127018
Disable Persistent Connections Article ID 238852
Hotfix from Article ID 329457
Patch from Article ID 826239
Increase Domain Logon Timeout Article ID 163204

There has to be a way set a timeout for DC contact or send a ping and if no
response, cancel.

Does anybody have any ideas?

Thank you,

Allen