Differences

This shows you the differences between two versions of the page.

--- the_ntp_functions [2017/03/17 19:02] – [Synchronising Clients] walkeradmin
+++ the_ntp_functions [2017/03/18 13:27] – [to do] walkeradmin
@@ Line 176: / Line 176: @@
 ----
 ==== Synchronising Clients ====
+\\
+** LINUX **
+\\
 \\
 Synchronising <color #ed1c24>Linux</color> clients is pretty much the same as we have already done, except in the <color #ed1c24>/etc/ntp.conf</color> instead of putting internet time servers, you just enter the internal IP address of your NTP server.
 \\
 \\
-For <color #ed1c24>Windows</color> PCs we will have to set the NTP server in the time settings.
+** WINDOWS **
+\\
+\\
+For <color #ed1c24>Windows</color> PCs we will have to set the NTP server in the time settings. To do this, first right click the clock in the bottom right hand side of the screen.
+\\
+\\
+{{:ntp01.jpg?400|}}
+\\
+\\
+Select 'Adjust date/time'
+\\
+\\
+When the next page opens, scroll down.
+\\
+\\
+{{:ntp02.jpg?700|}}
+\\
+\\
+Select 'Additional date, time, & regional settings'
+\\
+\\
+When the next page opens.
+\\
+\\
+{{:ntp03.jpg?700|}}
+\\
+\\
+Select 'Set the time and date'
+\\
+\\
+On the next page.
+\\
+\\
+{{:ntp04.jpg?400|}}
+\\
+\\
+Select the 'Internet Time' tab.
+\\
+\\
+On the next page.
+\\
+\\
+{{:ntp05.jpg?400|}}
+\\
+\\
+Select the Change Settings button.
+\\
+\\
+On the next page we will see a box that contains <color #ed1c24>time.windows.com</color>
+\\
+\\
+{{:ntp07.jpg?400|}}
+\\
+\\
+Change the contents of this box to the IP Address of the Raspberry Pi running the NTP server.
+\\
+\\
+Finally, Click the <color #ed1c24>Update</color> Button.
+\\
+\\
+{{:ntp08.jpg?400|}}
+\\
+\\
+The time should now be updated, you will see confirmation in this page (I have to do this twice sometimes)
+\\
+\\
+That's it.
+\\
+\\
+----
+==== Clients over 1000 Seconds out of time ====
+\\
+“NTP won’t normally reset the clock if it’s off by more than 1000s. If you run:
+<file>
+ntpd -gq’
+</file>
+It ignores the clock being way adrift from ntp time and will force it to be correct then close. The old ntpdate program does the same thing.”
+\\
+\\
+Credit: [[http://www.raspberrypi.org/phpBB3/viewtopic.php?f=91&t=16058|External Link]]
+\\
+\\
 ----
+==== Raspberry Pi Dropping of Wireless Network ====
-==== to do ====
+I found my raspberry Pi Zero, that is using the official Raspberry Pi Wireless Dongle drops off the wireless network after around a week. Only a reboot gets it back (as I have no keyb/mouse connected) so I figured just using Cron to reboot the thing every 24 hours will be a suitable work around.
+\\
+\\
+To use cron (should already be installed):
+\\
+\\
+    sudo crontab -e (reboots require super user rights)
+\\
+Insert the following line:
+\\
+\\
+0   *   *   *    /sbin/shutdown -r
+\\
+Explanation:
+\\
+\\
+<file>
+m      h    dom        mon   dow       command
+minute hour dayOfMonth Month dayOfWeek commandToRun
-wireless dropping out on ntp server
+so the line
+0   *   *   *    /sbin/shutdown -r
+would reboot your system every day at 00:00.
+</file>
+\\
+Use Ctrl+X, Y, Enter. This will save and exit crontab (if using nano)
+\\
+\\
-clients over 1000seconds out
-“NTP won’t normally reset the clock if it’s off by more than 1000s.
-If you run ‘ntpd -gq’ it ignores the clock being way adrift from ntp time and will force it to be correct then close. The old ntpdate program does the same thing.”
-credit: I found it here earlier today when I was searching on some raspi NTP issues
-http://www.raspberrypi.org/phpBB3/viewtopic.php?f=91&t=16058
-Reply