Rock,

Spoken like a gentleman. I just didn't want anyone to misunderstand.

Thanks,
Milt

"Rock" wrote:

> "Milt" <Milt@discussions.microsoft.com> wrote
> > Rock,
> >
> > I didn't mean to criticize anyone here. I just mean that someone at
> > Microsoft should really look into it after so many people posting the same
> > problem. (And I suspect that many more have the same problem but aren't
> > aware
> > of it. They don't manually sync. or read their error reports.) Even if
> > it's
> > not caused by them, M/S could offer some help.
>
> > I've written them about it a few times. Guess what. No answer!
> >
> > "Rock" wrote:
> >
> >> "Milt" <Milt@discussions.microsoft.com> wrote
> >> > C'mon guys,
> >> >
> >> > Over the past month at least a few dozen people have posted this
> >> > problem
> >> > with time servers. Darn near every patch and update that Microsoft has
> >> > ever
> >> > issued has been suggested as a remedy. But I have yet to see a proper
> >> > reason
> >> > why the problem is occurring! Or a real "fix" for it.
> >> >
> >> > Yes, a workaround is to choose other time servers. I've been able to
> >> > use
> >> > time.xmission.com successfully for manual time updates. I don't know
> >> > yet
> >> > if
> >> > it will work for scheduled updates though.
> >> >
> >> > Isn't it about "time", if you'll pardon the word, for Microsoft to look
> >> > into
> >> > the issue and resolve it?
> >>
> >> C'mon guys, what? I'm not sure what are you expecting of the folks here.
> >> This is a peer to peer newsgroup. Everyone posting here is a volunteer
> >> offering their assistance with problems. If you want some input from MS
> >> contact their tech support through the normal channels.
>
>
> No problem, Milt. I didn't mean to imply nor think you were criticizing
> anyone here. I just thought you might have thought this was MS tech
> support. Some posters think that's the case, and expect an MS employee to
> respond. Sorry if there was a misunderstanding.
>
> --
> Rock [MS-MVP User/Shell]
>
>