Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 28 replies
  • Subscribers 1 subscriber
  • Views 39393 views
  • Users 0 members are here
Options
Suggested
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

Sophos v10 & Dameware!

k3i1kp

Hello:

I have same problem discussed in this topic:

http://forums.dameware.com/viewtopic.php?f=17&p=7323

I worked on this subject and I know that this problem occur because of Sophos Antivirus

also I contact with Sophos customer service and they are searching for a solution.

we are working hard and we find many things about this stuck:

-          there is no system log or windows event about windows service conflict, windows firewall  or Sophos firewall error.

-          we are monitoring in/outbound traffic on client and remote pc so find the connection is established but remote screen not shown.

-          There is issue while Sophos Services are stopped.

-          Just after uninstalling Sophos problem solved and there is no issue.

-          this stuck occur on windows XP clients and not occur on windows 7.

-          There is no issue in computers with Sophos Antivirus v9.x we find that this occur after upgrading to Sophos v10.

-          We test on clients installed Sophos Endpoint Security with firewall module and without firewall.

installed Sophos Endpoint Security 10 with Dameware Mini Remote Control 7.5 in Domain and Workgroup mode.

Thanks,

:20673


This thread was automatically locked due to age.
Parents
  • 0

    HI,

    The reason that you will not see it in version prior to 10 is that, web scanning on the client was previously done by a Browser Helper Object (BHO) (http://en.wikipedia.org/wiki/Browser_Helper_Object).  This obviously only worked with IE as this is an IE only extension platform.  To make client based web scanning less browser specific, Sophos now uses a Layered Service Provider (LSP) (http://en.wikipedia.org/wiki/Layered_Service_Provider).

    It's not that Sophos has broken something that previously worked but they have changed the technology which in turn I assume leads to this problem,  As Sandy mentions, Sophos have investigated the issue and aren't doing anything wrong and I have no eason to doubt that, as just being where they are in the networking stack means that when removed the problem goes away so at first glance it looks like a Sophos problem.  

    I've heard that a change might be going in to an upcoming version of SAV to work around the issue, but rather than a fix, it's more of a change to help the two applications co-exist.  

    Regards,

    Jak

    :27433
Reply
  • 0

    HI,

    The reason that you will not see it in version prior to 10 is that, web scanning on the client was previously done by a Browser Helper Object (BHO) (http://en.wikipedia.org/wiki/Browser_Helper_Object).  This obviously only worked with IE as this is an IE only extension platform.  To make client based web scanning less browser specific, Sophos now uses a Layered Service Provider (LSP) (http://en.wikipedia.org/wiki/Layered_Service_Provider).

    It's not that Sophos has broken something that previously worked but they have changed the technology which in turn I assume leads to this problem,  As Sandy mentions, Sophos have investigated the issue and aren't doing anything wrong and I have no eason to doubt that, as just being where they are in the networking stack means that when removed the problem goes away so at first glance it looks like a Sophos problem.  

    I've heard that a change might be going in to an upcoming version of SAV to work around the issue, but rather than a fix, it's more of a change to help the two applications co-exist.  

    Regards,

    Jak

    :27433
Children
No Data