OmniOS r151038 LTS with nappit 22.01b sets wrong time on joining an Active Directory domain [SOLVED]

amp

New Member
Aug 24, 2016
15
0
1
45
I upgraded our r151030 LTS to 151038 LTS and am experiencing an error on re-joining the domain, as there is a too big time skew of 1 hour.

Actually the system time is correct when i check with "date", in my case it was 16:30h . The TZ is set to Europe/Berlin via "tzseclect".

I am trying to re-join the domain via nappit 22.01b. In this screenshot you can see that when the timesync is done with the ad-server the date is changed to one hour later (17:30) and thus the join domain fails. The AD server is synced with external NTP Servers and is set to the same TZ (Berlin).

2022-03-20_16-34-45.png

I wonder if you can help me on this issue.

Thanks, Alex
 
Last edited:

amp

New Member
Aug 24, 2016
15
0
1
45
Just as a follow-up: i was finally able to join the domain when i disabled the step1 additional timesnyc with the AD server, thanks to @gea who gave me the hint to comment our some lines in the join script.

So then joining was successful, i still don't know why the time of the server switched in this proces..
 

gea

Well-Known Member
Dec 31, 2010
2,809
970
113
DE
If you run your server under ESXi, check ESXi date and time as vmware tools want to sync time with ESXi.
 

amp

New Member
Aug 24, 2016
15
0
1
45
Hi gea, no this is a bare metal setup. I also checked in the BIOS is it had the wrong time but no. I just guess it might be due to some daylight savings setting which are not correctly interpreted.