Hello. I have been having issues with my windows based workgroup (not domain) issuing timeouts when trying to sync with the ntp time servers (time.windows.com, time.nist.gov, pool.ntp.org, etc). The thing is when I leave all else alone (windows firewall, gateway settings) and instead connect to my gateway rather than the router, the computer syncs just fine. I had tried to add the following iptables rules to the router:
When I tried to use the port-forwarding feature, adding items didn't stick even upon clicking "Apply". I had even disabled the firewall using the web gui and the sync attempts would timeout.
But I also noticed that the firmware can or does serve as a local ntp server. If so, how can I bypass this so that I can reach out to the ones out in the world? Or if it's more recommended for a LAN, how can I setup the ntp server in the firmware so that I can just have my host computers sync to that? I tried syncing to the local ip address of the router (192.168.1.1) but that timed out as well.
I also found a thread that reports the same thing except with dd-wrt. I'm wondering if wrt'ish firmware is plagued with these issues or if incidentally the OP of the other thread and I are just poor and configuring this awesome firmware. Thanks!
Code:
iptables -A OUTPUT -p udp --dport 123 -j ACCEPT
iptables -A INPUT -p udp --sport 123 -j ACCEPT
iptables -A INPUT -p udp --dport 123 -j ACCEPT
iptables -A OUTPUT -p udp --sport 123 -j ACCEPT
When I tried to use the port-forwarding feature, adding items didn't stick even upon clicking "Apply". I had even disabled the firewall using the web gui and the sync attempts would timeout.
But I also noticed that the firmware can or does serve as a local ntp server. If so, how can I bypass this so that I can reach out to the ones out in the world? Or if it's more recommended for a LAN, how can I setup the ntp server in the firmware so that I can just have my host computers sync to that? I tried syncing to the local ip address of the router (192.168.1.1) but that timed out as well.
I also found a thread that reports the same thing except with dd-wrt. I'm wondering if wrt'ish firmware is plagued with these issues or if incidentally the OP of the other thread and I are just poor and configuring this awesome firmware. Thanks!
Last edited: