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
  • Dear Patric,

    What i can suggest is in the updating policy change the username and password. Create one dedicated account for sophos auto update and use the same account in the updating policy.  After changing the credentials in the updating policy, you have to make sure that your clients has taken the policy.  Also you have to make sure that your subscribed package is downloaded and CID is updated.  Also you have to make sure that the below services are running.

    1. Computer Browser Service

    2. Workstation and Server Service

    3. Remote Registry Service

    4. Task Scheduler serveice.

    If this doesnt works go to c:\programfiles\sophos\Autoupdate in a client machine and open cache folder and delete the contents of the folder and check whether clients could able to connect to server or not. 

    If still you have the same problem please provide me the update log files.  please feel free to get back to me i will try to help you out in resolving this issue.

    Regards,

    Ramki.

    :113
Reply
  • Dear Patric,

    What i can suggest is in the updating policy change the username and password. Create one dedicated account for sophos auto update and use the same account in the updating policy.  After changing the credentials in the updating policy, you have to make sure that your clients has taken the policy.  Also you have to make sure that your subscribed package is downloaded and CID is updated.  Also you have to make sure that the below services are running.

    1. Computer Browser Service

    2. Workstation and Server Service

    3. Remote Registry Service

    4. Task Scheduler serveice.

    If this doesnt works go to c:\programfiles\sophos\Autoupdate in a client machine and open cache folder and delete the contents of the folder and check whether clients could able to connect to server or not. 

    If still you have the same problem please provide me the update log files.  please feel free to get back to me i will try to help you out in resolving this issue.

    Regards,

    Ramki.

    :113
Children
No Data