Unable to sync with Exchange 2003 getting Error Code 80072EE2, 80072EE7, 85010016 in HTC TOUCH HD WINDOWS 7 Phone

Hello friends, I am using the T-Mobile HTC TOUCH HD window 7 phone and I'm trying to connect the phone to our company EAS. First, go through a reverse proxy. When trying to connect, I get any error codes in the title, along with a message that says "We are having problems connecting to xxx.xxx.xxxx. Try again later." I tried to modify the domain of only the short name and use the full name. I'm waiting to hear back from our people proxy to make sure they have adequate access through the proxy, but just wanted to see if anyone had any of these error codes before. If I take the "necessary SSL" option, which is when I get the error 85010016 with a message that said, we are having a problem with the server or connection. Try again later." So please help me and provide some solution to it. Thank you.

I think you will be able to get the solution on the internet and also you will be able to get the appropriate method to solve the problem. So you should try over there and get it done.

The company has allowed the proxy regulations again and I am trying to connect. I no longer receive an "error" per se, but the device still says "xxxx account information is incorrect. Update your information xxx.xxx.xxxx (address of proxy) and click Save" Nothing that I goes further. I validate my password is acceptable, tried just my username and my domain name, tried the short name of my domain, tried using a. for the domain, an empty domain treated with UPN, the empty domain with domain or the username, etc. not anything is working, I just move incessantly.

I think the company has allowed and also you will be able to do and I also think you will be not able to get any sort of the problem which you were getting, so just check as per the above user have tried.

Basically, the requirement of WP7 to include a "domain" name when connected via EAS is the problem (depending on how you want to see them). Let's look at what happens on the iPhone and Android. When you configure the EAS settings on both OS, we tell our customers to enter their user name and password Active Directory, but to leave the "domain" blank. Try the connection to the external server to our proxy server address. When the user logs in, the proxy has a unique user name and queries Active Directory to see if there is sAMAccountName. If the sAMAccountName is found, it uses the username and password to successfully connect and authenticate AD. Everything is excellent.

I think the above is the correct and also you should might try that and also you will be able to get it done and also you will be able to solve the problem which you are getting and also you might get the perfect method for the problem of yours.

What phone does Windows 7? Fundamentally, it works exactly the same. Though, because the "domain" is required in WP7, add the domain to your username. What the sAMAccountName LDAP query to see mydomain.com \ username. Well, Active Directory does not have the chain anywhere as sAMAccountName. Therefore, a request for authentication failure is sent back to the proxy and the user's password even sent to the AD. In the phone itself, you just keep getting the message that your "account information in Outlook is incorrect" and has the option to change username, password and domain. None of which do any good. The next step is to create an environment with Forefront Unified Access Gateway 2010 as a reverse proxy and see if I can get it to work. We will not expose our foreign exchange in a different way.

I think that you have done the certainly come across a Windows Phone 7 requirement to enter the domain name when connecting to an Exchange mailbox. I think that this was also a requirement for Windows Mobile 6.5.

I'm not sure; you can leave the domain blank. In my tests, however, does not seem possible to move beyond the screen if the domain is left blank. As for me, my test ended sadly, WP7 reporting was not able to connect through our reverse proxy, as are the other devices (iPhone / Android). This is a shame, since it must be easy to give the option to use the domain or not. Why force? It makes no sense to me at all. It looks bad in MS. Now, I'm creating a UAG laboratory to demonstrate the use of the UAG. Unfortunately, it is probably a futile exercise because we are under contract for a vendor's product.

The above users have given you the perfect and also the best method to do it and also you should try it and get it done for yourself and make the synchronize of the things which you wanted to do.