What about trying listen on *? And are you mabye running pf with block-policy return? There are a bunch of reasons why connections might be reset. If listen on * still doesn't work, maybe think about filing some sort of bug report, or posting more to the list to get the problem solved, because OpenNTPd should work just fine, does for me. My entire network (including my XP machines) sync against OpenNTPd running on current just fine.
Jason On 6/26/05, J.D. Bronson <[EMAIL PROTECTED]> wrote: > At 04:29 PM 6/26/2005, Jason Crawford wrote: > >By default, OpenNTPd doesn't listen on any port, it just acts as a > >client for the local machine only. In order for it to serve time to > >other machines on your network, you must uncomment the listen * line > >in /etc/ntpd.conf, then send a SIGHUP to ntpd, or restart it, in order > >for it to listen on port 123. time in inetd.conf refers to the UNIX > >time protocol on port 37, which doesn't really have anything to do > >with ntp. Uncomment the listen * line in /etc/ntpd.conf and then it'll > >allow any box to sync time with it. > > > >Jason > > > Thats what I had thought....so here is what I did with ntpd.conf: > > # Addresses to listen on (ntpd does not listen by default) > listen on 192.168.10.1 > > ...then rebooted (what the heck) and still it wont permit any time sync. > the clients still get connection refused. > > Its ok though, I got it working via NTPD, but just didnt understand > why openntpd has this issue. :-( > > thanks for the reply. > > > > > > > > -- > J.D. Bronson > Information Services - Telecom > Aurora Health Care - Milwaukee, Wisconsin > Office: 414.978.8282 // Fax: 414.314.8787
