W32time

[agresbach]

I am having an issue with a Windows XP laptop on our domain network. Everything works fine when it is plugged into our internal network and logged in. However, if you try logging in when you are not plugged into any network connection or an external connection (ie. home, hotel), it takes approximately 15 minutes after you enter your login credentials before it will log in. This doesn't happen every time but almost.
These are the System Even logs that occur when this happens. I did some research on w32tm issues but all were related to when they are plugged into their domain netowork and having problems syncing with the dc. for my situation that works fine, its just when its not on that network its still looking to synch with that dc and its not there so gets locked for 15 minutes.
any ideas??? i've heard of setting the laptop to use the internal battery as a time source but not sure if thats recommended or how to do that.
any help would be greatly appreciated!
thank you

Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 14
Date: 7/22/2006
Time: 11:20:15 AM
User: N/A
Computer: TPC-AGD-JSALCHE
Description:
The time provider NtpClient was unable to find a domain controller to use as a time source. NtpClient will try again in 15 minutes.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 29
Date: 7/22/2006
Time: 11:20:15 AM
User: N/A
Computer: TPC-AGD-JSALCHE
Description:
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. NtpClient has no source of accurate time.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

[glc]

Does this help at all?

http://support.microsoft.com/kb/314054/

[agresbach]

hmm that article looks very familiar. i might give that a try anyways though. thanks!
from what it looks like should those instructions set the system to look at the bios or cmos clock when logging in to sync rather than the DC?
do you know if this might cause any issues when plugged in and logging into the domain again ?

[glc]

Well, I think what you want to do is do what you have to in order to set up one of the Internet time servers as an alternate source if the domain time server can't be located. Try a carefully phrased Google search, you may find an article that covers this. That's how I found that M$ article.

You could of course just disable the Windows Time service - this will take care of that in a hurry. You might want to try that anyway to confirm that it's causing the problem.

[agresbach]

thanks for the help. i might try that just to see if it makes a difference but i'd imagine she'd need that service for SOMETHING when she's on the network, wouldnt she?
if i set up an alternate internet time source what will it do when she just logs onto her machine w/out being plugged into any connection? wouldnt the same thing occur? thats why i thought using the hardware choice would be a good one

[glc]

I've never had a XP box choke on bootup when it's not connected to a network or the Internet.