Jump to content

Brianlogic

Members
  • Posts

    3
  • Joined

  • Last visited

Everything posted by Brianlogic

  1. I have checked both tablets having the issues and they are on ESET Endpoint Security version 2.7.9.0 Opening app and then it immediately closes and says app stopped working. These are AT&T Trek 2 HD Model K88, and they are running Android 7.1.1 They are ESET fresh installs as well. I have tried uninstalling, reinstalling, Clear Cache, Clear Data and nothing works. I go through install like ones we have done in the past and everything works except when I go to open the app to finish install after downloading. My phone was on 2.6.2.0 version and worked just fine. I updated to 2.7.9.0 and it still works and app opens. I took another AT&T same model tablet that already has ESET 2.6.2.0 on it and it works and opens. Updated it to 2.7.9.0 and it works just fine. App opens without crash. Sounds like a fresh install issue? Any help?
  2. Does this mean you cannot use the ESET certificates created and MUST use a custom HTTPS certificate from an outside source? As stated is does not work with the certificate created by ESET with the advanced security checked also.
  3. Have been using ESET mobile connector for our mobile devices for about a year. Up to this point they have all been Android. No problems. Company now wants to enroll brand new iPhones they just bought. Set all policies, got apple cert, serial numbers are on the DEP site, ESET server connects to DEP. I added our GoDaddy certificate purchased Dec. 2017 expires Dec. 2019, which is RSA256, added it as a custom certificate for these devices to use. However, ESET mobile connector policy says it is invalid per the yellow alert notification on my ESET server. When I go to website along with the port I still get the old certificate obviously. What is wrong with my third party certificate? It is installed on my server with the intermediaries also. Certificate chain is also there. ESET clearly states can use a third party certificate but is there anything else I can look at to see why it does not like my certificate? BTW.... using only ESET certs does not fix the issue. With ESET certs I get error in trace logs saying: [12096] Uncaught exception: NodSslException, NodSSL error occurred in completeHandshake.RecvEncryptedData (Handshake failed to complete). Local: [::ffff:10.10.3.15]:9980 Peer: [::ffff:70.62.39.50]:32107 ESET Security Management Server 7.0.577.0 ESET Security Management Center Mobile Device Connector 7.0.406.0
×
×
  • Create New...