Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 3 subscribers
  • Views 16797 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

Netsupport School

DanielWest

Hi

I am having trouble with Sophos Antivirus and NetSupport School. I have NetSupport School running in a classroom. There is 14 student machines and 1 tutor machine. The tutor machine has Netsupport School Tutor installed and the student machines have NetSupport School Client installed. The Tutor machine connects to the student machines for classroom management purposes.

Now this all worked fine untill we installed Sophos Antivirus on all student and tutor machines, after that the Tutor machines can not connect to the student machines. I have tried adding exceptions the the NetSupport School applications, disabling on-access scanning and even disabling all sophos services and nothing works. If I then uninstall Sophos and restart, everything works. Please Help.

:5453


This thread was automatically locked due to age.
  • 0

    Hello,

    you did not install the firewall component - did you? What exactly is can not connect? Do you get any error messages? If so, please specify. If not - do you notice some other different behaviour like (part of) an application unresponsive?

    As you (think you) have disabled almost everything related to Sophos I think you better call support (unless you want to wait if others speak up in this forum).

    Christian

    :5455
  • 0

    Thanks for you reply QC

    I have not installed the firewall component, as I downloaded the version without it. Windows Firewall is disabled too. By "can not connect" I mean the tutor app runs, and scans the network based on their computer name, when you have selected your desired computers, the tutor app makes a connection to those machines and can perform tasks such as lock thier desktop, restart their machine, run tests, remote desktop etc

    I have not noticed any error messages and sophos doesn't log any errors. There is no different behaviour being displayed other than when it gets to the point where the tutor machine makes its connection to the clients, it fails.

    I forgot to add I am running Windows 7 64-bit.

    :5457
  • 0

    Thanks for the kudos (although I don't think I deserve it - yet).

    as I downloaded the version without it  Downloaded which version from where? It can make a difference whether it is 7.x, 9.0 or 9.5. Apart from that the settings (defaulted  or set by a policy) could suppress a desktop notification by/from SAV. But suppressed alerts shouldn't be the problem at all as you say you have disabled "everything" (both tutor and student?).

    Check SAV.txt in C:\ProgramData\Sophos\Sophos Anti-Virus\Logs on all machines (from your description I don't expect you'll find something there).

    Wild guess: If Netsupport has some built-in security features it and SAV might step on each other's toes ... As I said, there's always Support for the really complicated cases :smileywink:

    Christian

    :5461
  • 0

    We use NetSupport School with our Sophos, but I did have to allow it in Application Control i believe.  It's been a while.  Since it uses a remote control protocol, Sophos stops it by default.

    :5563
  • 0

    Since it uses a remote control protocol, Sophos stops it by default.

    I beg to differ :smileyhappy:. Not only is Application Control disabled by default but all applications are initially authorized. Thus two actions are needed to block an application. It might be that NetSupport School is detected as NetSupport Manager - which is on the list - but you should at least see an alert even if desktop messaging is disabled.

    Christian

    :5572
  • 0

    I know this thread is an old thread, but through some troubleshooting with Sophos, it was determined that if you disable the Sophos Network Threat Protection in the services of the affected machine, this will fix the issue.  Sophos is looking into the issue further as well

    :57345