After update to 4.2.58 file server is crippled

2 days ago I updated to 4.2.58 and all hell broke loose. File server became completely useless, I get all the symptoms described in this Microsoft article
http://support.microsoft.com/kb/822219
Client computers are fine, but any time there is an operation on remote files, network lag is worse than on 56k modem. Our ERP software is running of the file share, also all user settings, documents and applications settings are redirected to file server. So this behavior renders our network useless. Everything worked fine on 4.2.40. After removing nod32 from file server everything is back to normal. Anyone else experienced similar issues?

 

did you do this?

 

On top of what nonoise has recommended, it might be worthwhile to also exclude any database files you have on the server as well.

 

Yes, I did.
None of the settings helped. Settings shouldn't be the issue here as older versions have worked just fine with exactly the same settings.
And I can't find 4.2.40 anymore. Microsoft describes it as kernel mode filter driver issue and it's affecting server service.

 

Hello,

When you installed the latest build did you install over the top of the previous installation? If you did then try an uninstall and then re-install the new version. Also as stated before you will want to ensure that you are following the reccomended server settings. As well as Microsoft's recommendations for Antivirus software running on a server OS. After that if you are still having issues I would recommend putting in a case with ESET Customer Care.

-Tom

 

I've been fiddling around DFS replication between two Win2008 R2 servers with EAV 4.2.58 installed on both and didn't find any problems.

 

I have a case with eset. But all I get is settings recommendation. And my problem still exist.
And I did uninstall and did clean installation. Same results.

 

Hello,

Someone will contact you shortly.

Cheers,
-Tom

 

spongecat, your issue is very similar to EAV v 4.2.58.3 problem on Fileserver posted recently. So, have a look at it.

-- rpr.

 

Yeah, that seem exactly like my issue.
I was contacted by Eset and they send me earlier version. I'll do more testing with it.