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

Could not find a source for updated packages

Version: Sophos Enterprise Console 4.7

Firewall disabled on clients, server update share accessible via UNC path.

The SophosUpdateMgr account is local to the SEC server (call avserver ).

On the Enterprise Console, from which the command to deploy the client was issued:

6/22/2011 4:14:36 PM     fffffffd  This computer is not yet managed. It is protected but has not yet reported back its status.

Installation failed.

Date/time                Code      Description

On the client, in alc.log:

AutoUpdate finished
Downloading phase completed
ERROR:   Could not find a source for updated packages
Could not connect to the server. Check that this computer is connected to the network and that Sophos AutoUpdate is configured to update from the correct location with the correct credentials and proxy details (if required)
Downloading product Sophos AutoUpdate from server \\avserver\SophosUpdate\CIDs\S000\SAVSCFXP\
Could not add a connection to server \\avserver\SophosUpdate; user .; Windows error 1326
Could not connect to the server. Check that this computer is connected to the network and that Sophos AutoUpdate is configured to update from the correct location with the correct credentials and proxy details (if required)
Downloading product SAVXP from server \\avserver\SophosUpdate\CIDs\S000\SAVSCFXP\
Could not add a connection to server \\avserver\SophosUpdate; user .; Windows error 1326
Could not connect to the server. Check that this computer is connected to the network and that Sophos AutoUpdate is configured to update from the correct location with the correct credentials and proxy details (if required)
Downloading product RMSNT from server \\avserver\SophosUpdate\CIDs\S000\SAVSCFXP\
Could not add a connection to server \\avserver\SophosUpdate; user .; Windows error 1326

***************          Sophos AutoUpdate started          ***************

:14245


This thread was automatically locked due to age.
  • Hello deskadmin,

    searching for 1326 in this board would have helped you finding the answer. 1326 means incorrect credentials, i.e. either username or password in the updating policy are wrong or the user (SophosUpdateMgr) is locked out.

    Christian

    :14247
  • I just had the same issue. As its not perfectly clear here, the script you use MUST have a username and password. Doesnt matter about share permissions (such as everyone). The username and password provided in your "install sophos" script actually get put into the program itself. They are not just used at install time as I was led to believe by the phrasing of the article. This user is used for updates and is saved under Configure -> updating in the program.

    -user and -pwd at sophos client install time are REQUIRED parameters to get updates on the domain.

    :45905