Dear Mangus,

I will allow myself to share a comment on your thread. 

Timing on windows servers is not one of their plausible strengths. It was 
clearly pointed out during the SIM conference last week at CENAM. In fact there 
was an interesting discussion about the drawbacks when using NTP Windows based 
servers and all kind of NTP appliances compared to full size Linux based NTP 
servers. The example of what NIST is using nationwide for their servers set an 
example of good server hardware and linux to provide the nation's NTP pulse.

I haven't done any experiments with Windows for NTP services, still it could be 
interesting as to set a benchmark while comparing it to the Linux boxes.

I am currently trying out the Domain Time II NTP client from Symmetricom for 
the thesis. I have to come back to Symmetricom's Miguel García to decide on 
purchasing a Domain Time II NTP client kit.  How is the Mainberg NTP client 
different from the Symmetricom version? Have you tried both? If not I will be 
more than glad to help comparing both if you can help me pointing out the 
source for a demo version of Mainberg's software. Maybe then an objective 
review of both clients will be in order, I will be more than glad to do it or 
to test them against Windows NTP services, appliances and/or Linux NTP boxes. I 
have at least an example of those at the office.

                        -13
Just my  2x10   cents.


Regards to you and the group,



Edgardo Molina
Dirección IPTEL

www.iptel.net.mx

T : 55 55 55202444
M : 04455 20501854

Piensa en Bits SA de CV



Información anexa:




CONFIDENCIALIDAD DE INFORMACION

Este mensaje tiene carácter confidencial. Si usted no es el destinarario de 
este mensaje, le suplicamos se lo notifique al remitente mediante un correo 
electrónico y que borre el presente mensaje y sus anexos de su computadora sin 
retener una copia de los mismos. Queda estrictamente prohibido copiar este 
mensaje o hacer usode el para cualquier propósito o divulgar su en forma 
parcial o total su contenido. Gracias.


NON-DISCLOSURE OF INFORMATION

This email is strictly confidential and may also be privileged. If you are not 
the intended recipient please immediately advise the sender by replying to this 
e-mail and then deleting the message and its attachments from your computer 
without keeping a copy. It is strictly forbidden to copy it or use it for any 
purpose or disclose its contents to any third party. Thank you.





On Oct 24, 2012, at 5:47 PM, Magnus Danielson <[email protected]> 
wrote:

> Fellow time-nuts,
> 
> When spending time on a conference last week, I heard one interesting comment 
> that they lost data due to bad timing on their Windows servers.
> 
> Now, I know that the standard Windows uses SNTP in order to achieve the goal 
> of having the timing of the machines sufficiently aligned to allow Kerberos 
> authentication. SNTP suffice for that, as it needs to be a handful of minutes 
> in line.
> 
> If you need better performance than that, you should use NTP (and then 
> download and install Meinbergs Windows-client for NTP).
> 
> Then again, I would point out that for this type of data, it would most 
> probably be better served on a Linux box.
> 
> What should be a nice wake-up call for them would be a summation of how 
> different strategies would give them clock precision of sufficient grade. So, 
> does anyone know of such measurements presented anywhere?
> 
> There are bits and pieces, but the ideal for this case would be if they where 
> collected in one page/paper.
> 
> This is an awareness thing, so that people can do a little more well-informed 
> choices.
> 
> Cheers,
> Magnus
> 
> _______________________________________________
> time-nuts mailing list -- [email protected]
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.

_______________________________________________
time-nuts mailing list -- [email protected]
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

Reply via email to