This sounds strange, but I had something similar to this. The way we fixed it was to have the user go into Outlook Web Access and through the OWA options select his proper timezone. It fixed it for him (don't ask me why.. or how this is connected)
If you do try this though, please give feedback if it resolved the problem.