Solved

Exchange 2013 RPC Proxy cannot be pinged

Posted on 2014-07-22
5
324 Views
Last Modified: 2014-07-29
I have a new server 2012 VM running in Hyper-V on a new server 2012 host which is also the DC.  Exchange 2013 was installed with attention to the prerequisites, and appeared to do the job. New Godaddy UCC cert installed. Outlook anywhere is configured to use the external FQDN both inside and out. External address pings from inside OK. OWA web page works. connectivity test passes activesync test.  Connectivity test fails autodiscover and outlook connectivity test.  Outlook connectivity test fails RPC ping.  tried to open https://localhost/rpc/rpcproxy.dll and did not get login prompt. I am trying to check/correct the path for rpcproxy in IIS and have a challenge.   Which one to fix?

there is a RPC under default website, and another under Exchange Back End.  Neither one will ask for authentication.  I changed the path from one down a road in program files\microsoft\exchange... to the normal (I think) path in windows\system32 and ran iisreset, but still neither one works.

Begining to feel like swimming in circles in a toilet bowl here.  Could use some help.
0
Comment
Question by:billherde
  • 4
5 Comments
 
LVL 3

Author Comment

by:billherde
ID: 40214391
I have attempted repair of both RPC virtual directories, and still no joy.  Removed and replaced rpc over http from server with same results.  re-ran the add services script from technet which came back no changes made, and then ran service pack 1 setup /mode:upgrade in an effort to get installer to fix it.  This unfortunately resulted in a fail while configuring unified messaging portion.  Now I have to correct that to get past it in installer.  Any thoughts out there about the original issue?
0
 
LVL 3

Author Comment

by:billherde
ID: 40214659
Service pack upgrade completed successfully, but still no RPC.
0
 
LVL 42

Expert Comment

by:Amit
ID: 40215184
Any HLB or NLB between client and server? Can you try this, open host file on the server and add two entries.

ServerIP NetBIOS
ServerIP ServerFQDN

Like
192.168.1.1 Server1
192.168.1.1 Server1.xyz.com

Save it and restart and test again.
0
 
LVL 3

Accepted Solution

by:
billherde earned 0 total points
ID: 40218304
Had to call msft to get it moving.
Solution started with adding binding to 127.0.0.1 for http and https on IIS. Then set externalclientauthenticationmethod to auth for outlook anywhere to ntlm.  No negotiate anywhere. and finally we found the outlookprovider settings were blank. (get-outlookprovider) so we set the serviceprinciple names for expr and exch.  At that point, Outlook clients within the building were able to autodiscover and connect to exchange.
There is still a remaining DNS issue for autodiscover on the public side, but that will be another query.
0
 
LVL 3

Author Closing Comment

by:billherde
ID: 40226235
Thanks for the reply, but this could not wait days to get fixed.
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This process describes the steps required to Import and Export data from and to .pst files using Exchange 2010. We can use these steps to export data from a user to a .pst file, import data back to the same or a different user, or even import data t…
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…

786 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question