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

    Well, I'd give Support a call (and refer them to this thread).

    But try Process Monitor first - although you have narrowed down the problem and Support should be able to recreate it I assume this will nevertheless take some time. OTOH if Process Monitor shows a "weird" path this might enable you to configure a working exclusion until a general solution is found.   

    Christian

    :25185
Reply
  • 0

    Well, I'd give Support a call (and refer them to this thread).

    But try Process Monitor first - although you have narrowed down the problem and Support should be able to recreate it I assume this will nevertheless take some time. OTOH if Process Monitor shows a "weird" path this might enable you to configure a working exclusion until a general solution is found.   

    Christian

    :25185
Children
No Data