Why does the EAP225 require IP address only for NTP server on the network?

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Why does the EAP225 require IP address only for NTP server on the network?

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Why does the EAP225 require IP address only for NTP server on the network?
Why does the EAP225 require IP address only for NTP server on the network?
2019-03-03 00:11:46
Model: EAP225  
Hardware Version: V3
Firmware Version: 2.4.0 Build 20181121 Rel. 55897(5553)

I have the latest firmware on the device and it will not accept host names for the NTP server configuration, only IP address.  That's not really good practice...

 

Could you please consider adding an update to the next firmware to include support for DNS queries to resolve an configured NTP server host name to an IP address?

 

  0      
  0      
#1
Options
4 Reply
Re:Why does the EAP225 require IP address only for NTP server on the network?
2019-03-04 09:04:40

Which IP-address do you use?

dich vu cam do anh hien: https://camdoanhhien.com
  0  
  0  
#2
Options
Re:Why does the EAP225 require IP address only for NTP server on the network?
2019-03-04 09:50:03

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.

 

 

  0  
  0  
#3
Options
Re:Re:Why does the EAP225 require IP address only for NTP server on the network?
2019-03-06 16:38:46 - last edited 2019-03-06 16:39:42

@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.

  1  
  1  
#4
Options
Re:Re:Why does the EAP225 require IP address only for NTP server on the network?
2020-10-02 05:57:17 - last edited 2020-10-02 09:12:03

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.

  0  
  0  
#5
Options

Information

Helpful: 0

Views: 1643

Replies: 4

Related Articles