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 contact server" error

We are evaluating Sophos ESDP and will purchase it if it works as needed. Our network is a win2k8 domain. On all of the systems that I've deployed the Endpoint security and control client from Enterprise Console they are getting the 'Could not contact server' error message when it tries updating so the client is disabled. I've deployed it to XP, wink3, win2k8, win2k8 r2, vista, and win7 and none worked. One of the win2k8 r2 server didn't work then about a day later it started updating and working on it's own. Nothing was changed on that system from the time it wasn't working until it did work.  I saw a knowledgebase article about adding the local SophosSAU*0 user to the local 'User's group. I did that and it still doesn't work. That is not an acceptable answer in the first place since the whole point of a centrally managed system is that we should NEVER have to touch the client/workstation. It should all be done centrally from  Enterprise Console, group  policy and/or System Center. If I ever have to touch the workstations to make this work and maintain except on the rarest of occasions then your product is a no go. I've also turned off the firewalls to test and it's still not working. Speaking of firewalls, what ports does the system use to communicate that need to be opened.

Thanks,

Patrick

:68


This thread was automatically locked due to age.
Parents
  • Hi Oliver,

    We should probably have different threads for these issues, but...

    Note.  If the SophosSAU*0 account was missing, you should remove Sophos AutoUpdate, and reinstall from the setup.  This is created on installation and generates a random password, which is stored in the registry.  Creating a new account will not work.  So I would fix this first.

    When dealing with "could not contact server", you need to know where its updating from and which exact part is failing (or all).

    Can you tell us your primary/secondary server details ? (without username/passwords)

    If you update from work & home, its likely you will have a network locate (\\server\share\..) address as Primary and Sophos as secondary, is this the setup ?

    Once you know this, check the update log

    - SAV 7 - Right click shield, Configure updating, Logging [tab], View log file

    - SAV 9 - Right click shield,Open Sophos Endpoint..., View update log

    Now there are two stages, the update stage and the installation stage.

    Could not contact server is going to be the download stage, but is it all components (SAVXP, RMS, SAU), or just one ?

    If it is failing accessing a CID (UNC) path, this should give a valid windows errors code, and you can work from there.

    e.g. 1326 = unknown username or bad password.

    If it is updating from Sophos only (http), then this will be a little harder to troubleshoot.

    Let us know what you find :)

    OD

    :304
Reply
  • Hi Oliver,

    We should probably have different threads for these issues, but...

    Note.  If the SophosSAU*0 account was missing, you should remove Sophos AutoUpdate, and reinstall from the setup.  This is created on installation and generates a random password, which is stored in the registry.  Creating a new account will not work.  So I would fix this first.

    When dealing with "could not contact server", you need to know where its updating from and which exact part is failing (or all).

    Can you tell us your primary/secondary server details ? (without username/passwords)

    If you update from work & home, its likely you will have a network locate (\\server\share\..) address as Primary and Sophos as secondary, is this the setup ?

    Once you know this, check the update log

    - SAV 7 - Right click shield, Configure updating, Logging [tab], View log file

    - SAV 9 - Right click shield,Open Sophos Endpoint..., View update log

    Now there are two stages, the update stage and the installation stage.

    Could not contact server is going to be the download stage, but is it all components (SAVXP, RMS, SAU), or just one ?

    If it is failing accessing a CID (UNC) path, this should give a valid windows errors code, and you can work from there.

    e.g. 1326 = unknown username or bad password.

    If it is updating from Sophos only (http), then this will be a little harder to troubleshoot.

    Let us know what you find :)

    OD

    :304
Children
No Data