ERA Server stopped working after local IP change

[K-Secit 0]

Hi,

we are using ERA V6.5 and everthing worked fine until we had to change our local subnet. We switched with all our servers from 192.168.45.0 to 192.168.100.0. Up from then the local "ESET Remote Administrator Server" Service won't run properly. We can start the service, log into ERA but after some minutes, the service shuts down and we just get a " Login failed: Connection has failed with state 'Not connected' " from ERA. When we start up the service again, we can log in, but same after some minutes. Nothing has changed, just the subnet.

Can someone give us some advise, where we could find the error?

We already did an repair installation of the Server component from ERA, but this doesn't solve the problem.

 

Thanks,

K-SecIT

[MartinK 376]

I would recommend to contact your local ESET support. Seems that ERA service is not stable and  proper analysis will be required. There is one known issue which behaves similarly, and caused by specific DNS messages causing ERA failure - any change you changed also DNS server?

You could also send me PM with ERA Server logs (C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs\) for quick analysis.

[K-Secit 0]

Hi MartinK,

yes, the Gateway and DNS Server changed too with the Subnet Change. Can you give me some more information about this DNS Problem?

 

Thanks,

K-SecIT