Era Proxy doesn't work

[Nicolas DEVOUGE 0]

Hello,

 

I have installed an Era server :

Ubuntu  14.04 64bits

ESET Remote Administrator (Server), version 6.3.148.0
ESET Remote Administrator (Console Web), version 6.3.114.0

  
Module de mise à jour    1064 (20160324)
Module de prise en charge de la traduction    1494.1 (20160615)
Module de configuration    1277.6 (20160413)
Module SysInspector    1257 (20151113)

 

It is working fine

 

On an distant site, I want to set up a Proxy server, so I have installed a 2012 R2 datacenter VM , with Era Proxy, during the installation I have given the cerificate, and now the replication between ERA Server and ERA Proxy is fine , the status.html of Proxyis green, and beautiful

 

BUT, I have created a Policy to say to computer to connect to proxy ( I have set Proxy port to 2244 , wich is reply when I telnet the proxy server) , and it is my problem :

CReplicationModule	2016-Jun-24 14:31:48	CReplicationManager: Processing client replication task message
CReplicationModule	2016-Jun-24 14:31:48	CReplicationManager: Initiating replication connection to 'host: "admin-win.domoce.local" port: 2244' (scenario: Regular, data limit: 1024KB)
SchedulerModule	2016-Jun-24 14:31:48	Received message: GetRemainingTimeByUserDataRequest
NetworkModule	2016-Jun-24 14:31:48	Received message: CreateConnectionRequest
NetworkModule	2016-Jun-24 14:31:48	Attempting to connect to endpoint: 192.168.20.10
NetworkModule	2016-Jun-24 14:31:49	Forcibly closing sessionId:530, isClosing:0
NetworkModule	2016-Jun-24 14:31:49	Removing session 530
NetworkModule	2016-Jun-24 14:31:49	Closing connection , session id:530
NetworkModule	2016-Jun-24 14:31:49	Sending message: ConnectionFailure
CReplicationModule	2016-Jun-24 14:31:49	CReplicationManager: Replication (network) connection to 'host: "admin-win.domoce.local" port: 2244' failed with: (0x274d), Aucune connexion n’a pu être établie car l’ordinateur cible l’a expressément refusée

I Have no firewall on the Proxy Server, and a telnet to proxyserver:2244 is working (no error). Have I forgotten anything ?

 

Thanks !

 

[MartinK 378]

Is IP of ERA Proxy correct = 192.168.20.10? Are there any related entries in PROXY trace logs? There is a chance that connection attempt has not even reached PROXY server - it may have been blocked by firewall (on AGENT, PROXY or somewhere between).

[Nicolas DEVOUGE 0]

Thank you for your response

 

Yes, the IP of Era Proxy is 192.168.20.10, I have installed an agent on a windows PC, wich is in 192.168.20.X (same subnet). I wil post Proxy and Agent logs Monday. Firewall on this 2 PC are off.

[Nicolas DEVOUGE 0]

Here are some logs :

 

 

ERA Server :

