Exchange 2010 Outlook Anywhere RPC Proxy can't be pinged only on some accounts?!
I have a Exchange 2010 server on Windows server 2008 using outlook anywhere. I I have a problem with some exchange accounts failing during authentication with outlook anywhere when outside of the office lan (internal outlook anywhere always works). I ran a outlook.exe /dcdiag and these accounts wont even connect properly just remain on connecting. (i ran the test on a external network). I used the exchange connectivity tester website to try one of the problem account outside of my local and my account. When i run MY account though the exchange connectivity tester it goes though the test fine and connects without a problem. I only get a warning "The Referral service returned generic error 0x80004005. This many mean that encryption is required. ExRCA is trying again with encryption" - It then tries again with encryption and no problem. However when i try a account that outlook anywhere does not work i get one of two errors. At first i got the Testing SSL mutual authentication with the RPC proxy server. Verification of mutual authentication failed. Tell me more about this issue and how to resolve it Additional Details The certificate common name *.mydomainname.com doesn't validate against the mutual authentication string that was provided: msstd:webmail.brookskushman.com I figured out this probably happened because i am using a wildcard certificate. No problem i went ahead and Set-OutlookProvider -Identity EXPR and WEB to my common name certifcate msstd:*.thedomainname.com , and also entered the certifcate name manually when using the conncitivty tester. When i do that i get a NEW error! A Web exception occurred because an HTTP 401 - Unauthorized response was received from Unknown. How can one account work fine without a problem and another get a RPC Proxy can't be pinged when using outlook anywhere?! This problem only occurs for some accounts outside the office lan. Also some of the accounts that are having the RPC ping problem occur intermediately. some account will be fine for a week and then suddenly not work. All the problem email accounts work fine internally as expected when configured for outlook anywhere. Before you jump and say wrong settings during mail profile setup, let me assure you its all correct. So what the heck? Note: My exchange server has all roles installed on the same server and i am not using a edge server, insisted i have email coming into my gateway a baraccuda spam/firewall and then dumping to the exchange connector.
April 1st, 2011 6:44pm

Does your own account have different permissions? Domain admin for example? Wildcard certificates are always a source of trouble as well. It may well be that you need to disable Outlook Anywhere, remove the RPC Proxy and then reinstall the RPC Proxy and enable Outlook Anywhere again, so that everything is back to the defaults. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.
Free Windows Admin Tool Kit Click here and download it now
April 2nd, 2011 2:10pm

Does your own account have different permissions? Domain admin for example? Wildcard certificates are always a source of trouble as well. It may well be that you need to disable Outlook Anywhere, remove the RPC Proxy and then reinstall the RPC Proxy and enable Outlook Anywhere again, so that everything is back to the defaults. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me. I already tired that, i even tried reinstall of CAS role, iis every possible combination of repair/recover its not that. Keep in mind i keep all my exchange roles on one server. I am part of the admins groups. Interesting thing is when i go to RPCproxy.dll Here the thing, If i try to go to the page and enter my credentials it works proper as it should. I get a Blank page. However if i use one of the accounts that is having "issues" i get a "You do not have permission to view this directory or page." and constant credentials prompt everytime i try to visit it. (i tried two problem accounts). I cant change permissions on on the rpcproxy.dll to resolve this problem in a possible way.
April 3rd, 2011 12:43pm

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

Other recent topics Other recent topics