Hi,

Thank you for the suggestion. For now, the NTP Server just support IP address. We will add the suggestion in our improvement suggestion list.

@NgocAnh94 The IP Address that you need to configure currently is the one for the NTP server you want to talk to... My suggestion is to allow us to configure a hostname instead.

Likewise EAP 245, same limitation. Standard practice uses specified address in form: 0.pool.ntp.org 1.pool.nrp.org ..etc. This allows the fastest and most acurate responses to all queries. EAP 245 demands IP number and refuses to save format above.

In addition, although it may follow TP-Link convention, the failed attemp to save the actual time and date corrections ( i.e: set the correct date and time) is lost when the error of using the correct named entered servers (not supported in product, described above).  The admin then may believe they have set the correct information manually or by synch to the admin PC (also supported in this section) but data entered is not retained, apparently blocked by the NTP addreses entered instead of the IP numbers. This adds additional unexpected behavior and wildly incorrect date/time data and follow on confusion in logs and reports.  A warning that the data in that section has not been saved is not displayed or unclear. This error is compounded by (Optional) designation of the NTP fields. Invalid data in fields marked optional prevents updates in required (non blank) fields, contrary to reasonable expectation.