https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6114
--- Comment #15 from Norbert Koot <marbert@xxxxxxxxxx> 2011-07-20 21:15:00 PDT ---
(In reply to comment #7)
> (In reply to comment #5)
> > Created an attachment (id=6674)
--> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=6674) [details]
[details]
> > Heuristically determine endianness of originate, receive and transmit
> > timestamps.
>
> Thank you for acknowledging this issue. As Mr. Harris states, reversing the
> byte order appears to fix the issue for Windows. I've passed some raw
> time-stamp values from 6 different Windows PCs to an Excel sheet, to compare
> them (attachment). Re-ordering the bytes clearly works for WIN98 and XP,
> however for Vista and WIN7 the results imply that the byte order is likely the
> same but there is another bug in the MS implementation. The time-stamps after
> a 0.1 second delay are different by 93 to 109 seconds.
>
> This means that embedded devices that rely on *Windows XP-sourced* ICMP time-stamp for clock
> synchronization will fail under Vista or WIN7.
>
> --Norbert
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
