Hi, I have been spending about 2 days trying to sort out why Outlook Anywhere will not work correctly. The setup is: * Exchange 2007 SP1on theintranet (on Windows 2003) * ISA 2006 (on Windows 2003) as a firewall (3-zone solution, DMZ, Internal and External) * Outlook 2007 with all patches ActiveSync and Outlook Web Access is working without any problem and the certificates are setup correctly. It's working both from inside and outside. The only thing that doesn't work is Outlook Anywhere. When I configure clients internally to work with RPC and right-click Outlook 2007 to see connection status I can only see that mail is connected by HTTPS but directory is connected by TCP/IP (looking at the Type column). This brings me to the next problem when I try Outlook Anywhere from outside: First test with NTLM enabled: When connecting from outside I get no access, ISA 2006 give me an error: Log type: Web Proxy (Reverse) Status: 12239 The server requires authorization to fulfill the request. Access to the Web server is denied. Contact the server administrator. Rule: Exchange RPC Publishing Source: (xxx.xxx.xxx.xxx) Destination: (xxx.xxx.xxx.xxx:443) Request: RPC_IN_DATA http://xxx.xxx.xxx/rpc/rpcproxy.dll?xxx.xxx.xxx.xxx:6002 Filter information: Req ID: 0d911fda; Compression: client=No, server=No, compress rate=0% decompress rate=0% ; FBA cookie: exists=no, valid=no, updated=no, logged off=no, client type=unknown, user activity=yes Protocol: https User: anonymous With Basic(instead of NTLM)enabled I tried using https://www.testexchangeconnectivity.com/which gives me a fail at the end: Testing NSPI "Check Name" for user xxx@xxx against server xxx.xxx.xxx.xxx An error occured while attempting to resolve the name Could not resolve the name, Exception Details:Message: An RPC Exception occured Binding, RPC Status 1717 UnknownIfType: System.ExceptionStack Trace:at RpcPingLib.RpcPing.CheckName(String argInternalServerFqdn, String nameToCheck)at Microsoft.Exchange.Tools.ExRCA.Tests.OLACheckNameTest.PerformTestReally() My own conclusion with this is that I have some sort of authentication error which I am trying to sort out but I have browsed for many hours and haven't found anyone having a similar problem. It would very helpful if anyone could shread some light over this. Thanks ! Best regards, Jens

I have the exact same problem. I haven't tried NTLM yet but Basic authentication is giving me the same error.

What OS and service releases are running on the client? I have this same error from XP SP3 machines and Vista SP1 hosts, but it works fine from XP SP2. I haven't found any clues on the net as to what the problem may be yet, but I have confirmed that installing SP3 on a working XP configuration breaks it, and removing SP3 from that same configuration restores connectivity.

Did anyone find a solution?