Outlook anywhere failing HTTP authentication
I am running Exchange Server 2003 single server Have enabled rpc/http for outlook anywhere but receive the following attached error when testing. my users cannot use simple outlook anywhere Testing RPC/HTTP connectivity. The RPC/HTTP test failed. Test Steps Attempting to resolve the host name owa.server.xx.xx in DNS. The host name resolved successfully. Additional Details IP addresses returned: 196.xx.xx.xx Testing TCP port 443 on host owa.server.xx.xx 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 owa.server.xx.xx 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 = CN=thawte Primary Root CA, OU="(c) 2006 thawte, Inc. - For authorized use only", OU=Certification Services Division, O="thawte, 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. xxxxxxxx Checking the IIS configuration for client certificate authentication. The test passed with some warnings encountered. Please expand the additional details. Additional Details Client certificate authentication couldn't be determined because an unexpected failure occurred. WinHttpSendRequest failed with error 12002. Testing HTTP Authentication Methods for URL https://owa.server.xx.xx/rpc/rpcproxy.dll. The HTTP authentication test failed. Additional Details A Web exception occurred because an HTTP 404 - NotFound response was received from ISA. I need a word of advice, please Reg:Shakoanem
May 30th, 2011 4:45am

Are you able to reach that url https://owa.server.xx.xx/rpc/rpcproxy.dll from within your network ? If yes please check in IIS on the RPC dir: 1) the execution permissions must be set to "Scripts and Executables" in IIS 2) Anonymous access must be disabled If you are not able to reach the url internally, either try to move the RPC virtual directory under your webmail site or recreate it from scratchVincenzo MCTS, MCTIP Server 2008 | MCTS Exchange 2010 | WatchGuard Firewall Security Professional
Free Windows Admin Tool Kit Click here and download it now
May 30th, 2011 7:33am

Hi Vincenzo Yes, i am able to reach url within my network 1. execution permission is indeed set to scripts and executables" 2. Anonymous is disabled, only checked Basic authentication ShakoaneM
May 30th, 2011 8:38am

How exactly have you enabled this feature? Are you using an ISA server, or is traffic coming straight to the Exchange 2003 server? With Exchange 2003, it is not as simple as enabling the option in ESM, you have to make registry changes for a single server implementation. http://exchange.sembee.info/2003/rpcoverhttp/default.asp Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.
Free Windows Admin Tool Kit Click here and download it now
May 30th, 2011 9:48am

Hi Simon Yes we are using ISA server -and OA publishing rule was done I have made regisrty changed - and can be seen when i ran rpccfg /hd - can see also port on the server I can forward to you if you need to verify the corectness of them (My exchange server is internet facing running as backend) - meaning one server also for OWA Regards,<sShakoanem
May 30th, 2011 10:38am

Have you tested RPC over HTTPS inside ISA? You need to verify that the feature is working correctly, because adding ISA in to the mix complicates matters considerably. As it stands, you don't know if the problem is with ISA or with Exchange. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.
Free Windows Admin Tool Kit Click here and download it now
May 30th, 2011 1:09pm

Hi The 404 or Not Found error message is a HTTP standard response code indicating that the client was able to communicate with the server, but the server could not find what was requested. You should check ISA configuration. http://www.isaserver.org/tutorials/2004owafba.html Can you post result when you turn off the ISA? Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
May 30th, 2011 11:14pm

Hi Terence I checked configurations on our ISA and looked same as other clients using same ISA Just to give a light on that: we have about 5 clients (distributors) using same ISA server So i have check the publishing rule for this specific one and looks excatly same as others Check also IIS RPC vd and looks fine with me Ref:shakoanem
Free Windows Admin Tool Kit Click here and download it now
May 31st, 2011 6:24am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics