We recently threw up a 525 w/failover. The problem is that our Kronos Timeclocks are not talking to the outside (the County). My guess is that these devices, for some reason, do not handle translation very well (or at all?). The correct UDP ports are opened in the pix as well as the arp entries and a translated IP address. Has anyone here any Experience with Kronos Timekeeper or similar time clock systems? We can't wait for the company to sort it out and are at a loss on what to do. Thoughts? Questions?
Krono clock is very time sensitive, but the timing is ajustable. Your problem may not be at the config. Your config looks fine to me. to ajust the timeout, the file is under \program files\kronos\wfc\dcm, file name is krdcm. under [data collection manager] and [comm channel name], there are timeout statics you may change. You may need to contact kronos to find out what will be the best timeout timing for you. they would like to see 70ms, but that's very hard to meet for WAN, we have changed to over 2min. hope this will help. we are using the Kronos 400 terminal clock.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...