Our system date/time synchronization works like this:
<omnisense web server inserts current UTC date/time into http header on response sent to gateway> then
<omnisense gateway sets its clock from the http header> then
<omnisense sensor sets its clock from gateway clock>
The system is fool proof unless you are using a proxy server which rewrites the HTTP header and your proxy server does not have the proper date and time set. When using a proxy it looks more like this:
<omnisense web server inserts current UTC date/time into http header on response sent to gateway> then
<local network’s proxy server rewrites HTTP header> then
<omnisense gateway sets its clock from the http header> then
<omnisense sensor sets its clock from gateway clock>
To solve this talk to your IT department and ask them to configure your proxy server to sync its clock to a NIST time standard time server on a regular schedule.
<omnisense web server inserts current UTC date/time into http header on response sent to gateway> then
<omnisense gateway sets its clock from the http header> then
<omnisense sensor sets its clock from gateway clock>
The system is fool proof unless you are using a proxy server which rewrites the HTTP header and your proxy server does not have the proper date and time set. When using a proxy it looks more like this:
<omnisense web server inserts current UTC date/time into http header on response sent to gateway> then
<local network’s proxy server rewrites HTTP header> then
<omnisense gateway sets its clock from the http header> then
<omnisense sensor sets its clock from gateway clock>
To solve this talk to your IT department and ask them to configure your proxy server to sync its clock to a NIST time standard time server on a regular schedule.
0