Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'My firewall does not have a hole for UDP 123 and the timeserver works nevertheless?' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
My firewall does not have a hole for UDP 123 and the timeserver works nevertheless?
Authored by: hamarkus on Aug 11, '04 02:58:15PM

My firewall does not have a hole for UDP 123 and the timeserver works nevertheless???



[ Reply to This | # ]
My firewall does not have a hole for UDP 123 and the timeserver works nevertheless?
Authored by: cleanhead on Aug 11, '04 04:20:13PM

Mine too under Panther. System time drifted out of synch under Jaguar, however, until I opened port 123. Maybe a bug fixed?



[ Reply to This | # ]
My firewall does not have a hole for UDP 123 and the timeserver works nevertheless?
Authored by: dsouth on Aug 11, '04 04:30:12PM

The desktop clients initiate the connections to the NTP servers. So unless you've configured your firewall to disallow outgoing connections, the AE will be allowed to connect to ntpd running at time.apple.com, and any macs on your wireless net can connect to the ntpd running on the AE.

Note that, unless you've modified the /etc/ntp.conf file, ntpd will allow other machines to connect and query time. So if you set one Mac/access point/whatever to synchronize with time.apple.com, other machines on the network can synchronize with that machine. Large sites often make use of this to implement several strata of time service.



[ Reply to This | # ]