Comments on: Exchange, ActiveSync and my new Verizon XV6700 http://www.rickwargo.com/2006/03/20/exchange-activesync-and-my-new-verizon-xv6700/ Acquiring information, one day at a time. Sat, 04 Sep 2010 06:11:36 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Ian http://www.rickwargo.com/2006/03/20/exchange-activesync-and-my-new-verizon-xv6700/comment-page-1/#comment-20142 Ian Tue, 16 Dec 2008 00:30:09 +0000 http://www.rickwargo.com/2006/03/20/exchange-activesync-and-my-new-verizon-xv6700/#comment-20142 Rick. Thank you so much for helping resolve my issue. I looked everywhere else and couldn't find a resolution. It turns out that the problem was that my backend server didn't have integrated auth checked off. Rick. Thank you so much for helping resolve my issue. I looked everywhere else and couldn’t find a resolution. It turns out that the problem was that my backend server didn’t have integrated auth checked off.

]]> By: Justus' .Net Blog http://www.rickwargo.com/2006/03/20/exchange-activesync-and-my-new-verizon-xv6700/comment-page-1/#comment-14919 Justus' .Net Blog Thu, 15 May 2008 16:59:21 +0000 http://www.rickwargo.com/2006/03/20/exchange-activesync-and-my-new-verizon-xv6700/#comment-14919 <strong>Exchange über HTTP...</strong> Nur ein kurzer Eintrag mit einem Link zu einer Anleitung, die ich schon mehrfach benutzt habe, um einen Exchange nach außen sichtbar zu machen. How-To Configure RPC over HTTP Um mein Handy dann auch noch mit dem Exchange Server direkt zu synchr... Exchange über HTTP…

Nur ein kurzer Eintrag mit einem Link zu einer Anleitung, die ich schon mehrfach benutzt habe, um einen Exchange nach außen sichtbar zu machen.
How-To Configure RPC over HTTP
Um mein Handy dann auch noch mit dem Exchange Server direkt zu synchr…

]]> By: Jeremy Lam http://www.rickwargo.com/2006/03/20/exchange-activesync-and-my-new-verizon-xv6700/comment-page-1/#comment-4759 Jeremy Lam Sun, 18 Nov 2007 21:41:15 +0000 http://www.rickwargo.com/2006/03/20/exchange-activesync-and-my-new-verizon-xv6700/#comment-4759 Thanks a Million you finally help me to solve the 0×85010014 and 0×85010001 errors. I think you are the ultimate solution after i search for over 100 webpages out there. Thanks a Million you finally help me to solve the 0×85010014 and 0×85010001 errors. I think you are the ultimate solution after i search for over 100 webpages out there.

]]> By: Roberto http://www.rickwargo.com/2006/03/20/exchange-activesync-and-my-new-verizon-xv6700/comment-page-1/#comment-4111 Roberto Mon, 27 Aug 2007 05:42:33 +0000 http://www.rickwargo.com/2006/03/20/exchange-activesync-and-my-new-verizon-xv6700/#comment-4111 [/exchange-oma] virtual directory - BRILLIANT. Thanks for the fix. [/exchange-oma] virtual directory – BRILLIANT.
Thanks for the fix.

]]> By: James http://www.rickwargo.com/2006/03/20/exchange-activesync-and-my-new-verizon-xv6700/comment-page-1/#comment-148 James Tue, 06 Feb 2007 10:12:22 +0000 http://www.rickwargo.com/2006/03/20/exchange-activesync-and-my-new-verizon-xv6700/#comment-148 ActiveSync was working fine until I reconfigured for http over rcp on a single server. Then I received the 3031 error on the server and 0×85010014 on the desktop. This was the solution that worked for me. Application Event viewer (on the exchange server) for Source: Server ActiveSync, Event ID: 3031 about the mailbox server does not allow “Negotiate” authentication to its [/exchange-oma] virtual directory. This led me to configure IIS to support both Kerberos and NTLM authentication (as described above), although after doing so, I continued to see the error message. It finally went away when I recreated the /Exchange-OMA directory. James ActiveSync was working fine until I reconfigured for http over rcp on a single server. Then I received the 3031 error on the server and 0×85010014 on the desktop.

This was the solution that worked for me.

Application Event viewer (on the exchange server) for Source: Server ActiveSync, Event ID: 3031 about the mailbox server does not allow “Negotiate” authentication to its [/exchange-oma] virtual directory. This led me to configure IIS to support both Kerberos and NTLM authentication (as described above), although after doing so, I continued to see the error message.
It finally went away when I recreated the /Exchange-OMA directory.
James

]]> By: Timothy Cox http://www.rickwargo.com/2006/03/20/exchange-activesync-and-my-new-verizon-xv6700/comment-page-1/#comment-21 Timothy Cox Thu, 21 Dec 2006 19:17:16 +0000 http://www.rickwargo.com/2006/03/20/exchange-activesync-and-my-new-verizon-xv6700/#comment-21 Thank you for contributing to the community! Your blog on Exchange Activesync is what finally fixed me. Particularly: (quoted: I often saw an error in my Application Event viewer (on the exchange server) for Source: Server ActiveSync, Event ID: 3031 about the mailbox server does not allow “Negotiate” authentication to its [/exchange-oma] virtual directory. This led me to configure IIS to support both Kerberos and NTLM authentication (as described above), although after doing so, I continued to see the error message. It finally went away when I recreated the /Exchange-OMA directory. ) The other thing I did (other than recreate) was to rename it, This customer is a subdomain in a larger exchange forest, I had created "AZ-Exchange-OMA" and kept getting the error above, I changed it to just "az-oma", changed the registry entry, restarted IIS, and it finally worked. It's too bad there is no really good "active sync t-shoot" doc I could find. IT sucks, I'm going to become a plumber. Tim Thank you for contributing to the community! Your blog on Exchange Activesync is what finally fixed me.
Particularly: (quoted: I often saw an error in my Application Event viewer (on the exchange server) for Source: Server ActiveSync, Event ID: 3031 about the mailbox server does not allow “Negotiate” authentication to its [/exchange-oma] virtual directory. This led me to configure IIS to support both Kerberos and NTLM authentication (as described above), although after doing so, I continued to see the error message. It finally went away when I recreated the /Exchange-OMA directory. )

The other thing I did (other than recreate) was to rename it, This customer is a subdomain in a larger exchange forest, I had created “AZ-Exchange-OMA” and kept getting the error above, I changed it to just “az-oma”, changed the registry entry, restarted IIS, and it finally worked. It’s too bad there is no really good “active sync t-shoot” doc I could find.

IT sucks, I’m going to become a plumber.

Tim

]]>