The local IT guys managed to identify the answer:
The client PC that was showing "wrong" information (timestamps at 11pm) was missing hotfix KB981793 - a cumulative patch for time zone rules.
Not what I expected at all - but installing that hotfix has fixed the problem on every machine we've tested.
Bevan
2010-08-10 02:47:04