Re: Firewalled NTP on Redhat - ntpdate works, but ntpq doesn't
- From: "Herta Van den Eynde" <herta.vandeneynde@xxxxxxxxx>
- Date: Fri, 18 May 2007 23:27:18 +0200
On 18/05/07, Young, Mike <Mike.Young@xxxxxxxxxxxxxx> wrote:
Good info, but does ntpq use different ports than ntpdate? After all, ntpdate works, but ntpq does not.
It's easy to check. Open two terminal windows on your client.
In the first, run
# tcpdump -nn host 213.239.194.210
(213.239.194.210 is the address of a public ntp server, but you can
substitute it with one of your own)
In the second run
# ntpdate -q 213.239.194.210
On my laptop, it results in:
23:20:10.906836 IP 182.188.1.103.32890 > 213.239.194.210.123: NTPv4,
Client, length 48
23:20:10.938987 IP 213.239.194.210.123 > 182.188.1.103.32890: NTPv4,
Server, length 48
23:20:10.939104 IP 182.188.1.103.32890 > 213.239.194.210.123: NTPv4,
Client, length 48
23:20:10.971364 IP 213.239.194.210.123 > 182.188.1.103.32890: NTPv4,
Server, length 48
23:20:10.971444 IP 182.188.1.103.32890 > 213.239.194.210.123: NTPv4,
Client, length 48
23:20:11.002340 IP 213.239.194.210.123 > 182.188.1.103.32890: NTPv4,
Server, length 48
23:20:11.002434 IP 182.188.1.103.32890 > 213.239.194.210.123: NTPv4,
Client, length 48
23:20:11.037272 IP 213.239.194.210.123 > 182.188.1.103.32890: NTPv4,
Server, length 48
So, my laptop uses a high port value, the server uses 123.
Kind regards,
Herta
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
- References:
- Re: Firewalled NTP on Redhat - ntpdate works, but ntpq doesn't
- From: Herta Van den Eynde
- RE: Firewalled NTP on Redhat - ntpdate works, but ntpq doesn't
- From: Young, Mike
- Re: Firewalled NTP on Redhat - ntpdate works, but ntpq doesn't
- Prev by Date: Re: RHEL Linux 3 - AS vs ES
- Next by Date: mail sending problem..
- Previous by thread: RE: Firewalled NTP on Redhat - ntpdate works, but ntpq doesn't
- Next by thread: Re: Firewalled NTP on Redhat - ntpdate works, but ntpq doesn't
- Index(es):
Relevant Pages
- Re: Unable to access local workstations from SBS 2003
... domain AT the client. ... I did focus on the DNS of the server as a possible
issue. ... Relative to the "..computer name is not in Win2K3" I mean that the laptop ...
>> I'm able to do just about anything from the laptop or any other workstation ...
(microsoft.public.windows.server.sbs) - Re: What doesnt lend itself to OO?
... >> proxy and instructs the server to constuct the real object. ... rather
than client code. ... If 'clock' is instantiated in the server, ... >
for the server interface at the OOA level. ... (comp.object) - This is going straight to the pool room
... or not the client has privilege to do what they're trying to do, ... The server
environment is this: ... 3GL User action Routines that Tier3 will execute on your behalf
during the ... Routine Name: USER_INIT ... (comp.os.vms) - Re: Unable to access local workstations from SBS 2003
... Ensure there is no local HOSTS and LMHOSTS files on the client PCs ... Not sure
why you would specify the UNC computer path - browse to the server, find a server share, right
click 'Copy' ... Relative to the "..computer name is not in Win2K3" I mean that the laptop
computer name, eg DCF9R51, is not part of the "Computers" in Active Directory. ... I'm able
to do just about anything from the laptop or any other workstation on the domain: logon, WinExplore,
delete but, evidently, not copy/move FROM the server. ... (microsoft.public.windows.server.sbs) - [Full-Disclosure] R: Full-Disclosure Digest, Vol 3, Issue 42
... Full-Disclosure Digest, Vol 3, Issue 42 ... SD Server 4.0.70 Directory
Traversal Bug ... Arkeia Network Backup Client Remote Access ... (Full-Disclosure)