| Re: [chrony-users] can not sync with vmware ntp server |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] can not sync with vmware ntp server
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Tue, 6 Jun 2017 13:24:48 +0200
- Authentication-results: ext-mx05.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx05.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=mlichvar@xxxxxxxxxx
- Dkim-filter: OpenDKIM Filter v2.11.0 mx1.redhat.com D30A31293
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com D30A31293
On Tue, Jun 06, 2017 at 01:18:25PM +0200, Thomas Aichinger wrote:
> Am 06.06.2017 um 12:13 schrieb Miroslav Lichvar:
> > The chrony config looks ok. Is there a firewall which drops packets
> > that don't have source port equal to 123? Does the ntpd server use the
> > orphan mode?
> >
> > Seeing output of "tcpdump -v port 123" on the client might help.
> >
> There is no firewall.
>
> The same client gets sync with "ntpq -p" but not with "chronyc sources"
> The esx server does not use orphan mode
>
> According to tcpdump chrony sends requests to esx but does not get any
> answer from esx.
> But ntp does. Here is a dump.
That is odd. Can you please try to add "acquisitionport 123" to
chrony.conf and see if it helps? That will make it use source port 123
like ntpd does. If that helps, it must be something with the
networking configuration.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.