Danged W32Time errors...how to fix for good??? 1

[wahnula]

Hello,

I have an SBS2003 SP1 Premium server that gives me 2-3 W32Time errors per day, spoiling my pristine Daily Report more often than not.

I have applied the fix described here:

http://www.smallbizserver.net/Default.aspx?tabid=266&articleType=ArticleView&articleId=71

Which calls for the following commands:

w32tm /config /manualpeerlist:time.nist.gov,0x8 /syncfromflags:MANUAL
net stop w32time
net start w32time
w32tm /resync

I asked my tech to fix the problem, he changed the time source to 127.0.0.1, still had many errors, so I reverted to the above procedure and the errors lessened but still persist.

As always any & all help is greatly appreciated.

Tony

 

[ShackDaddy]

Tony, you need to surpress those sorts of errors in your daily report. I'd say the majority of the SBS servers out there get them now and then. The fact that you are only having 2-3 per day is a good thing. That means that the process that is generating the errors usually succeeds.

Go ahead and post the text of the error so we can advise you better.

ShackDaddy
Shackelford Consulting

 

[wahnula]

ShackDaddy,

Event Type:	Error
Event Source:	W32Time
Event Category:	None
Event ID:	29
Date:		3/5/2007
Time:		10:14:50 AM
User:		N/A
Computer:	SBS2
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 960 minutes. NtpClient has no source of accurate time. 

For more information, see Help and Support Center at [URL unfurl="true"]http://go.microsoft.com/fwlink/events.asp.[/URL]

So...ignorance is bliss???

Tony

 

[ShackDaddy]

Ignorance is sometimes bliss. These sorts of errors are the "where do you squeeze the toothpaste tube?" equivalent in a marriage. You usually enjoy increased marital bliss when you ignore them. Or you can pursue them for fun, as a distraction from more important questions.

I would try switching time servers every couple of days until you get one that's more reliably responsive. I think the error is due to a time-out when querying the nist.gov server.

ShackDaddy
Shackelford Consulting

 

[wahnula]

Or you can pursue them for fun, as a distraction from more important questions.

Yeah, Landscape Architect in high season, lots of time for that. Then again tech work is really a welcome distraction for me(as long as it's not a blazing fire), so maybe I will try different timeservers. I'm just a blasted perfectionist!

I really should get back to work LOL

Tony

 

[wahnula]

UPDATE: Timeserver was changed to time.microsoft.com and to date no more W32tm errors. I am a happy boy again...oh no wait...DST is different this year...ARRRRGGGHHH