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

Client PCs not getting managed

I have a number of PCs that are not manageable from the console. It may be more than one issue, so I am looking at the moment at just one client:

Server: Windows SBS 2011, Sophos Enterprise Console 5.2.0.644

Client: Windows 7 Pro, Endpoint Security and Control, 10.3

Running "Sophos network communications report" from the client gets this:

  • Sophos Anti-Virus cannot report to the Sophos management console or receive new security policies.
  • This is because it is using an SSL certificate that is incompatible with the Sophos management console.
  • This may be caused by the server having been reinstalled.
  • Sophos Anti-Virus should be reinstalled by the system administrator.


I came across this article, and so checked the server and client time, and they are identical to the second.
https://www.sophos.com/en-us/support/knowledgebase/17266.aspx

I re-installed the client software - uninstalling all Sophos products from the client, restarting the PC, then running this:
\\<ourserver>\SophosUpdate\CIDs\S000\SAVSCFXP\setup.exe

This gives me in the list of installed programs:

  • Sophos Anti-Virus
  • Sophos AutoUpdate
  • Sophos Remote Management System

... and I can see 7 Sophos services are running (Sophos Web Intelligence upsdate is not).

Following advioce on another webpage, I have added an exception to the client firewall to allow connections to port 8192. From the client I get an IOR response when telneting to port 8192 on the server. Going the other way I get "Connect failed". However, this is also the case if I try to connect to a client that is managed however, so is not a use diagnostic indicator.

Can anyone help me?

:57503


This thread was automatically locked due to age.
Parents
  • Hello F2Andy,

    Sophos Web Intelligence update is not [running]

    this is correct, it's only running for a short time when an update could be necessary

    port 8192

    responds with the IOR which by default directs the endpoint to port 8194 on the same server. Ideally the server should be able to connect to port 8194 on the endpoint (the endpoint's 8192 is not used). You should start with the Router log on the endpoint.

    Christian

    :57505
Reply
  • Hello F2Andy,

    Sophos Web Intelligence update is not [running]

    this is correct, it's only running for a short time when an update could be necessary

    port 8192

    responds with the IOR which by default directs the endpoint to port 8194 on the same server. Ideally the server should be able to connect to port 8194 on the endpoint (the endpoint's 8192 is not used). You should start with the Router log on the endpoint.

    Christian

    :57505
Children
No Data