Re: NTP vs SNTP

[Roberto José Etcheverry Romero <yggdrasil.raiker@xxxxxxxxx>]

If you have any kind of enterprise you should have an inhouse NTP server
that gets it's time from the closest ntp.org and point everything from the
storage devices, network switches, IBM i LPARs, windows clients, etc to it.
That way you are certain that everything is sync'ed.
If you have Active directory you usually sync to the PDC or equivalent,
since kerberos is picky with time for its auth tickets.
There's nothing wrong with pointing everything to ntp.org but the increased
traffic and having to allow those devices communication to the internet
might not be a good idea.


On Tue, Nov 19, 2019 at 12:42 PM Steinmetz, Paul via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

> Not directly related.
> I was receiving TCP9110, did know why.
> I had previous SNTP issues, caused by the time servers I was pointing to
> were no longer valid.
> I now use us.pool.ntp.org.
> Is there a better choice?
>
> Some interesting articles SNTP vs NTP.
>
>
> https://www.streetdirectory.com/travel_guide/125508/computers/which_should_i_use_ntp_or_sntp.html
>
> Paul
>
>
>
>
> -----Original Message-----
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob
> Berendt
> Sent: Tuesday, November 19, 2019 10:20 AM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
> Subject: RE: NTP vs SNTP
>
> No.  Why? Is this related to this decision?
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
> to:  2505 Dekko Drive
>           Garrett, IN 46738
> Ship to:  Dock 108
>           6928N 400E
>           Kendallville, IN 46755
> http://www.dekko.com
>
>
> -----Original Message-----
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
> Steinmetz, Paul via MIDRANGE-L
> Sent: Tuesday, November 19, 2019 10:14 AM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
> Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
> Subject: RE: NTP vs SNTP
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
> Rob,
>
> Did you receive a TCP9110 30 DIAGNOSTIC The maximum threshold for SNTP
> Client  errors  has been reached?
>
> Paul
>
> -----Original Message-----
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob
> Berendt
> Sent: Tuesday, November 19, 2019 10:07 AM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
> Subject: RE: NTP vs SNTP
>
> I guess NTP vs SNTP is not a mission critical thing.  After all, this
> system was off by 3 minutes until last week when we noticed that it wasn't
> communicating to the ntp server due to firewall issues.  So if I mangle it
> I can reverse it without too much issue, right?  I may try it when I get a
> few other things cleared off of my plate.
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
> to:  2505 Dekko Drive
>           Garrett, IN 46738
> Ship to:  Dock 108
>           6928N 400E
>           Kendallville, IN 46755
> http://www.dekko.com
>
>
> -----Original Message-----
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
> Kevin Bucknum
> Sent: Tuesday, November 19, 2019 9:55 AM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
> Subject: RE: NTP vs SNTP
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
> There shouldn't be any difference. It is a client difference, not a
> protocol difference. The server shouldn't care what the client is using. I
> think anything running windows 10 is now NTP.
>
> -----Original Message-----
> From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf
> Of Rob Berendt
> Sent: Tuesday, November 19, 2019 8:42 AM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
> Subject: NTP vs SNTP
>
> Apparently NTP is a new thing with 7.3 and above.  It can be used instead
> of SNTP as a client to keep your clocks in sync.  I only discovered this
> because I was using the webby IBM Navigator for i.  Drilled down into TCP,
> Servers and checked SNTP and tried to view Connection Status and it was
> blank.  Opened up a ticket.  The support person had to look it up and get
> back to me.  Basically it will be blank unless you change your client type
> from SNTP to NTP.  He changed it on his system and then the connection
> status screen was active.
> It all sounds simple to me until I start worrying about if that will come
> through different ports, etc on our firewall thus having to get numerous
> network consultants from different companies involved (DMZ lpar).  And if
> there might be any required modifications on the SNTP servers to support
> NTP.  At this time I'm thinking not worth it.  What say ye?
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
> to:  2505 Dekko Drive
>           Garrett, IN 46738
> Ship to:  Dock 108
>           6928N 400E
>           Kendallville, IN 46755
> http://www.dekko.com
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
> unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives at
> https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com
>
>
> [https://www.medtronsoftware.com/img/MedtronMinilogo.bmp]  Kevin  Bucknum
>                    Senior Programmer Analyst
>                    MEDDATA / MEDTRON
>                    120 Innwood Drive
>                    Covington LA 70433
>                    Local: 985-893-2550
>                    Toll Free: 877-893-2550
>                  https://www.medtronsoftware.com
>
>
>
> CONFIDENTIALITY NOTICE
>
> This document and any accompanying this email transmission contain
> confidential information, belonging to the sender that is legally
> privileged.  This information is intended only for the use of the
> individual or entity named above.  The authorized recipient of this
> information is prohibited from disclosing this information to any other
> party and is required to destroy the information after its stated need has
> been fulfilled.  If you are not the intended recipient, or the employee of
> agent responsible to deliver it to the intended recipient, you are hereby
> notified that any disclosure, copying, distribution or action taken in
> reliance on the contents of these documents is STRICTLY PROHIBITED.  If you
> have received this email in error, please notify the sender immediately to
> arrange for return or destruction of these documents.
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com