4.0.424 still crashes DC's

SORRY!! 4.0.424

FYI - running 4.0.424 EAV fresh install on a Windows Server 2003 fully patched with recommended exclusions, etc-

Can still ping it - but cannot login or interact in any way, and it is dead as far as DC/DNS/DHCP, etc.

- Update -- one of the DC's I put it on was completely hung -- I can connect to the other, but cannot login with valid credentials until I hard boot it.

 

Re: 4.0.324 still crashes DC's

do you mean 4.0.424? did you set it as advised?

 

Re: 4.0.324 still crashes DC's

I confirm this for 2008 but not with the newest 4.0 build.. I rolled back to 3.0.672..

 

Re: 4.0.324 still crashes DC's

Yep, I mis-posted the topic... can someone edit it to say 4.0.424?

And yes, using recommended settings for server from both ESET and MS.

 

Re: 4.0.324 still crashes DC's

Does it just lock up to the point where you cannot do anything at all but cold boot? All we could do is turn it off because it would not respond to ctrl-alt-del.. We were running 2k8 file cluster services on both servers... Added exceptions and settings recommened per eset and microsoft.. 4.0.314 and 4.0.417.. Roll back to 3.0.672 all is good for 6 days.. Had locked up back to back days in a locked state... Services on the server fail, but it remains running, no crash dump, no BSOD, just locked solid..

 

Re: 4.0.324 still crashes DC's

Our AD server with Netware client gets to the point all you can do is power it off with Nod32 4 on it. Mouse moves, but that's it. Eventually the network quits responding too.

I have a Windows 2008 server standard with VMWare server 2 and nothing else. Nod32 4 does the same thing to it.

Both are on other AV software as the fix.

 

Re: 4.0.324 still crashes DC's

What are the recommended exclusions you are running, exactly?

 

Re: 4.0.324 still crashes DC's

One locked up this morning where I couldn't even hit ctrl-alt-del -- another locked up where I COULD , however any username/password I tried couldn't login -- could only login after 2 cold boots.

http://support.microsoft.com/kb/822158
http://kb.eset.com/esetkb/index?page...nt&id=SOLN2144

 

Re: 4.0.324 still crashes DC's

I honestly would run 3.0.672 or 684 in a production environment for now.. It is unfortunate but that is what I would do, and have done.. I tested 4.0.314 and 417 on Global Catalog servers for a while and had no problems.. Then about 2-3 weeks ago our file server got hosed.. I did not relate it to NOD32.. Then it started happening often, and frequent.. Since uninstall and downgrade to 3.0.672 everything is fine, and I have went back to using 3.0.672 as the standard for all servers because I know that is what works.

 

Re: 4.0.324 still crashes DC's

Yep, this is what we've done -- I have a support case open, and they wanted me to try 4.0.424 for them.. just figured I'd let others know it's still happening.. the only server I have 4.0.424 on is our ERAS server.. and it's behaving..

 

Re: 4.0.324 still crashes DC's

GC and DC roles work ok for me but I reversed them anyway.. File server is only thing fubared.. Cluster service

 

Re: 4.0.324 still crashes DC's

Where's the Moderator / Eset employee now with the explanations why it's still not fixed?? Worst thing is that they don't know how to fix it!!! This is happening since the first ver.4 was introduced... Should've gone with a major brand's AV

 

Just to confirm, this is still a huge issue. We have just had it on version 4.0.424.0 and had to downgrade all our servers to V3.0.621.0. I think ESET really need to be warning about this on the download page.

 

I have a Windows 2k3 R2 server that we are trying to run V4 on. Non-domain controller under VMWare ESX.

Constantly crashes. V3 works great.

i've opened a support call.....

 

This is the response.... I've already used the recommeded server settings via Eset and Microsoft already documented here.

Thank you for contacting ESET Customer Care.
please use these setting for the server.

Potentially unsafe applications: Yes
Runtime packers: Yes

Scanner (Email filter - Outlook)
Potentially unsafe applications: Yes

Real time file system protection uncheck network drives

Cleaning
Cleaning level: Strict cleaning

Extension setup: Default value (see the dialog...)
extentions only


Protocol filtering set to Http and pop3 ports
choose Http and pop3 port

SSL choose always scan ssl protocol



Under no circumstances should product settings cause a O/S crash. I understand improper settings could cause performance issues. I told support I had the dump but they didn't ask for it.

V3 .684 works perfectly. Something is wrong with V4/2003 Server and this kind of support isn't going to find the issue.

I have 200+ workstations running V4 with no issues.

 

We have the same problems too.

https://www.wilderssecurity.com/showthread.php?t=236661&page=3

On one location I downgraded to v3.0.684 on the DC's and are running
fine. These servers crashed every 10min.

On another location I have DC's still running on v4 with crashes once a week.
Very strange.. No good response (and slow) from eset.

I also was a great eset fan, but it's getting less and less every day...

 

Possible breakthrough.....

With the release of .437 I decided to try again. Ran the same procedure:

1. Uninstalled V3
2. Rebooted
3. Manually deleted any folders and registry entries related to V3
4. Installed V4 with the same config I previously tried.

Been running for 2 hours with no crashes or CPU spikes. Prior releases would cause CPU spikes and crash the server within 10 minutes.

Keeping fingers crossed...

 

4 straight days and no issues. Upgraded a second server last night and it's also running fine. Neither of these are file servers... saving that one for last!

 

See thread https://www.wilderssecurity.com/showthread.php?t=241554
--

I WAS running OK for about a month until today.. I've updated to 4.0.437 -- let's see what happens..