ERA 4.0.138 issue after update from version 3.x

Hello all,

the story:
A couple week ago, I updated our ERA Server by installing it over the previous v3.x version. Then i also created new NOD32 Business Edition packages base on the last version 4.2.71.2, but i pushed it only to several clients.

In our LAN, with very few exceptions, signature updates are retrieved from the ERA Server using the mirror file share option. We are using this system since in the older ERA servers the http update was very unreliable.

the issue:
Well, after the update, those few clients that were set to update via ERA http are failing the update with the error: Invalid Username and/or password.
I tried to reset the user/pass (a domain user which worked till the update) in both server and clients and i also tried with the real ESET user and pass which are set in the server.
Http update doesnt work at all, i tried it with 3.0.695, 4.0.471, 4.2.35 and 4.2.71 nod32 client versions.

Any hints please?

EDIT: i just tried it and http updates work only if i set the authentication as NONE or BASIC in the ERA console and if I set as NTLM it fails to authenticate. Setting the auth as none or even basic kinda defeats the purpose of having a password set in the first place

 

Hello,

If you go to the clients tab in RA, then highlight one of the problematic clients and press F4, open the configuration and expand the update module. Expand setup, and the update server should show where the clients are looking for the updates. Are they set to look at the mirror for updates, or is it set to choose automatically?

If the clients are returning a "Invalid username/password" when trying to update, it's referring to the license username and password.

Thanks,

Matt

 

Thanks for answering, but those problematic clients used to work before the ERA update.
Anyway, they are pointing towards the right update server. In my 1st post I already mentioned that the "invalid username and/or password" message appear only when i set http authentication as NTLM. On basic/none http updates are working.

 

Try replacing http_dll.dlll located in "C:\Program Files\ESET\ESET Remote Administrator\Server\http_dll.dll" with the one from the latest EAV/ESS BE version 4.2.71 followed by the ERAS service restart.

 

Sorry for the late answer.

After replacing the http_dll.dll the ESER RA HTTP Server doesn't even start. And i tried everything: starting from services (gives error message), restarting the parent service - ESET RA Server - but the HTTP server doesn't start, unchecking/checking the Http Update check-box in server settings.

After reverting to the original dll file, the HTTP Server started again.

Any other ideas/things to try or an estimate for a fix from ESET?