This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

"SophosSAU <hostname>" account locks out.

I am having problems with downloading the latest Updates from the SophosUpdate share.

If I click on the Blue Sophos Shield in the system tray and select "Update Now" I get a message saying "Could not contact Server".

In Active Directory Users and Computers the "SophosSAU" account which is used for downloading of Sophos updates becomes locked out each time I try to do an "Update Now" and the Sophos Blue Shield in the system tray has a red cross in it indicating that updating has failed.

In the "C:\Program Files\Sophos\AutoUpdate\logs\alc.log" there are references to
"There was a problem while establishing a connection to the server. Details : LogonUser ("SophosSAU-hostname",".",...) failed A Windows API call returned error 1326".

Now a confession : everything was working fine, but then I had to change the password hashing algorithm I use on this Server.

My guess is that the "SophosSAU" account or its password have been affected by this change, but I'm not sure what to do next. I tried re-installing by doing a "Protect Computers" from the "Enterprise Console" but that made no difference.

Any advice gratefully received.

Peter

:16469


This thread was automatically locked due to age.
Parents
  • Slight correction to my last post :

    the "SophosSAU<servername>1" account does exist in Active Directory now. I just needed to Refresh the display.

    I've got a "SophosSAU<servername>2" account as well now following another attempt at throwing away the AutoUpdate\Service key and re-protecting.

    Still doesn't work though.

    :16503
Reply
  • Slight correction to my last post :

    the "SophosSAU<servername>1" account does exist in Active Directory now. I just needed to Refresh the display.

    I've got a "SophosSAU<servername>2" account as well now following another attempt at throwing away the AutoUpdate\Service key and re-protecting.

    Still doesn't work though.

    :16503
Children
No Data