I did some more testing with a total of four different machines behind
the NAT. Two of them synced in a few seconds, the other two were stuck
in INIT. For the machines that didn't sync, the external server did
not respond at all.
Here are the detailed packet captures of each session, as seen from
On Sat, Apr 7, 2012 at 16:53, Ken Link kl...@numberzero.org wrote:
I did some more testing with a total of four different machines behind
the NAT. Two of them synced in a few seconds, the other two were stuck
in INIT. For the machines that didn't sync, the external server did
not respond at
On Sat, Apr 7, 2012 at 21:36, Dave Hart h...@ntp.org wrote:
I notice the successful clients were querying using ports 123, and
the failing ones 123. I dimly recall seeing an inappropriate
less-than-123 source port comparison in ntpd long ago, in fact I'd
have guessed it had been removed
Hello,
I'm trying to sync two NTP clients behind the same NAT to an Internet
NTP server. Both machines behind the NAT have the same NTP
configuration file and are running v4.2.6p4 on Windows XP. The NTP
server outside the NAT is running v4.2.6p3 on Ubuntu 10.04 LTS. The
problem I'm having is that
On Fri, Apr 6, 2012 at 02:38, Ken Link kl...@numberzero.org wrote:
Now I stop NTP on machine A and start NTP on machine B. The client
request goes out the NAT, and I see the request coming into the
external server with tcpdump. But, NTP on the external server doesn't
respond. In fact, the
