We have a Windows Server 2003 file server that was running NOD32 2.7 with no problems. Besides running SQL Server 2000 the server is just acting as extra network storage. I recently upgraded it to NOD32 3.0.621 Business Edition. It is currently running virus database 2794 and all of the latest program components. Since the NOD32 upgrade it will run for a few hours and then grind to a halt, denying access when trying to open any files on its shared drives. It is possible to browse the directories with normal speed, but trying to open any file (e.g. doc, xls, pdf or even a simple text file of only a few KB), causes the application to hang and eventually time out without managing to open the file. If I log into the server locally or via a Remote Desktop Connection it is possible to open those files at a normal speed. If I examine the processes running with Task Manager nothing is using much CPU time. Trying to access the files remotely just hangs the application used (e.g. Word, Excel, Notepad etc.) If I reboot the server everything is fine again for another few hours. I have disabled advanced heuristics and excluded any SQL Server database files but this does not seem to have improved the situation. When I rolled back to NOD32 2.7 the problem went away. NOD32 3.0 is running successfully on all other servers and workstations in the Company except for this one file server. Any ideas what might be the problem and how to fix it?