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

Longs start of .NET applications from network drive

AndrejK

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
  • 0

    Hello AndrejK,

    exclusion on file filter *.dll

    didn't suggest this as it is similar to excluding all remote files. So you could not (yet) determine the actual path used? To be sure it works I just tried a folder exclusion on Win7/64 (using eicar.com) - works as expected (Process Monitor confirmed the open was on the normal path). So I assume it's not an issue with the base OS, the folder being on a NetWare volume might make the difference - file exclusion obviously works. Did you check the path with Process Monitor (excuse my insistence - it was quite useful assessing the looping problem with SAV32CLI)?

    Christian

    :25175
Reply
  • 0

    Hello AndrejK,

    exclusion on file filter *.dll

    didn't suggest this as it is similar to excluding all remote files. So you could not (yet) determine the actual path used? To be sure it works I just tried a folder exclusion on Win7/64 (using eicar.com) - works as expected (Process Monitor confirmed the open was on the normal path). So I assume it's not an issue with the base OS, the folder being on a NetWare volume might make the difference - file exclusion obviously works. Did you check the path with Process Monitor (excuse my insistence - it was quite useful assessing the looping problem with SAV32CLI)?

    Christian

    :25175
Children
No Data