2016-06-27 06:29:27 Error: NetworkModule [Thread 7f07177fe700]: Error reported by JobScheduler[Name:Dns job scheduler for not network operation]. Error message is:resolve: Host not found (non-authoritative), try again later
2016-06-27 06:30:57 Warning: NetworkModule [Thread 7f071e7fc700]: The connection will be closed due to timeout. Resolved endpoint is NULL
2016-06-27 06:31:58 Error: NetworkModule [Thread 7f07177fe700]: Error reported by JobScheduler[Name:Dns job scheduler for not network operation]. Error message is:resolve: Host not found (non-authoritative), try again later
2016-06-27 06:34:11 Warning: NetworkModule [Thread 7f071d7fa700]: The connection will be closed due to timeout. Resolved endpoint is NULL
2016-06-27 06:34:26 Warning: NetworkModule [Thread 7f071ffff700]: The connection will be closed due to timeout. Resolved endpoint is NULL
2016-06-27 06:36:38 Error: NetworkModule [Thread 7f07177fe700]: Error reported by JobScheduler[Name:Dns job scheduler for not network operation]. Error message is:resolve: Host not found (non-authoritative), try again later
2016-06-27 06:36:47 Error: NetworkModule [Thread 7f07177fe700]: Error reported by JobScheduler[Name:Dns job scheduler for not network operation]. Error message is:resolve: Host not found (non-authoritative), try again later
2016-06-27 06:36:57 Warning: NetworkModule [Thread 7f071effd700]: The connection will be closed due to timeout. Resolved endpoint is NULL
2016-06-27 06:40:58 Error: NetworkModule [Thread 7f07177fe700]: Error reported by JobScheduler[Name:Dns job scheduler for not network operation]. Error message is:resolve: Host not found (non-authoritative), try again later
2016-06-27 06:41:37 Warning: NetworkModule [Thread 7f071effd700]: The connection will be closed due to timeout. Resolved endpoint is NULL
2016-06-27 06:41:46 Warning: NetworkModule [Thread 7f071effd700]: The connection will be closed due to timeout. Resolved endpoint is NULL
2016-06-27 06:45:57 Warning: NetworkModule [Thread 7f071dffb700]: The connection will be closed due to timeout. Resolved endpoint is NULL
2016-06-27 09:36:34 Error: LicenseModule [Thread 7f06127ec700]: Update credentials do not exist.
2016-06-27 12:23:38 Error: NetworkModule [Thread 7f07177fe700]: Error reported by JobScheduler[Name:Dns job scheduler for not network operation]. Error message is:resolve: Host not found (non-authoritative), try again later
2016-06-27 12:23:59 Error: NetworkModule [Thread 7f07177fe700]: Error reported by JobScheduler[Name:Dns job scheduler for not network operation]. Error message is:resolve: Host not found (non-authoritative), try again later
2016-06-27 12:24:20 Error: NetworkModule [Thread 7f07177fe700]: Error reported by JobScheduler[Name:Dns job scheduler for not network operation]. Error message is:resolve: Host not found (non-authoritative), try again later
2016-06-27 12:24:41 Error: NetworkModule [Thread 7f07177fe700]: Error reported by JobScheduler[Name:Dns job scheduler for not network operation]. Error message is:resolve: Host not found (non-authoritative), try again later
2016-06-27 12:28:17 Warning: NetworkModule [Thread 7f071dffb700]: The connection will be closed due to timeout. Resolved endpoint is NULL
2016-06-27 12:28:34 Warning: NetworkModule [Thread 7f071effd700]: The connection will be closed due to timeout. Resolved endpoint is NULL
2016-06-27 12:28:54 Warning: NetworkModule [Thread 7f071d7fa700]: The connection will be closed due to timeout. Resolved endpoint is NULL
2016-06-27 12:28:58 Error: NetworkModule [Thread 7f07177fe700]: Error reported by JobScheduler[Name:Dns job scheduler for not network operation]. Error message is:resolve: Host not found (non-authoritative), try again later
2016-06-27 12:29:08 Warning: NetworkModule [Thread 7f0738ff9700]: The connection will be closed due to timeout. Resolved endpoint is NULL
2016-06-27 12:33:37 Warning: NetworkModule [Thread 7f071ffff700]: The connection will be closed due to timeout. Resolved endpoint is NULL
2016-06-27 12:50:17 Error: NetworkModule [Thread 7f071f7fe700]: ProtocolLayer: unsupported protocol version, ResolvedIpAddress:185.74.X.X, ResolvedHostname:185.74.X.X, ResolvedPort:56510

And proxy.log :

