Jump to content

scott72

Members
  • Content Count

    10
  • Joined

  • Last visited

Profile Information

  • Location
    USA
  1. We are seeing this all over our network, not sure if it is causing issues but would be nice to know.
  2. Finally got mine to work, showing as managed in my console.
  3. That's what I thought, I guess they just screwed me up again.
  4. I just got off the phone with eset and they want you to use the agent cert, not the one for the era console. I was doing the same thing since the documentation is so vague. (Might not be what you are doing but it sounds like it) The problem now for me is that that particular agent cert is self signed by the era server, which it won't be trusted by most phones. I guess I need to figure out how to get my purchased cert to work as the agent cert because I can sign my era console with my internal CA.
  5. Are you using the self signed agent cert generated by the era server for the mobile agents?
  6. Trying to get the MDC installed on a server in my dmz which is not a part of my internal domain where my era 6 resides. Getting the following error and installer rolls back. Opened a ticket with ESET and the only reply I got was RTFM. Documentation isn't much help. Eset Mobile Device Connector Issue ID: SOLN406 Installing MDC on a separate server. Install Fails when connecting to DB on ERA Server. Logging shows: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON
  7. Thanks for the response, this helps. Not sure exactly how people were deploying this. I think I am going to try and separate the MDC and put it on my DMZ, we'll see if this works.
  8. I was able to get it to work with the following instructions. Not ESETs, I havent tinkered with the agent certs yet though. https://forum.eset.com/topic/4986-era-v6-webconsole-ssl-certificate/
  9. I am currently testing out deploying the MDC on our internal network, but will eventually want this accessible from the Internet in order to use the remote wipe capabilities. Are people installing the MDC separate from their ERA in a DMZ scenario? I would be surprised if everyone was opening up these ports to their internal network. I currently am getting the MDM is up and running, but when trying to enroll on an internal wireless network I am getting a Communication Failure. Anyone run into this issue? I can get to the webpage, but when you hit connect, this comes up.
  10. I am getting the same error. I have setup the MDC internally as a test before making this accessible from the internet. I get the MDM server is up and running, but when I go to enroll the device I get the error above. Error comes up automatically, accessing from an internal wireless network. Firewall disabled on the server temporarily still same error.
×
×
  • Create New...