rpc over http exchange 2007 not working

rpc over http exchange 2007 not working

when we tried from www.testexchangeconnectivity.com  /Testing RPC/HTTP connectivity  test  getting error .  Attached the error screen shot
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

nashim khanExchange AdministratorCommented:
BuntyquestAuthor Commented:
Thanks for your above suggestions , bu we have already go thru those topics.
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

Simon Butler (Sembee)ConsultantCommented:
Disable Outlook Anywhere completely in Exchange.
Wait for the event log to confirm it has disabled.
Remove the RPC Proxy feature and then ensure the two directories are gone from IIS manager. If not, remove them.
Run IIS Reset.

Reverse the above, so you end up enabling Outlook Anywhere after reinstalling the proxy.

Check that nothing else is using port 443, the feature doesn't work on another port. I have seen firewalls get in the way for example.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Md. MojahidCommented:
The error is caused by a combination of the Windows Server 2008 RPC Proxy feature and Windows Server 2008 prefering IPv6 over IPv4 when talking to it self either with the localhost or the servername address. This means that when the CAS role contacts the RPC proxy on the same server, it will use the local ServerName resulting in the IPv6 address of :::1: instead of In it self this should not be a problem, however the RPC Proxy feature is bugged and does not listen on one of the 3 ports used (6001-6002 and 6004) when using the IPv6 address. So the RPC over HTTPS connection will fail.
To resolve the problem all You have to do is make the server use the IPv4 address instead of the IPv6 address when contacting it self.
Resolution #1 (Recommended resolution)
Edit the hosts file to use IPv4 localhost address instead of the IPv6 address :::1:, for the local ServerName and localhost addresses, the hosts file is located in the \Windows\System32\Drivers\etc folder. (Remember to start the editing with Administrator permissions)
Resolution #2
By not placing the CAS and Mailbox roles on the same server, and using IPv4 networking, the connection will go with IPv4 to the Mailbox server with RPC Proxy installed.
Resolution #3 (I would not recommend this solution.)
Use Windows Server 2003 on the Mailbox role, since it does not prefer IPv6 it wont be an issue.
Remember to get Outlook Anywhere working you will need to have the Windows feature RPC Proxy installed.
BuntyquestAuthor Commented:
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.