I have Exchange 2007 SP1 running on Windows 2008 Server. Everything is fully updated as of this morning. I have enabled Outlook Anywhere but can't get my Outlook 2003 client to communicate. I am running all Exchange roles on one server and didn't see a need to do any registry hacking to ensure the ports are pointed correctly to my mailbox server. My configuration is as follows:[PS] C:\Windows\System32>Get-OutlookAnywhereServerName : MYSERVERSSLOffloading : FalseExternalHostname : exchange.mydomain.comClientAuthenticationMethod : NtlmIISAuthenticationMethods : {Ntlm}MetabasePath : IIS://MYSERVER.mydomain.com/W3SVC/1/ROOT/RpcPath : C:\Windows\System32\RpcProxyServer : MYSERVERAdminDisplayName :ExchangeVersion : 0.1 (8.0.535.0)Name : Rpc (Default Web Site)DistinguishedName : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN= MYSERVER,CN=Servers,CN=Exchange Administrative Gr oup (FYDIBOHF23SPDLT),CN=Administrative Groups,CN= First Organization,CN=Microsoft Exchange,CN=Servic es,CN=Configuration,DC=mydomain,DC=comIdentity : MYSERVER\Rpc (Default Web Site)Guid : 1effe973-21d0-49b3-b890-f294312d62c1ObjectCategory : mydomain.com/Configuration/Schema/ms-Exch-Rpc-Http -Virtual-DirectoryObjectClass : {top, msExchVirtualDirectory, msExchRpcHttpVirtual Directory}WhenChanged : 5/14/2008 2:57:10 PMWhenCreated : 5/14/2008 2:07:27 PMOriginatingServer : MYDCGC.mydomain.comIsValid : TrueSo, I have pointed my Outlook client towards exchange.mydomain.com and ensured the NTLM setting is chosen as well as set the msstd: stuff right. So, it doesn't work. However, when I VPN into the network it does work. So, I'm guessing it has something to do with the autodiscover DNS record. What do I need to have that pointed to? TIA!

Dear Snickered, Firstly, please understand that Outlook 2003 does not use Autodiscover service to configure its profile. Thus, you need to configure that profile yourself. From your output, please firstly ensure that there is an A Record on your external DNS server able to resolve the exchange.mydomain.com into correct IP Address. If the remote client computer is able to resolve the exchange.mydomain.com into IP Address, please let me know whether all the users cannot connect to the Client Access Server through Outlook Anywhere (RPC over Http). If all the user encountered the issue, please check the following configuration on your Client Access Server. 1. Please firstly check whether the ExternalHostName is listed in the SSL Certificate domain. We can check the Certificate Domain by using the following commands: Get-ExchangeCertificate -Thumbprint XXXXXXX | fl certificatedomains You should get the following response: CertificateDomains: (exchange.mydomain.com) 2. Please ensure that your Root Certificate has been installed into Trusted Root Certification Authorities on the Remote Client 3. If the above settings are correct, I suggest that you modify the authentication method to Basic on both the Client Access Server and Remote Client to troubleshoot the issue as some firewalls may affect the NTLM authentication process. If specific users encountered the issue, please notice the following points: 1. The Root Certificate has been installed into Trusted Root Certification Authorities on the Remote Client. 2. Whether the Outlook Anywhere (RPC over HTTP) profile are configured correctly on the Remote Client: For detailed steps to configure Outlook Anywhere (RPC over HTTP), you can refer to the following site: http://www.msexchange.org/tutorials/outlookrpchttp.html If the above method cannot get the issue solved, please let me know: 1. Whether all the user encountered the issue or specific users encountered the problem? 2. Which error codes and error messages/symptom are encountered when configure the Outlook 2003 to remote access the Exchange Server through RPC over Http? 3. Whether you can configure a computer (does not join domain or not logon as domain name) connect to the Client Access Server directly and successfully logon onto Exchange Server through RPC over Http? Mike

Yes, the certificate says exchange.mydomain.com. The certificates are installed on the clients properly also. It's just the initial setup that's the problem. When I tell the client to connect to the VPN and then configure the RPC over HTTPS it works fine. After they make the initial configuration they can then disconnect from the VPN and the Outlook client works without problems. One thing I notice is that when I type in exchange.mydomain.com into the "Microsoft Exchange Server" while connected to the VPN it changes it to the internal server name... something like "hostname.mydomain.com." Now, when I'm not connected to the VPN it obviously can't do this. Does this have anything to do with me not being able to configure it correctly while not connected to the VPN?

Hi Snickered, Please understand that it is normal behavior that we cannot Check Name when initially configuring the profile to connect to Exchange Server remotely by using RPC over HTTP. The issue occurs because the remote client cannot connect to GC directly to parse the user name. Thus, please simply cancel the error encountered when clicking Check Name and click More Settings to configure the RPC over HTTP setting. After that, the RPC over HTTP should able to work without problem. Mike