We are setting up mulitple domain names on Exchange 2007 by using separate OUs, 1 AD; after configuring Global Address lists per company, as well as Adress Lists and OABs, we purchased and installed one Certificate for a trial run. OWA is configured. Users in Company A can connect via Outlook Web Access, but not with RPC over HTTP; Outlook errors out, unable to resolve names. Running https://www.testexchangeconnectivity.com/ comes up with perfect marks until the last, unable to ping the proxy server: Testing RPC/HTTP connectivity. The RPC/HTTP test failed. Test Steps Attempting to resolve the host name mail.graycallison.com in DNS. The host name resolved successfully. Additional Details IP addresses returned: 70.60.248.15 Testing TCP port 443 on host mail.graycallison.com to ensure it's listening and open. The port was opened successfully. Testing the SSL certificate to make sure it's valid. The certificate passed all validation requirements. Test Steps Validating the certificate name. The certificate name was validated successfully. Additional Details Host name mail.graycallison.com was found in the Certificate Subject Common name. Certificate trust is being validated. The certificate is trusted and all certificates are present in the chain. Additional Details The certificate chain has been validated up to a trusted root. Root = OU=Go Daddy Class 2 Certification Authority, O="The Go Daddy Group, Inc.", C=US. Testing the certificate date to confirm the certificate is valid. Date validation passed. The certificate hasn't expired. Additional Details The certificate is valid. NotBefore = 10/29/2010 11:16:55 AM, NotAfter = 10/29/2011 11:16:55 AM Checking the IIS configuration for client certificate authentication. Client certificate authentication wasn't detected. Additional Details Accept/Require Client Certificates isn't configured. Testing HTTP Authentication Methods for URL https://mail.graycallison.com/rpc/rpcproxy.dll. The HTTP authentication methods are correct. Additional Details ExRCA found all expected authentication methods and no disallowed methods. Methods found: Basic Testing SSL mutual authentication with the RPC proxy server. Mutual authentication was verified successfully. Additional Details Certificate common name mail.graycallison.com matches msstd:mail.graycallison.com. Attempting to ping RPC proxy mail.graycallison.com. RPC Proxy can't be pinged. Additional Details A Web exception occurred because an HTTP 401 - Unauthorized response was received from Unknown. Prior to configuring the GAL,AL and OAB settings we were able to connect with a test user, so it stands to reason that the problem lies in the Address lists settings. The test users we have set up are not marked to "Hide from Exchange address list".

That wouldn't be my conclusion. Mine would be that your RPC Proxy might be misconfigured or blocked.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

How might I check that? The only settings in Outlook for the proxy are the URL, which passes the test, the Certificate, which passes the test and Basic Authentication, which passes the test. What am I missing?

It looks like you have gotten to the RPC Proxy, but you can't get through it.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Did you restart the Microsoft exchange service host service after enabling outlook anywhere the "ValidPorts" registery might not be set correctly with proper ports assignments to GC and DC. Dhruv

Hi, Please try to access https://localhost/rpc/rpcproxy.dll on the CAS server, you should get the blank page after inputting the password. If not, we need to reinstall RPC Proxy component. If it's fine, please try to check whether the below KB can help you fix this issue: http://support.microsoft.com/kb/896861 Thanks AllenAllen Song

Allen, The RPC component works properly; after entering the password, I get a blank white screen as you mentioned above. I'm not sure how the KB article would apply; we are running XP Pro SP3 on the test machine, and the Exchange Server is 2007 running on a Windows Server 2008. In addition, we are using Basic, not NTLM, authentication, and there is no DisableStrictNameChecking registry entry in Server 2008. JIM

Does not work internally or just from internet ( externally )

I cannot get a PC set up with Outlook using RPC over HTTP; the name will not resolve; I can use Outlook Web Access and connect to the test mailbox. We have removed all the changes we made to the permissions for address lists, and still cannot resolve names via RPC over HTTP.

If you change DNS record, start from here.

We ended up contacting Microsoft Tech support and paid for a resolution to this problem. There were 2 major problems that needed to be resolved. First there was a residual error in the permissions for the GALs that we had missed when we updated those permissions. Secondly, there were IPv6 connectivity issues. There is a TechNet article, http://technet.microsoft.com/en-us/library/cc671176.aspx, which addresses that. However, the article specifically states in a very large graphic, "This problem was resolved in Update Rollup 4 for Exchange Server 2007 Service Pack 1. If you have installed Update Rollup 4 for Exchange Server 2007 Service Pack 1 or a later version, do not follow the procedure that is described in this topic." Since we are up to Update Rollup 1 for Exchange Service Pack 3 on this Exchange Server, we very clearly read this as "This does not apply to you". Guess what? Following the procedures to remove IPV6 from Network connections, edit the registry AND edit the Host file all need to be done to make this work! Problem resolved. This problem was resolved in Update Rollup 4 for Exchange Server 2007 Service Pack 1. If you have installed Update Rollup 4 for Exchange Server 2007 Service Pack 1 or a later version, do not follow the procedure that is described in this topic. This problem was resolved in Update Rollup 4 for Exchange Server 2007 Service Pack 1. If you have installed Update Rollup 4 for Exchange Server 2007 Service Pack 1 or a later version, do not follow the procedure that is described in this topic. This problem was resolved in Update Rollup 4 for Exchange Server 2007 Service Pack 1. If you have installed Update Rollup 4 for Exchange Server 2007 Service Pack 1 or a later version, do not follow the procedure that is described in this topic.