2016-06-27 05:49:07 Error: CReplicationModule [Thread 1c0]: CReplicationManager: Replication (network) connection to 'host: "eset-era.XXX.WW" port: 2222' failed with: The connection will be closed due to timeout
2016-06-27 05:54:27 Warning: NetworkModule [Thread 670]: The connection will be closed due to timeout. SessionId:16840 Ip address: 193.248.BBB.BBB Port: 2222 Resolved name: 
2016-06-27 05:54:27 Error: CReplicationModule [Thread d50]: CReplicationManager: Replication (network) connection to 'host: "eset-era.XXX.WW" port: 2222' failed with: The connection will be closed due to timeout
2016-06-27 05:59:27 Warning: NetworkModule [Thread 670]: The connection will be closed due to timeout. SessionId:16851 Ip address: 193.248.BBB.BBB Port: 2222 Resolved name: 
2016-06-27 05:59:27 Error: CReplicationModule [Thread 13c4]: CReplicationManager: Replication (network) connection to 'host: "eset-era.XXX.WW" port: 2222' failed with: The connection will be closed due to timeout
2016-06-27 06:04:27 Warning: NetworkModule [Thread 670]: The connection will be closed due to timeout. SessionId:16862 Ip address: 193.248.BBB.BBB Port: 2222 Resolved name: 
2016-06-27 06:04:27 Error: CReplicationModule [Thread 82c]: CReplicationManager: Replication (network) connection to 'host: "eset-era.XXX.WW" port: 2222' failed with: The connection will be closed due to timeout
2016-06-27 06:09:27 Warning: NetworkModule [Thread 1114]: The connection will be closed due to timeout. SessionId:16873 Ip address: 193.248.BBB.BBB Port: 2222 Resolved name: 
2016-06-27 06:09:27 Error: CReplicationModule [Thread 13fc]: CReplicationManager: Replication (network) connection to 'host: "eset-era.XXX.WW" port: 2222' failed with: The connection will be closed due to timeout
2016-06-27 06:14:27 Warning: NetworkModule [Thread 670]: The connection will be closed due to timeout. SessionId:16884 Ip address: 193.248.BBB.BBB Port: 2222 Resolved name: 
2016-06-27 06:14:27 Error: CReplicationModule [Thread 5d4]: CReplicationManager: Replication (network) connection to 'host: "eset-era.XXX.WW" port: 2222' failed with: The connection will be closed due to timeout
2016-06-27 06:19:27 Warning: NetworkModule [Thread 1114]: The connection will be closed due to timeout. SessionId:16895 Ip address: 193.248.BBB.BBB Port: 2222 Resolved name: 
2016-06-27 06:19:27 Error: CReplicationModule [Thread bac]: CReplicationManager: Replication (network) connection to 'host: "eset-era.XXX.WW" port: 2222' failed with: The connection will be closed due to timeout
2016-06-27 06:24:27 Warning: NetworkModule [Thread 1114]: The connection will be closed due to timeout. SessionId:16906 Ip address: 193.248.BBB.BBB Port: 2222 Resolved name: 
2016-06-27 06:24:27 Error: CReplicationModule [Thread ae4]: CReplicationManager: Replication (network) connection to 'host: "eset-era.XXX.WW" port: 2222' failed with: The connection will be closed due to timeout
2016-06-27 06:29:27 Warning: NetworkModule [Thread 1114]: The connection will be closed due to timeout. SessionId:16917 Ip address: 193.248.BBB.BBB Port: 2222 Resolved name: 
2016-06-27 06:29:27 Error: CReplicationModule [Thread 3f8]: CReplicationManager: Replication (network) connection to 'host: "eset-era.XXX.WW" port: 2222' failed with: The connection will be closed due to timeout
2016-06-27 06:34:27 Warning: NetworkModule [Thread 670]: The connection will be closed due to timeout. SessionId:16928 Ip address: 193.248.BBB.BBB Port: 2222 Resolved name: 
2016-06-27 06:34:27 Error: CReplicationModule [Thread 1198]: CReplicationManager: Replication (network) connection to 'host: "eset-era.XXX.WW" port: 2222' failed with: The connection will be closed due to timeout
2016-06-27 06:41:47 Warning: NetworkModule [Thread 670]: The connection will be closed due to timeout. SessionId:16952 Ip address: 193.248.BBB.BBB Port: 2222 Resolved name: 
2016-06-27 06:41:47 Error: CReplicationModule [Thread 908]: CReplicationManager: Replication (network) connection to 'host: "eset-era.XXX.WW" port: 2222' failed with: The connection will be closed due to timeout
2016-06-27 12:26:07 Warning: NetworkModule [Thread 670]: The connection will be closed due to timeout. SessionId:18664 Ip address: 193.248.BBB.BBB Port: 2222 Resolved name: 
2016-06-27 12:26:07 Error: CReplicationModule [Thread 568]: CReplicationManager: Replication (network) connection to 'host: "eset-era.XXX.WW" port: 2222' failed with: The connection will be closed due to timeout
2016-06-27 12:31:27 Warning: NetworkModule [Thread 670]: The connection will be closed due to timeout. SessionId:18676 Ip address: 193.248.BBB.BBB Port: 2222 Resolved name: 
2016-06-27 12:31:27 Error: CReplicationModule [Thread fbc]: CReplicationManager: Replication (network) connection to 'host: "eset-era.XXX.WW" port: 2222' failed with: The connection will be closed due to timeout

The DNS error are corrected now, it was because of DNS server was down.

 

[MartinK 378]

Actually those DNS resolving problems are known issue of ERA 6.3 - it should not fails in such way even if DNS server is not available. In case you encounter such problem again, you can use fixed libraries available in this post" https://forum.eset.com/topic/8061-workstations-showing-up-as-unmanaged-in-era-63-and-task-timing-issue/?p=43028-> especially Network.so for this problems.

 

Unfortunately form PROXY log we can only see, that it is attempting to connect to SERVER every 5 minutes and it fails because of this DNS resolving issues on SERVER. There does not seems to be any record of incoming connections therefore I think there is some kind of network problem. Have you check (using netstat) whether ERAProxy process is actually listening on correct port? HAve you tried to restart PROXY or whole machine to be sure? 

[Nicolas DEVOUGE 0]

I have just replaced files by them on your link, but the problem persist. When I start a netstat -an on the proxy machine, I have a 0.0.0.0:2244 listenting, and a [::]:2244 , so I think the Proxy is waiting on the good port. Do you need some more logs ? On the proxy , or on the server ?

[MartinK 378]

I have just replaced files by them on your link, but the problem persist. When I start a netstat -an on the proxy machine, I have a 0.0.0.0:2244 listenting, and a [::]:2244 , so I think the Proxy is waiting on the good port. Do you need some more logs ? On the proxy , or on the server ?

 

I am almost out of ideas .. please check also AGENT's trace.log for Errors, especially for new/different than you already posted. Unfortunately previous error indicates some kind of network configuration problem and I am now almost sure that AGENT connection are not received by PROXY. In order to verify this, Wireshark capture on PROXY machine may be useful (filtered for specific AGENT). I have seen similar errors in case port forwarding managed by Virtualbox/VMWare vere involved.

Second alternative is that AGENT is actually connecting...how are you checking in Webconsole whether AGENT is connecting or not? Please check also whether managing AGENT of this PROXY is connecting successfully (AGENT installed on the same machine as PROXY).