Time being off is not minor. If your time is off more than 120 seconds the packets won't be accepted on the PoP, which will simply discard them. AICCU, or actually the TIC server, checks at the moment AICCU fetches the configuration if the clock on the client is in margins, if it is it allows the configuration to be fetched, otherwise it notifies the user and doesn't even continue. I have been thinking of adding two parts to AICCU to solve these issues though: - Automatic connectivity check, which checks if connectivity really works and notifies the user if it doesn't and the most likely reason why it doesn't. - Re-fetch of the configuration now and then, which would then also check the time setting again just in case. Depending on available time these should be added sooner or later (most likely the latter though... ;) )

I had read about the issue of time synchronization in the FAQ. I've repeatedly checked for a lack of time synchronization, but haven't found any problems. All of my systems are configured in a Windows Domain, and the top domain controller provides time service to all members, and in turn consults the U.S. National Bureau of Standards time service. Thanks for the tip.