wr841n - no timeserver connection
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
wr841n - no timeserver connection
Posts: 3
Helpful: 1
Solutions: 0
Stories: 0
Registered: 2017-01-13
2017-01-13 15:29:38
Posts: 3
Helpful: 1
Solutions: 0
Stories: 0
Registered: 2017-01-13
wr841n - no timeserver connection
2017-01-13 15:29:38
Tags:
Model :
Hardware Version :
Firmware Version :
ISP :
Even after entering "north-america.pool.ntp.org", still no connection can be made to update time from time server. This is the case even after a firmware upgrade. It just gives an error message after trying to get present time.
Hardware Version :
Firmware Version :
ISP :
Even after entering "north-america.pool.ntp.org", still no connection can be made to update time from time server. This is the case even after a firmware upgrade. It just gives an error message after trying to get present time.
#1
Options
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Thread Manage
Announcement Manage
5 Reply
Posts: 4334
Helpful: 1039
Solutions: 173
Stories: 3
Registered: 2015-12-05
Re:wr841n - no timeserver connection
2017-01-14 00:11:45
Did you set the gateway IP in IP settings if using static IP?
༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#2
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Announcement Manage
Posts: 3
Helpful: 1
Solutions: 0
Stories: 0
Registered: 2017-01-13
Re:wr841n - no timeserver connection
2017-01-14 09:15:28
Hi,
No, this is setup only as WDS bridge plus wireless access point. I think the WAN port is fried anyway. So it just has the bssid of the base router and has its own ip of 192.168.1.20. It is connected to one machine by cat5 cable- kind of a subtitute for a wireless card. But everything works fine except for the ntp. ntpdate program works on the machine though:
root@debian:/home/0# ntpdate pool.ntp.org
13 Jan 19:11:19 ntpdate[23390]: step time server 216.229.4.69 offset 2.003932 sec
No, this is setup only as WDS bridge plus wireless access point. I think the WAN port is fried anyway. So it just has the bssid of the base router and has its own ip of 192.168.1.20. It is connected to one machine by cat5 cable- kind of a subtitute for a wireless card. But everything works fine except for the ntp. ntpdate program works on the machine though:
root@debian:/home/0# ntpdate pool.ntp.org
13 Jan 19:11:19 ntpdate[23390]: step time server 216.229.4.69 offset 2.003932 sec
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#3
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Announcement Manage
Posts: 4334
Helpful: 1039
Solutions: 173
Stories: 3
Registered: 2015-12-05
Re:wr841n - no timeserver connection
2017-01-14 19:49:32
You need to set a default gateway if you use a static IP for the router. Without a default gateway the router's NTP daemon cannot find or connect to servers. Wether
ntpdate on your Debian Linux box works or not, is irrelevant for the NTP daemon running on the router.
༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#4
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Announcement Manage
Posts: 3
Helpful: 1
Solutions: 0
Stories: 0
Registered: 2017-01-13
Error code: 5028
2017-01-15 00:04:17
Hi R1D2:
Nothing worked when i tried to set default gateway, but Thanks for helping. Apparently, when in wds bridge mode, the time service does not work, probably because of latency more than 500 milliseconds, as per some older threads.
This worked when actual ip addr of 1.north-america.pool.ntp.org (192.155.90.13) is placed in the first time server's box, and is also setup as a static route under advanced routing..so is a good workaround. I have not tried other variations of this yet, but they may work.
For anyone using wds bridge mode, see older post here or do search on "Error code: 5028":
http://forum.tp-link.com/showthread.php?77730-TL-WR841N-WDS-Setup-Like-quot-Client-Bridge-quot-mode-of-Broadcom-Based-Routers&p=149747&viewfull=1#post149747
Nothing worked when i tried to set default gateway, but Thanks for helping. Apparently, when in wds bridge mode, the time service does not work, probably because of latency more than 500 milliseconds, as per some older threads.
This worked when actual ip addr of 1.north-america.pool.ntp.org (192.155.90.13) is placed in the first time server's box, and is also setup as a static route under advanced routing..so is a good workaround. I have not tried other variations of this yet, but they may work.
For anyone using wds bridge mode, see older post here or do search on "Error code: 5028":
http://forum.tp-link.com/showthread.php?77730-TL-WR841N-WDS-Setup-Like-quot-Client-Bridge-quot-mode-of-Broadcom-Based-Routers&p=149747&viewfull=1#post149747
1
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
1
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#5
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Announcement Manage
Posts: 4334
Helpful: 1039
Solutions: 173
Stories: 3
Registered: 2015-12-05
Re:wr841n - no timeserver connection
2017-01-15 03:17:07
Of course it also works with a static route instead of a default route. Not that much difference! :)
But having to use IP addresses for NTP is definitely a bug - I reported this for the EAP models long time ago to TP-Link already. No feedback so far.
The folks providing NTP servers for free are not amused if IP addresses are being used widely. They explicitly demand users to only use domain names, since using IPs break their load-balancing scheme. TP-Link should really fix this before the folks at ntp.org will decide to permanently blacklist devices using IPs instead of domain names.
But having to use IP addresses for NTP is definitely a bug - I reported this for the EAP models long time ago to TP-Link already. No feedback so far.
The folks providing NTP servers for free are not amused if IP addresses are being used widely. They explicitly demand users to only use domain names, since using IPs break their load-balancing scheme. TP-Link should really fix this before the folks at ntp.org will decide to permanently blacklist devices using IPs instead of domain names.
༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
1
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
1
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#6
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Announcement Manage
Posts: 3
Helpful: 1
Solutions: 0
Stories: 0
Registered: 2017-01-13
2017-01-13 15:29:38
Posts: 3
Helpful: 1
Solutions: 0
Stories: 0
Registered: 2017-01-13
Information
Helpful: 0
Views: 1854
Replies: 5
Voters 0
No one has voted for it yet.
Tags
Related Articles
Exposed APIs for wr841n?
520
0
TL-WR841N login
2320
0
TL-WR841N transmit power
1831
0
Report Inappropriate Content
Transfer Module
New message