>>> In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] writes:
Phil> I have a Windows 2000 Server system that has two IP address configured Phil> - one a routeable address, the other is 192.168.2.x for communication Phil> with internal devices. My time source requires communication outside Phil> the local environment, but it would appear that the server randomly Phil> decides to only try to synch via the 192.168 interface, and failing. Sounds like a bug to me... Please open a report at http://bugs.ntp.org . Phil> I wandered through the support.ntp.org site, and found reference to a Phil> directive "listen-on" being discussed. Is something resembling that Phil> functionality available in 4.2.4p5, or is the current behavior of "all Phil> interfaces" my only current option? Support for listen-on is not yet in any condition to be released. Danny has been *very* busy elsewhere, no new volunteers have stepped up to work on that task, and the NTP Forum does not yet have enough members to pay somebody to work on this task. I remain open to suggestions... -- Harlan Stenn <[EMAIL PROTECTED]> http://ntpforum.isc.org - be a member! _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
