• Computer Clock Is Not Synchronized (code 3000)
    I've been having the same problem recently. Many of the endpoints that have this error are on an Active Directory domain and receive their time from the DC. But even right after I get the error stating the time of off by over 2 hours, I connect to the endpoint and can confirm the time is under 5min skew of UTC. So I'm really confused by this. I contacted Wasabi and they said there's really nothing they can do, nor did they see any errors on my account that would help diagnose the problem.