I finally figured it out. I'd apparently removed the activesync path from the original listener and left only RPC. Created a new listener for testing and left off the "forward basic authentication". Got that straightened out and everything works great. Jeff ________________________________ From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On Behalf Of Mark Morgan Sent: Friday, July 21, 2006 1:01 PM To: isalist@xxxxxxxxxxxxx Subject: [isalist] Re: Exchange Activesync authentication problem Do you have FBA listening on a different IP?? ________________________________ From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On Behalf Of Bunting, Jeff Sent: Thursday, July 20, 2006 2:39 PM To: isalist@xxxxxxxxxxxxx Subject: [isalist] Exchange Activesync authentication problem Hi All, I'm trying to get Activesync working on a Motorola Q phone. I managed to get our certificate installed on the phone, but ISA keeps rejecting the connection. Exchange 2003 SP2 Front End Server & ISA 2004 SP1 if that matters. The ISA logs show Client Username as anonymous and HTTP status code as: "12229 The server requires authorization to fulfill the request. Access to the Web server is denied. Contact the server administrator." I'm using the same listener as RPC over HTTP which uses Basic Authentication (SSL required). I have OWA using a different listener using FBA. OWA, OMA, and RPC/HTTP are all working OK. OMA works from the phone and Activesync works when cradled, just not over the air. . Can anyone think of something I might have misconfigured to cause this problem? Thanks, Jeff -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.10.3/394 - Release Date: 7/20/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.10.3/394 - Release Date: 7/20/2006