Jump to content

Dennis

Members
  • Posts

    6
  • Joined

  • Last visited

About Dennis

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Netherlands
  1. Hello, I have managed to resolve the issue by stopping and starting Apache Tomcat 7.0 through the system tray, I should have thought of this earlier.
  2. Hello, CTRL+F5 unfortunately did nothing. The services have been restarted, unfortunately restarting the machine is (currently) not an option. I will leave it be for the weekend and hope it's resolved on monday morning like https://forum.eset.com/topic/5110-login-failed-communication-error/. If not i'll post back here and contact ESET support, if the issue gets solved I'll make sure to post the solution here.
  3. Hello, running telnet to port 2223 works fine. The ESET services have the following statuses: ESET HTTP Server: not running ESET Remote Administrator Agent: running ESET Remote Administrator Server: running ESET Rogue Detection Sensor: running ESET Service: running ESET SHA Service: running
  4. Having done a little more research since I submitted this topic I'd like to think that the information in trace.log is unrelated as it shows multiple entries similar to this one. I found the following topic submitted by a user having the same issue, unfortunately mine has not resolved itself after a few days: https://forum.eset.com/topic/5110-login-failed-communication-error/
  5. Hello, I am trying to access the web console for ESET Remote Administrator but receive the following error when attempting to log in (I am using the right username and password): "Login failed (communication error)" Attempting to change the password will also give an error saying "Password change has failed". I have pulled some information from the trace.log file and added it as an attachment to this post. There seems to be an error related to the protocol version but I am not sure how to resolve this. Any help would be greatly appriciated. Regards, Dennis. trace.log
×
×
  • Create New...