NASLite Network Attached Storage

I have not been able to get my NAS unit to time synch via the internet.
I have found several servers that provide the RFC-868 protocol (not all do) and have tried them with no success.

I tried opening a hole in my router's firewall for UDP and for TCP on port 37.

I also installed a client time-synching program on a machine connected to the same network and it works (set for an RFC-868 protocol); the router firewall changes don't appear to be necessary for this to happen. Works both ways.

I set a timeserver IP address in NAS, save the configuration, and reboot; then let it go for a week or so. But I never see any change from the 'Unknown' on the NAS system status page for 'Last Successful Synchronization'.

How often does NAS try to get a time reading?

(Using NAS-CDD version 2.06)

No real biggie, but it would be nice to have it working.
Any ideas, anyone?
Thanks.

javascript:emoticon(':(')
Sad

Yeah I have the same thing going here.. got a local linux NTP server that syncs all my clients fine but NASLite still reports:

I use 129.6.15.28 to sync the clock. So far haven't had any problems.

NASLite-2 uses rdate as opposed to NTP. The benefits of rdate are mainly compact size and very low resource usage. It uses port 37 (opposed to 123 for NTP).

For further info on rdate, one can refer to the following: http://www.faqs.org/rfcs/rfc868.html

In contrast, take a look at the rfc governing NTP: http://www.faqs.org/rfcs/rfc1305.html

Once set, NASlite-2 can then be used to sync clocks of windows machines using the NET command as follows: NET TIME \\NAMEORIP /SET /YES

I guess I'll try 129.6.15.28 then.. feels abit odd to point to a time server in the US when I have a local time server sitting right next to the NASLite box

I understand,

The key however is an RFC 868 compliant time server.

[quote="Tony"]I use 129.6.15.28 to sync the clock. So far haven't had any problems.

That's one that I tried. I have it set to that IP right now, no update.
I used a separate client time setting program to verify that I can reach the time-server from here.


[quote="Tony"]NASLite-2 uses rdate as opposed to NTP. The benefits of rdate are mainly compact size and very low resource usage. It uses port 37 (opposed to 123 for NTP).

Yes, I tried several servers which support RFC-868. /port 37.

You didn't answer one question: 'how often does NAS try a time synch?' Will it happen right after boot-up or do I have to wait some time?? Are there retries?

Maybe I can put a packet sniffer on it and see if anything is coming out of the box.

I take it one has to set a gateway in order for the time sync to work.. have you entered a gateway in NASLite settings? Mine actually did sync after using the 129.6.15.28 server:

Once at boot time and once each day at 00:00 UTC

Sorry for "reviving" such an old thread ... but I just had the same question, and could not otherwise find an answer. I noticed that the documentation does not even mention "timeserver" in it (hint ... hint) ... might want to update the User Guide/Install_and_Admin Manual

So ....

Now that I have started looking into using the TimeServer feature ... I am unable getting it to work. In debugging the issue with an Ubuntu system on the same internal network, I have discovered that under Ubuntu (after installing "rdate") I need to specify the "-u" option for the command to work; omitting it causes the command to hang.

rdate -pu 129.6.15.28 (this works on Ubuntu; /usr/bin/rdate is dated 2/28/2010)

On NASLite I have verified that I can "Ping Remote Computer" (Tools & Utilities Menu) that's external (e.g. 12.203.....).

So, does NL2 specify a "-u" option (UDP protocol) ? What else could cause the TimeServer to not update ? ("Last Successful Synchroniztion" reports "UNKNOWN"; I have rebooted a few times and waited past 0:00 UTC.)

TIA.

In another thread (viewtopic.php?f=7&t=3753)

THANK YOU !

This solved my Internet Time Sync issue on first boot of the updated USB stick. (Had been running v2.65, and the problem was probably present since MUCH earlier.)

Speaking of ... this Forum's time clock is 13 minutes slow

Sorry to continue an old topic...

Since I started using NasLite, the timeserver sync NEVER worked. It annoys me that my resync times are so far off the real time, the time they're supposed to resync.

Reading this topic, I noticed that time sync works through port 37, so I opened port 37 in the firewall of XP for 192.168.1.111 (Box I), 192.168.1.112 (Box II), 192.168.1.3 (WinXP).
As you can see below, I am using the NL prescribed timeserver. What am I doing wrong, what can I do?

Thanks for answering, solving this issue



--
P.

I use 216.171.124.36.

Go to http://tf.nist.gov/tf-cgi/servers.cgi and pick a server near you ... and report back

(The NL recommended one is shown as "All services busy, not recommended" at the above link.)


P.S.: Speaking of ... (again) ... this forum's time clock is now REALLY slow (behind) ! ( By my calculation 1 hour and 36 minutes. )

There is no server 'near', since I am - right now - located in The Netherlands.... But OK, I'll give it a try :-)
It is a pity that NL only accepts one numeric URL, and not capable of using the alpha-numeric pool address: 0.pool.ntp.org - for instance.

--
P.