I find it hard to think of any time issue would affect DHCP unless your server is part of an LDAP or AD Domain.
Assuming your DHCP server is “standalone”
You should be able to just re-configure your system time and although shouldn’t be needed if it makes you feel better to reboot.
You can easily make your change using YaST > System > Date & Time.
Double-check and be certain your time zone is correct, it’s a common cause of an incorrect offset. This must be set correctly or all your time settings will be thrown off (and things like using NTP won’t help).
In the UNIX®
world – and therefore, Linux also – the System Time [Hardware Clock] (for PC based systems, the BIOS clock) is usually set to UTC. 1. For the Redmond world, the System Time is normally set to Local Time «but
, there’s a Registry value which can be changed to line up with the UNIX® world» …
[HR][/HR]Why set System Time to UTC?
If the System Time is set to UTC then, all the Time Stamps (at System level) are UTC. Usually, when the user queries a Time Stamp, a value corrected to the Local Time is displayed.
This means that, across all the networked systems, regardless of where they are on Planet Earth or, in Outer Space, the Time Stamps are consistent – across ALL
systems …
[HR][/HR]In your case, Time Stamps “off” by 2 hours is similar to what happens when, Central European Summer Time is being compared against UTC …