I have installed the EMM v9.5.5; now i get a error when install the agent on two devices i get the following error “Cannot Connect to Server”; if i check the account settings all is fine except the server settings, appears something like this:
When my server is test.domain.com.
Somebody knows why this occur.
Thanks in advance.
El mensaje fue editado por: choscar08 on 1/06/11 05:35:39 PM GMT-06:00
Solved! Go to Solution.
Thanks for your reply, yesterday i read this document and work with it; but the issue was not fixed.
Do you know something that i could do to try fix this issue ?.
Not necessarily! I have EMM running fine for most devices, iOS and Android. But I have 3 Android devices and 1 Windows device that have never been able to connect. 1 Android device that I used to be able to “make always compliant” to connect but not anymore.
what was the problem choscar08 ?
I have the same issue.
EMM worked before but from now to then I get the error. I also reviewed Final ActiveSync Troubleshooting Guide for EMM.pdf
and it seems all fine ( telnet to apple OK, telnet to Email Server /Active Sync Server on 443 OK)
Im getting in the IIS log this :
The server understood the request, but is refusing to fulfill it.
Would be nice to see your solution.
Basically we had to reinstall the EMM, because we found a problem with the certificate. Our certificate was wrong generated, after check this, the EMM works fine.
was the MDM Certificate wrong or the public one for your Server? Was it a MDM Certificate which was not generated trough Apple Developer Enterprise Program?
Worked it before / on other devices?
I just want to know, because maybe I got the same problem. Just make sure
I am getting something like this as well. I can't understand why when I enter my AD account password it comes back up and says the password I entered is invalid. I can log into the portal and my desktop machine with my AD credentials so I would think the link to LDAP is working. I also can log into the hub with my user/pass.
When we checked the exchange logs its essentially saying "wrong credentials"
Is this issue possible cause by the KB artice that mentions changing https to http?