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

Protect client computer failed "waiting for response from computer"

Hi there,

I'm a newer, and I'm using Sophos Enterprise Console to protect the client computer.  Enterprise Console version is 4.7..., and the version of  EndPoint antivirus I'm planing to setup to client computer is 10.0. 

When I protect the client computer, I can choose "FireWall", "Compliance Control", "Patch" and "Third-Party security software detection".   Except the "Compliance Control" I choosed the other three, and the client computer can be reached, but after a little while, there will be an error:" Waiting for response from computer".

Does anyone know this reason?

Thanks  a lot.

:34599


This thread was automatically locked due to age.
  • HI,

    Firstly, are you able to upgrade SEC 4.7 to SEC 5.1, there were a couple of significant changes that help with the ability to deploy.

    Regards,

    Jak

    :34605
  • Hi Jak,

    Thanks for your reply.

    I tried to upgrade SEC 4.7 to SEC 5.1, but it failed, the error is "Failed to get the handle for MSSQLSERVER service. OpenService return: 1060 - The specified service does not exist as an installed service."

    Does it because I'm using SEC 4.7 to deploy?

    Thanks,

    Nancy

    :34623
  • Hi,

    I don't think that message in the bootstrap log is fatal, it's more of a check.

    If you look further down to where setup.exe calls the MSIs (database, server, console) does one of those return failure?  If, so the MSI log for each component is in the same directory (check the timestamps to ensure they are the latest or oder by last modified).  Maybe you could make that MSI log available.  If you can't make it all available somewhere to dowload as it's too large.  Search from the bottom up for the text:

    Return value 3

    Then paste here 15 ish lines above that, that might show roughly what failed and why.

    http://www.sophos.com/en-us/support/knowledgebase/114627.aspx is the landing article for this sort of problem and you might find a solution via that depending on the error.

    Regards,

    Jak

    :34631