Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 28 replies
  • Subscribers 1 subscriber
  • Views 39381 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.
  • 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
  • 0

    Sophos support said to me that this would be resolved in 10.0.7. But then again they said that for 10.0.6!

    :27443
  • 0

    Thanks for the explanation Jak hopefully Sophos gets the "coexistance" issue resolved as Dameware is used heavily in many corporations but I'm somewhat surprised that this didn't get caught in QA testing.  I'd imagine this is affecting a lot of installations.  With that said kudos to Sophos for making the web content scanning less browser specific as you mentioned.

    :27473
  • 0

    Hello Sandy

    The position of Sophos might be correct from your perspective, but I as a user of Sophos feel "alone in the rain" - and there is the point, I cannot understand Sophos!

    We are all faithfull Sophos-users and we have a problem, that occures with a new version of your product. Personally I think, it would be professional and really customer oriented, if Sophos would work directly together with Solarwinds to resolve the issue and fix this for us, your users.

    -> We as Sophos users do not feel having done anything wrong in using Dameware together with Sophos Antivirus - but I feel treated a bit like that from your answer...

    Thank you again for bringing that again up to your developpers and solving this issue for us ;-)

    Kind regards

    David

    :27739
  • 0

    Hello David,

    I can understand your feelings (and just to avoid misconceptions - I'm not Sophos, and I'm also not a DameWare user). Reading the knowledgebase article and the thread in the DameWare forum the issue seems indeed not not be restricted to SESC 10.x. I also don't have the impression that Sophos didn't (at least try to) contact DameWare/solarwinds.

    Sure, the problem and its solution look simple enough - it came with v10 so Sophos should reverse the changes to make it work again. The changes have probably not been introduced just for the fun of it - and it might just not be possible to work around the DameWare issue and keeping the changes at the same time. Just because the problem became apparent with v10 doesn't mean that the fault doesn't lie somewhere else. And you can't expect that Sophos withholds (probably necessary) changes indefinitely from other customers for this reason.

    LSP is tricky - and while it has been around for quite some time the recently modified Wikipedia article still starts the Details section with a quote from Microsoft's System Journal May 1999 issue the Winsock 2 SPI is relatively unexplored. Increased use of the SPI might have - as it seems to be the case - unexpected side effects on applications which make specific assumptions on the network.

    BTW: Do you have a statement from DameWare?

    Christian

    :27767
  • 0

    Hi,

    I solved the problem by installing:

    WinsockxpFix.exe then run "Fix" the program cut the network connection then a reboot is required.

    Test connection with dameware successfully on 2 PCs XP

    Hope this help

    Best regards,

    :28003
  • 0

    Has anyone else tried windsockXPfix.exe

    :28567
  • 0

    HI,

    If you've installed 10.0.7 and rebooted, this conflict may no longer be a problem:

    http://downloads.sophos.com/readmes/sesc_100_rneng.html

    • (DEF78282) The Sophos web protection Layered Service Provider stops remote desktop connections being made from Dameware Mini Remote Control 7.5.

    Regards,

    Jak

    :28569