Alright I have read almost ever article I can find about this but I still am having no luck. What I have Exchange 2007 on 2003 R2 64bit our internal domain is set to domain.com our external domain is domaininc.com the email is hosted at exchange.domaininc.com we have the ad hosting domain.com, there is nothing point to domaininc.com on the local network. The mail server is named mail.domain.com but hosting exchange.domaininc.com. our internal domain is not a registered domain on the web. I have installed the RPC, changed the properties of the pages in IIS. Configured the registry setting for the 6001 ports. I have outlook anywhere setup in exchange ( I have tried NTLM as well as basic. I can set up a machine internally and it will connect with http first the switch to tcp/ip and everything will work. When I am out of the office it will never authenticate. I have even gone and set up the mail server as an domain controller thinking that would help. using testexchangeconnectivity.com it passes all the first test but Testing HTTP Authentication Methods for URL https://exchange.domaininc.com/rpc/rpcproxy.dll. The HTTP authentication test failed. Additional Details Exception details: Message: The underlying connection was closed: The connection was closed unexpectedly. Type: System.Net.WebException Stack trace: at System.Net.HttpWebRequest.GetResponse() at Microsoft.Exchange.Tools.ExRca.Extensions.RcaHttpRequest.GetResponse() I don't know what else to try. webmail is working as well as Apple mail clients. Thanks, Brian

Hi Brian, If I understand correctly from your explaination, Outlook Anywhere is not working, right? Run this and post the result https://www.testexchangeconnectivity.com/ Did you configure Outlook Anywhere?Gulab Prasad, My Blog | Z-Hire Employee Provisioning App gulab@exchangeranger.com

Hi Brian Did you try the link above? CheersZi Feng TechNet Community Support

Testing RPC/HTTP connectivity. The RPC/HTTP test failed. Test Steps Attempting to resolve the host name exchange.astrophysicsinc.com in DNS. The host name resolved successfully. Additional Details Testing TCP port 443 on host exchange.astrophysicsinc.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 Checking the IIS configuration for client certificate authentication. Client certificate authentication wasn't detected. Additional Details Testing HTTP Authentication Methods for URL https://exchange.astrophysicsinc.com/rpc/rpcproxy.dll. The HTTP authentication test failed. Additional Details Exception details: Message: The underlying connection was closed: The connection was closed unexpectedly. Type: System.Net.WebException Stack trace: at System.Net.HttpWebRequest.GetResponse() at Microsoft.Exchange.Tools.ExRca.Extensions.RcaHttpRequest.GetResponse()

Hi As the information that you provide, that might because of RPC component in the IIS was corrupt. Here is the steps that might help to your issue In the "Exchange Management Console", plese select "Client Access" under the "Server Configuration", right then click on "OWA" under "Outlook Web Access" and disable "Outlook Anywhere" on both the CAS servers.Go to "Control Panel", clicked on "Add/removed" programs, uninstalled and then re-installed the "RPC" component.Restart the MS Exchange System Attendant Service, then configure Outlook Client with Outlook Anywhere. CheersZi Feng TechNet Community Support

completed with no change in the results.

Hi Another solution Please check the setting on IIS Manager and if "Enable anonymous" access is checked under Rpc virtual directory, If yes, uncheck that and check "Basic authentication". Also Check the registry entry for ValidPorts , under : HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy , If there is an invalid entry, Change the ValidPorts reg key on the : HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy To : mail:6001-6002; mail.nwc.com.sa:6001-6002; mail:6004; mail.nwc.com.sa:6004 Finally restart the server CheersZi Feng TechNet Community Support

THANK YOU! it was the anonymous access, I didn't even think to remove that. Brian