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

    Would like to know if anyone manages to solves this. I can also confirm that for Win XP, dameware with sophos v10 is not working. It is also not working with Win Server 2003. Did a test and from what i saw, it seems the host pc is connected as can be seen from the connect dialog box and the change of wallpaper on the client pc but still see white screen on host pc with the word "Initializing settings"

    This however works on Win 7.

    Downgrading v10 to v9.5 does not work as work if an uninstall is not performed in the first place.

    From what I can see, definitely not a dameware issue.

    Please fix this sophos peeps.

    :26085
  • 0

    Several weeks ago I performed some testing with Sophos on a newer version of LSP (Layered Service Provider ) and this resolved the Dameware problem during the testing. I'm hoping this newer LSP will eventually make it into production and be released in a later version of v10. 

    Fingers crossed!

    :26095
  • 0

    Hi All,

    Sophos have pretty much shut the door on me regarding this issue
    and advised me to seek assistance from Dameware instead. For those
    interested I have logged a case with Dameware : Case # 354954

    They (Dameware/Solarwinds) have been in touch and I sent them some
    packet captures (Wireshark) comparing a working connection (to Sophos 9.7)
    against a non-working connection (to Sophos 10). I will update this thread
    if there is any usefull feedback.

    FWIW : I've also done some further testing with Sophos 10.0.4 and 10.0.5,
    the problem persists. I can still use any version of Dameware I want with
    Sophos 9.5/9.7 without issue. The moment I try any Sophos v10.x I cannot
    connect cleanly to Win XP and Server 2003 hosts. The testing is done to the
    same hosts, with nothing other than the version of Sophos changing.

    RogueViper : I'd be very eager to also test the LSP you were testing, how did
    you go about obtaining it and could we get access to it too?

    Roland

    :26239
  • 0

    Any News for this Problem?

    :26781
  • 0

    According to a member of the local infrastrucuture team this has now been resolved with the latest release of Sophos endpoint 10.0.6. Although I havn't had chance to test this myself yet. 

    :26809
  • 0

    Thanks for the info RogueViper.

    Just tested 10.0.6 and unfortunately for me it doesn't work... As far as Solarwinds are concerned I will follow up with them today/tomorow to see if they picked up anything usefull on their (Dameware) end and provide some feedback here.

    Roland

    :26815
  • 0

    Same here... no joy.  Dameware still requires a SEND > SEND REFRESH.

    :26835
  • 0

    Morning all,

    I have now gotten around to testing this myself this morning. I can confirm that a 'Send refresh' command from Dameware is still required before the session connects. 

    Mike

    :26859
  • 0

    Roland any luck with Dameware/Solarwinds ?

    Were having the exact same issue and would be curious to see what answer they give if any....

    :27195
  • 0

    After Sophos 10.0 was pushed all our XP clients are now stating "waiting on initial screen" - I have seen the "workarounds" for this issue.  I didn't have the issue prior to 10.0 being deployed and now any XP client - even on the same network, no latency are affected.  What is the status of this issue as Sophos seems to be blaming Dameware?

    :27427