- Overview
- Configuration
- NTP4 Plug-In
- Hardware
- RFC 868
- RFC 2030
-
RFC 1305
- RFC 1305
- 1. Introduction
- 1.1 Related Technology
- 2. System Architecture
- 2.1 Implementation Model
- 2.2 Network Configurations
- 3. Network Time Protocol
- 3.1 Data Formats
- 3.2 State Variables and Parameters
- 3.2.1 Common Variables
- 3.2.2 System Variables
- 3.2.3 Peer Variables
- 3.2.4 Packet Variables
- 3.2.5 Clock-Filter Variables
- 3.2.6 Authentication Variables
- 3.2.7 Parameters
- 3.3 Modes of Operation
- 3.4 Event Processing
- 3.4.1 Notation Conventions
- 3.4.2 Transmit Procedure
- 3.4.3 Receive Procedure
- 3.4.4 Packet Procedure
- 3.4.5 Clock-Update Procedure
- 3.4.6 Primary-Clock Procedure
- 3.4.7 Initialization Procedures
- 3.4.7.1 Initialization Procedure
- 3.4.7.2 Initialization-Instantiation Procedure
- 3.4.7.3 Receive-Instantiation Procedure
- 3.4.7.4 Primary Clock-Instantiation Procedure
- 3.4.8 Clear Procedure
- 3.4.9 Poll-Update Procedure
- 3.5 Synchronization Distance Procedure
- 3.6 Access Control Issues
- 4. Filtering and Selection Algorithms
- 4.1 Clock-Filter Procedure
- 4.2 Clock-Selection Procedure
- 4.2.1 Intersection Algorithm
- 4.2.2. Clustering Algorithm
- 5. Local Clocks
- 5.1 Fuzzball Implementation
- 5.2 Gradual Phase Adjustments
- 5.3 Step Phase Adjustments
- 5.4 Implementation Issues
- 6. Acknowledgments
- 7. References
- Appendix A
- Appendix B
- Appendix C
- Appendix D
- Appendix E
- Appendix F
- Appendix G
- Appendix H
- Appendix I
- Time Tools
- NTP Auditor
- About
| Previous Top Next |
Windows Time Server
NTP4 Plug-In Driver TroubleshootingIf your GPS or radio clock is listed as supported or you have a clock model which you feel is compatible with a clock listed under NTP4 Plug-In Drivers and your clock is unable to communicate with PresenTense Time Server, kindly let us know. Please submit a detailed problem report by email to support@bytefusion.com listing details of both the operating system and service pack information of your computer as well as the exact model number and description of your GPS or radio clock.
Additionally, we request that you submit a serial port capture, showing the interaction between PresenTense Time Server and your clock. This will confirm to us that your PC hardware is operating correctly and that your GPS or radio clock is properly connected to your PC. The serial port capture will also help us troubleshoot the interaction between your clock and PresenTense Time Server. We request that you submit your serial port capture as a ".lgs" file as produced by the HHD Serial Port Monitor. A sample serial port capture showing the interaction between PresenTense Time Server and an Arbiter GPS receiver is displayed below.
