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
  • I'm having a similar problem.

    A previous network engineer has installed Sophos onto our mail server which works fine. Now that I come to install Sophos onto a windows 7 machine I find that it can't connect to the server for updating.

    Upon further inspection I found that there was no SophosSAU*0 account. I added one for my machine name but still no joy.

    Should Sophos have created this account automatically, and if not - what could be the cause.

    Also if it didn't create the account and I simply made one in the same group as the working account - should it now work.

    Is it likely that I'm looking in completely the wrong place for solutions?

    :290
Reply
  • I'm having a similar problem.

    A previous network engineer has installed Sophos onto our mail server which works fine. Now that I come to install Sophos onto a windows 7 machine I find that it can't connect to the server for updating.

    Upon further inspection I found that there was no SophosSAU*0 account. I added one for my machine name but still no joy.

    Should Sophos have created this account automatically, and if not - what could be the cause.

    Also if it didn't create the account and I simply made one in the same group as the working account - should it now work.

    Is it likely that I'm looking in completely the wrong place for solutions?

    :290
Children
No Data