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

Longs start of .NET applications from network drive

Hello,

We are having problems with Sophos On-Access scanner. When enabled (always and default for every workstation in company) it can take up to 60-120 seconds before a .NET application located on network drive will start. It includes a single executable and around 10MB of DLL libraries which are located in same folder. If I disable On-Access scanning it opens instantly.

If I check the Task Manager I can see that Savservice.exe is peaking at around 20-40% which tells me that DLL files are beeing scanned. And this is taking way too long.

I tried to exclude the folders like so:

\\SERVER\SHARE\FOLDER\ and

X:\FOLDER\

or any other possible exclusion solution but none helped. When user closes application and starts it again from same network path it will open almost instantly. Until next reboot that is.

What can I do? How to correctly exlude those folder from beeing scanned or how to setup the Endpoint so the DLL files are not scanned everytime?

We are using Windows 7 Pro 64bit OS, Novell Netware file server and latest up-to-date version of Sophos Endpoint Security (9.7).

Thank you for your support.

:25101


This thread was automatically locked due to age.
Parents
  • I did some more tests. And so far I can confirm this is a problem with Sophos and Novell file system.

    I copied two of our .NET applications with DLL files onto our QNAP NAS which every user have mapped twice. Once for private and one for public folder on it.

    I copied the application into M:\Temp\APP1 and M:\Temp\APP2 and then excluded M:\Temp\ from Sophos. Also purged cache. Result? 1-2 second to copy from it to HDD. But when I input exclusion of Novell file server map Q:\FOLDER\ where two apps are in Q:\FOLDER\APP1 and Q:\FOLDER\APP2 it takes 3-4 minutes to copy/start them.

    So this at least for me confirms that Sophos has a bug and can't exclude properly the Novell file system shares. We are using Novell Netware 6.5 with service pack 8.

    I tried to exclude all options like so:

    Q:\FOLDER\

    \\SERVER\VOLUME\SHARE\FOLDER\

    \\192.1.1.1\VOLUME\SHARE\FOLDER\

    And with all three exclusions it failed. Maybe bacause of that it also takes that long to scan the DLL files?I also tried on two other computers with different AV software (MSE and AVG). Zero problems with them and Novell file system share exclution.

    How and where can I report this bug or do you have any other suggestions?

    :25183
Reply
  • I did some more tests. And so far I can confirm this is a problem with Sophos and Novell file system.

    I copied two of our .NET applications with DLL files onto our QNAP NAS which every user have mapped twice. Once for private and one for public folder on it.

    I copied the application into M:\Temp\APP1 and M:\Temp\APP2 and then excluded M:\Temp\ from Sophos. Also purged cache. Result? 1-2 second to copy from it to HDD. But when I input exclusion of Novell file server map Q:\FOLDER\ where two apps are in Q:\FOLDER\APP1 and Q:\FOLDER\APP2 it takes 3-4 minutes to copy/start them.

    So this at least for me confirms that Sophos has a bug and can't exclude properly the Novell file system shares. We are using Novell Netware 6.5 with service pack 8.

    I tried to exclude all options like so:

    Q:\FOLDER\

    \\SERVER\VOLUME\SHARE\FOLDER\

    \\192.1.1.1\VOLUME\SHARE\FOLDER\

    And with all three exclusions it failed. Maybe bacause of that it also takes that long to scan the DLL files?I also tried on two other computers with different AV software (MSE and AVG). Zero problems with them and Novell file system share exclution.

    How and where can I report this bug or do you have any other suggestions?

    :25183
Children
No Data