KoolTech Posted June 12, 2014 Posted June 12, 2014 Hi, I have recently moved our Sophos Enterprise Console onto a new Server 2008 rt machine and it all seems to be working except for the update policy. I have the policy set to update from the recommended location and have our Administrator account for the username and password. Is this correct? This is a copy of the updating log as well. I assume I am using the wrong credentials or something similar. Time: 12/06/2014 09:23:31 Message: 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) Module: CIDUpdate Process ID: 7952 Thread ID: 8820 Time: 12/06/2014 09:23:31 Message: Downloading product Sophos AutoUpdate from server \\[sERVERNAME]\SophosUpdate\CIDs\S000\SAVSCFXP\ Module: CIDUpdate Process ID: 7952 Thread ID: 8820 Time: 12/06/2014 09:23:31 Message: Could not add a connection to server \\[sERVERNAME]\SophosUpdate; user Administrator; Windows error 1326 Module: CIDUpdate Process ID: 7952 Thread ID: 8820
jonnykewell1 Posted June 12, 2014 Posted June 12, 2014 If you pop that URL into a web browser, can you get to the page and login with those credentials? You should then see the files it needs to download?
sted Posted June 12, 2014 Posted June 12, 2014 personally i wouldnt use administrator as all the user needs is read access to \\server\SophosUpdate anyway and iirc it stores the password you use in the registry of client pcs so if you use the admin account it may be possible for someone to retrieve your admin password to me it looks like youve typod the password or the user dosent have access to the share (or the share dosent exist) also with administrator specifically wont that try and upadte using the local pcs administrator account rather than domain\administrator? the same as on a win7 box typing in administrator cghanges the logon domain to that pc rather than the domain. First thing id try is create a user called sophosupdate or something as a domain user give it access to the share and try that as the update account AND makes sure the box is filled in domain\sophosupdate not just sophosupdate
KoolTech Posted June 12, 2014 Author Posted June 12, 2014 @sted thanks for that. Is the Sophos Update Manager account suitable for this? I had tried the account with domain\username as well hence the change to see if it would work! Does the update account only need read access to the sophosUpdate folder?
sted Posted June 12, 2014 Posted June 12, 2014 @sted thanks for that. Is the Sophos Update Manager account suitable for this? I had tried the account with domain\username as well hence the change to see if it would work! Does the update account only need read access to the sophosUpdate folder? as far as i remember yes its one of those things i do without thinking and i still use the old emlibuser1 account name for ease of memory and ive just checked its just a member of domain users thats it 1
KoolTech Posted June 12, 2014 Author Posted June 12, 2014 @sted thats the one mate!! Knew it would be something simple I was just going round in circles, cheers mate
sted Posted June 12, 2014 Posted June 12, 2014 @sted thats the one mate!! Knew it would be something simple I was just going round in circles, cheers mate no problem weve all been there
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now