Re: RN626x: Security database on the server does not have a computer.... error

JumpM8 · ‎2021-03-22

Hello all,

So I am having a really weird issue with my Netgear. It was working fine than all of sudden I can't connect to any of my folders and gives an error of "The security database on the server does not have a computer account for this workstation trust relationship". It's conencted via AD and when I try to rejoin the domain and it will usually error out but when it sucessfully joins I still get the same error.

The really weird thing is most of the time while it's trying to join the domain, it starts to work again. The moment it errors out or even successfully joins, than it stops working and I get that error message. If I keep doing it over and over, it'll eventually work but sooner or later we lose access again in the near future.

Need help to figure out what is going on.

Thank you

StephenB · ‎2021-03-22

One cause here is the date and time settings.

So maybe start by checking that the date and time on both the NAS and the PC are correct (including checking that daylight savings time change was applied to both the NAS and the PC).

JumpM8 · ‎2021-03-23

Date and time are correct, it's syncing with our domain controller.

StephenB · ‎2021-03-23

Time is correct on both the NAS and the PC?

There are a couple of other suggestions here: https://www.minitool.com/news/security-database-on-server-doesnt-have-computer-account.html

rn_enthusiast · ‎2021-03-24

Check that the NAS machine account is not duplicated somewhere in AD.

Un-join from AD > delete the NAS machine account in AD > check that no other machine accounts exists in AD with that same name > Re-join NAS to AD.

It sounds like a machine account issue to me, somewhere in AD. It could also be DC sync issues perhaps. There are no sync issues with the DCs? You can force a sync as well, I believe MS calls it "replication".

JumpM8 · ‎2021-03-25

I've already deleted it from AD and rejoined but still same issue. No sync issues from our DC. Right now it's working but for how long no one knows. It stopped worked after a week, we'll see how long this one last.