I keep being panicked about it being later than I thought, only to be confused five minutes later when I check again and it's not as late as I thought.
-
I keep being panicked about it being later than I thought, only to be confused five minutes later when I check again and it's not as late as I thought. It turns out one of my computers has drifted ten minutes fast and hasn't picked up an NTP correction?!
-
I keep being panicked about it being later than I thought, only to be confused five minutes later when I check again and it's not as late as I thought. It turns out one of my computers has drifted ten minutes fast and hasn't picked up an NTP correction?!
@0xabad1dea rude! Hopefully easily fixable. ..
-
I keep being panicked about it being later than I thought, only to be confused five minutes later when I check again and it's not as late as I thought. It turns out one of my computers has drifted ten minutes fast and hasn't picked up an NTP correction?!
@0xabad1dea
I recently learned the hard way that DNSSEC requires a somewhat accurate clock (not really surprising, most network encryption does), which combined with ntpd using DNS to look up the ip addresses of ntp servers can create a catch-22 where neither DNS nor NTP works because the other one doesn't work.Though I don't know how much the time can be off before things start breaking, in my case it was off by a couple of months (my brother had set the clock manually after replacing the cmos battery and didn't notice that the bios was using middle endian date format).
-
I keep being panicked about it being later than I thought, only to be confused five minutes later when I check again and it's not as late as I thought. It turns out one of my computers has drifted ten minutes fast and hasn't picked up an NTP correction?!
@0xabad1dea TFW your own computers are gaslighting you even though you're not even running any LLMs…
-
I keep being panicked about it being later than I thought, only to be confused five minutes later when I check again and it's not as late as I thought. It turns out one of my computers has drifted ten minutes fast and hasn't picked up an NTP correction?!
@0xabad1dea I have a work laptop like that. It's 10 minutes ahead, even though it claims to automatically set the time via NTP. What's worse, because these settings are managed by an organization, Windows doesn't even let me set the clock manually to fix it.
Luckily, I also have a workstation that doesn't suffer from that issue that I use 99% of the time. The laptop is only needed for a few in-person meetings, but when I'm using it I'm also always thrown off by the wrong time.
-
@0xabad1dea I have a work laptop like that. It's 10 minutes ahead, even though it claims to automatically set the time via NTP. What's worse, because these settings are managed by an organization, Windows doesn't even let me set the clock manually to fix it.
Luckily, I also have a workstation that doesn't suffer from that issue that I use 99% of the time. The laptop is only needed for a few in-person meetings, but when I'm using it I'm also always thrown off by the wrong time.
@berglerma does the organizational management also prevent toggling automatic time updates off and back on? As that’s what unstuck it for me
-
@berglerma does the organizational management also prevent toggling automatic time updates off and back on? As that’s what unstuck it for me
@0xabad1dea Yeah you can't toggle that either. You can press the "Sync now" button, but that doesn't do anything
-
@0xabad1dea Yeah you can't toggle that either. You can press the "Sync now" button, but that doesn't do anything
@berglerma @0xabad1dea If the laptop is part of a domain, it'll automatically sync time with domain controller (you can't have more than 5 minutes difference between client and server, otherwise Kerberos authentication won't work), so what almost certainly happened is that your work's DCs have wrong time, and they propagate it to all clients.
-
@berglerma @0xabad1dea If the laptop is part of a domain, it'll automatically sync time with domain controller (you can't have more than 5 minutes difference between client and server, otherwise Kerberos authentication won't work), so what almost certainly happened is that your work's DCs have wrong time, and they propagate it to all clients.
@jernej__s @0xabad1dea On the Workstation the time is correct, though, and that is part of the same AD domain.
-
@jernej__s @0xabad1dea On the Workstation the time is correct, though, and that is part of the same AD domain.
@berglerma @0xabad1dea Weird, could be just one server that somehow drifted, but that should cause problems on that server itself, too (assuming anybody pays attention).
-
@berglerma @0xabad1dea Weird, could be just one server that somehow drifted, but that should cause problems on that server itself, too (assuming anybody pays attention).
@jernej__s @berglerma I believe what happens is Windows can just get stuck and stop applying NTP corrections until you manually completely shut off and restart NTP checks.
-
R relay@relay.infosec.exchange shared this topic
