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

    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
Reply
  • 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
Children
No Data