Riadg

If you mean as ping yes we can ping both ways from 192.x.x.x to 10.x.x.x. But we can check port 2222 if is open or not. If it is going to be an issue is there a way to allow these clients as an external clients to connect to era server ?

Hi We have installed ERA server 8.0 in our network range 192.168.x.x which is working fine. We have another network connected via VPN with the range 10.0.x.x with ESET installed but these computers does not show in the panel. Is there a way that we can add them. They are not shown in lost and found nor in Rogue. Any suggestions

Yes already Updated all modules ,regardling ESMC Agent ,so i think before it was workin well

I am attacked with an MBED ransom ware which is now asking me to make payment of a lot of $. Please do help me I have lot of company data in and also note already was have latest updated modules and definitions for out ESET products ,So need help because we discover this case only in 3 computers Otherwise there is more than 200 computer on the same range .we have to find solution to fix this as soon as possible

Thank you for your reply , could you please provide more information where will the one AGENT and rogue detection sensor be installed , To calrify more yes we want to detect rogue devices in a different metwork Thanks

Dear All Here is our situation ESMC server ip address is in the range 10.10.10.xxxx, All clients in this range can be managed from ESMC. We have nother internal network with another range 192.168.0.xxxx , the two networks are connected but in ESMC we can't see the desktops with the 192.168.0.xx range , how can we manage that other network from ESMC. Thank you

Hi Martink Resolved the issue , but still we have another issue which is as follows , can't deploy easet agent and product from console , we get the message ( try to install software manually ) when we try to install software manually we get error message ( This may be a result of malware activity and recommends to run a specialized cleaner ). We downloaded it from ESET and ran the specialized cleaner wirth a result of ( No malware had been found on the system ). When we remove ESET and try to reinstall the package again we get the same error of malware activity and error 108. msi. In client log file before ESET removal we get this error which is in most machines , proxy is not enabled on the server. 2019-03-03 12:20:04 Warning: CReplicationModule [Thread 2228]: InitializeConnection: Not possible to establish any connection (Attempts: 1) 2019-03-03 12:20:04 Error: CReplicationModule [Thread 2228]: InitializeFailOverScenario: Skipping fail-over scenario (stored replication link is the same as current) 2019-03-03 12:20:04 Error: CReplicationModule [Thread 2228]: CAgentReplicationManager: Replication finished unsuccessfully with message: InitializeConnection: Initiating replication connection to 'host: "WIN-95NG7KIBUQE" port: 2222' failed with: Request: Era.Common.Services.Replication.CheckReplicationConsistencyRequest on connection: host: "WIN-95NG7KIBUQE" port: 2222 with proxy set as: Proxy: Connection: :3128, Credentials: Name: , Password: ******, Enabled:0, EnabledFallback:1, failed with error code: 2, error message: Failed to create subchannel, and error details: Replication details: [Task: CReplicationConsistencyTask, Scenario: Automatic replication (REGULAR), Connection: WIN-95NG7KIBUQE:2222, Connection established: false, Replication inconsistency detected: false, Server busy state detected: false, Realm change detected: false, Realm uuid: a601b950-8f2e-4bd7-8cde-3d05befd2491, Sent logs: 0, Cached static objects: 0, Cached static object groups: 0, Static objects to save: 0, Static objects to delete: 0, Modified static objects: 0]

Hi We still have problems in upgrading agents and eset security as well , please check these messages on server side 2019-02-21 06:00:07 Warning: CReplicationModule [Thread d48]: VerifyDeviceAuthenticationToken: Verification of authentication token: ac9ee386f05a39a7122ec45a40f4c3c007ac2c6a770897e2f95b69c44d63f5e9 failed (error_code=INVALID_TOKEN, status=TOKEN_EXPIRED, msg= 2019-02-21 06:00:07 Warning: CReplicationModule [Thread d48]: RpcCheckReplicationConsistencyHandler: Token validation failure 2019-02-21 06:04:21 Error: CRepositoryModule [Thread fc8]: GetFile: Host 'us-repository.eset.com' not found [error code: 20002] Remote agents 2019-02-20 06:22:07 Error: CReplicationModule [Thread 328]: SendRequestAndHandleResponse: Rpc message response AUTHENTICATION_FAILURE (Token status: TOKEN_EXPIRED) -> Request new session token and resend replication request 2019-02-21 16:00:25 Warning: CSystemConnectorModule [Thread 90]: CWinRestartAgentTask: unable to restart at the moment. Retrying in a minute Can you pleasde point us what can we do next

Hi We excuted client task Security Management Center Components Upgrade , the succesful ones only updated the agent , but endpoint security is not updated do we need to do something else ? once we finish those we will start to debug the failed ones .

Dear All Afer Succesful Upgrade to running componenet upgarde task , some clients failed , so do we create all in one installer and install on the failed clients ? Thanks

Thank you so much

Hi I have been trying to add my activated license in license manager on my.eset.com account but i see the following massage Sorry for the inconvenience, there was an error processing your request. Please advice