We're running a VM infrastructure of Windows Server 2008 R2 and Windows 7 clients. Our Management Server (mgmt1) is hosting the latest release of Sophos Enterprise Management Console.
All clients and other servers have successfully been added to the console and are happily receiving updates automatically. They are also happily checking for and receiving updates when asked to do so (right-click Sophos icon in taskbar, "Check for Updates".
All machines are pointing at mgmt1 as the primary source for updates, including the Sophos client on mgmt1. The server is 'airgapped' and not connected to the internet. Updates are copied manually on to the mgmt1 server from CD. Putting the server online is not an option and therefore the Sophos servers are not an option for providing updates.
However, server mgmt1 won't update itself. When the "Check for updates..." option is clicked, the dialogue box displays that it cannot connect to server (depsite the server being itself and all other machines configured in the same way work).
The update logs within the Sophos client give the following:
"There was a problem while establishing a connection to the server. Details: Logon User ("%username%" etc.) failed. A windows API call returned error 1311"
After lots of googling, we can find nothing relating to "error 1311". All usernames and passwords have been checked etc. The primary update server (mgmt1) is configured the same on all machines through 1 Sophos policy.
We're now a bit stuck. Why can the clients update successfully from mgmt1 but mgmt1 cannot connect to itself and update properly?
Thanks in advance.