Jud said:
I tried one of those, and it gave me the same message "An error
occurred getting the status of the last synchronization. The RPC
server is unavailable."
Does that point to some problem on my end?
The last time I tried to debug a time problem, I got no where.
The w32time.log is filled with stuff I'm sure the developers
appreciate. But the log contents don't tell an end user
anything of interest. I think I added something to the
registry, to turn that on.
I can find instances of that RPC related error, but no quick and
easy solutions.
On my old Win2K machine, I think the "net time" command
is what I might have used. WinXP has w32tm for
such things, for manipulating the service.
If you enter "w32tm" in Help and Support, there is an
overview article. It gives the command syntax. There
is a /computer:Computername option, which implies
the command can even talk to other computers. This
could be the reason the command might use RPC
(remote procedure call). While I found one article
describing a "computer name mismatch" or a change in the
computer name, as a reason for an RPC to fail,
I don't know if something that obvious is at
work here. It could be one of those cases, that
the error message is a side effect of something
else (like a firewall problem).
Paul