EMON error and UPDATE error :(

Hi there!

I am using an registered NOD32 Enterprise Edition,
I am receiving this error message from different users:

During execution of EMON - Microsoft Outlook email monitor module on ***** computer, the following notification was generated: Attempt to read configuration (5) failed.

The RAS is installed on a computer that runs Windows 2003 Server X64, R2
The clients are not on active directory or joined to domain. They are runing the latest version of NOD32(2.51.26) and with lastest update:1.1651 (2006070
Any Ideas?

I am also having problems with updating.
I have configured all clients to update via http, they are making updates but I am also receiving this error message:

During execution of Update on the computer *****, the following warning occured: Update attempt failed (Incorrect username or password.) or the one with server connection failure

I am receiving a lot of this kind off errors described below. Please someone help me, cause I don't know what else can I do. I have tried to see if the config file si the problem, but I don't think so. I have put the config file on the mirror update server, which they are connecting to over the http.

 

It sounds like the configuration file you used for the clients may have some incorrect settings.

I'd review the settings under the EMON section...did you do any specific settings?

Regarding the updates....you do not use a username and password when you use http for update. Leave the username and password section blank for the clients, under the update section. You'll use the server address which will look something like http://192.168.10.10:8081 Or you can use the netbios name of the server...http://servername:8081..but I prefer IP when I can..less DNS load/traffic. This is for the clients only..your mirror server will be getting the updates from Esets public servers.

 

No the settings for the EMON are not changed. Also, why some computers are giving this error and others don't?

The http update mirror is configured well, I'm using the ip address instead the server name, followed by port. I am not using passwords or account user names, also if is on http, it should't look for such things. I can't find the solution for this. I have computers in LAN that are not giving errors. All are using same config and same client, so what's the problem?

 

Maybe the local system account is not granted write permission to the appropriate registry key with EMON settings on those machines?

 

How did you deploy the clients? Push installs from the RAC? Or sitting at each workstation..installing the NOD32 client..and manually configuring it?
Did you further attempt to update any client configs?
Is there a domain controller ruling the network, DNS and name resolution? (I know you said the clients are not logging into AD..but just curious if your 2K3 server is running DNS)
All a single class C network?
Any software firewalls?

The workstations that are giving the errors...I would looks for a common "thing" with them...in how they are different from the ones that appear to be working correctly.

The workstations that are giving errors...I'd go to one..and visually inspect the settings in the control center. If you're getting "user/pass" errors..then it must be attempting to log into "something" with a user/pass.

 

I have installed on each computer by sitting at workstations. I put the nod32 clients to get the config from RAS and after connecting to RAS, each one took the config file, I have checked myself and all the settings specified in config file were in client's config. The Windows server is not configured for DNS.

Yesterday, the computer gave me the error again many times, one by one with very little difference of time betwen them like in 2 minutes-8 errors: During execution of EMON - Microsoft Outlook email monitor module on ***** computer, the following notification was generated: Attempt to read configuration (5) failed.
That happend in the morning, after that, no errors given.
This morning, nothing, it works well.
I don't know what to say about it.