Well, to be exact, most of it works, just the last step fails: Testing HTTP Authentication Methods for URL https://email.lavelle.com/rpc/rpcproxy.dll. The HTTP authentication test failed. Additional Details An HTTP 500 response was returned from Unknown. All the other tests from https://www.testexchangeconnectivity.com work and pass.

Can you check to see if SSL is enabled on the RPC virtual directory? Confirm the following SSL Settings: Require SSL (Checked) Require 128-bit SSL (Unchecked) Client certificates: Ignore If you are still having issues then you may need to re-isntall the RPC proxy component on the CAS. MCITP: Enterprise / Server Administrator | MCITP: Enterprise Messaging Administrator 2007/2010 | MCP | MCDST

Can you check to see if SSL is enabled on the RPC virtual directory? Confirm the following SSL Settings: Require SSL (Checked) Require 128-bit SSL (Unchecked) Client certificates: Ignore If you are still having issues then you may need to re-isntall the RPC proxy component on the CAS. MCITP: Enterprise / Server Administrator | MCITP: Enterprise Messaging Administrator 2007/2010 | MCP | MCDST Require SSL is checked. Ignore is selected. There is no option for 128 bit. How would I re-instal RPC proxy components?

Try the following: Disable outlook anywhere using the Exchange Management Console Remove RPC proxy component using PowerShell servermanagercmd -r rpc-over-http-proxy Reboot the server Install RPC proxy component using PowerShell servermanagercmd -i rpc-over-http-proxy Enable outlook anywhere using the Exchange Management Console Restart the Microsoft Active Directory Topology Service Try the test again MCITP: Enterprise / Server Administrator | MCITP: Enterprise Messaging Administrator 2007/2010 | MCP | MCDST

Try the following: Disable outlook anywhere using the Exchange Management Console Remove RPC proxy component using PowerShell servermanagercmd -r rpc-over-http-proxy Reboot the server Install RPC proxy component using PowerShell servermanagercmd -i rpc-over-http-proxy Enable outlook anywhere using the Exchange Management Console Restart the Microsoft Active Directory Topology Service Try the test again MCITP: Enterprise / Server Administrator | MCITP: Enterprise Messaging Administrator 2007/2010 | MCP | MCDST I will try it tomorrow when users are off. When I re-enable outlook anywhere, what authentication should I choose? Basic, NTLM or Neg Ex?

You can use the same authentication that you currently have enabled. If you enable Basic authentication users will be prompted to enter in the domain, username and password each time they connect to the Exchange Server. If you enable NTLM then users that are logged onto the domain will not have to enter in the credentials they should automatically connect to the Exchange Server. Additional details in the following article: http://technet.microsoft.com/en-us/library/bb123542.aspxMCITP: Enterprise / Server Administrator | MCITP: Enterprise Messaging Administrator 2007/2010 | MCP | MCDST

You can use the same authentication that you currently have enabled. If you enable Basic authentication users will be prompted to enter in the domain, username and password each time they connect to the Exchange Server. If you enable NTLM then users that are logged onto the domain will not have to enter in the credentials they should automatically connect to the Exchange Server. Additional details in the following article: http://technet.microsoft.com/en-us/library/bb123542.aspx MCITP: Enterprise / Server Administrator | MCITP: Enterprise Messaging Administrator 2007/2010 | MCP | MCDST OK. The error changed. This makes no sense. I have a DNS record pointing to email.lavelle.com. That is how I log onto OWA. Attempting to resolve the host name email.lavele.com in DNS. The host name couldn't be resolved. <label for="testSelectWizard_ctl12_ctl06_ctl02_tmmArrow">Tell me more about this issue and how to resolve it</label> Additional Details Host email.lavele.com couldn't be resolved in DNS InfoDomainNonexistent.

Hi, I test the URL https://email.lavelle.com/rpc/rpcproxy.dll from my side, it is working. Also, the name in the certificate issued by Godaddy appears correct. However, whan I tried email.lavele.com, it fails. Note that there is single "L" between two "E". So I believe it is a typo cause the error when you tested. Fiona

I finally figured that out. When I reset up Outlook Anywhere, I mistype my actual domain. Thanks everyone for your help. All the connectivity tests now have green check marks!!