RPC Proxy can't be pinged._ A Web exception occurred because an HTTP 405 - MethodNotAllowed response was received from Unknown.


  • Hi all,


    I downloaded the RPC tools from the microsoft site, exactly the rpcping tool.


    on the Command Prompt I wrote:



    rpcping -t ncacn_http -s exchangesrv -o RpcProxy=exchangesrv -P"user,domain,password" -I"user,domain,password" -H 2 -u 10

    -a connect -F 3 -v 3 -E -R none


    and it gave me the result:



     RPCPinging proxy server exchangesrv with Echo Request Packet
       Sending ping to server
       Response from server received: 401
       Client is not authorized to ping RPC proxy
       Ping failed.


    this is the explanation for this Error:


    Response from server received: 401 
    Client is not authorized to ping RPC proxy
    You receive this response if the RPC Ping Utility test failed. The PRC Ping Utility test may have failed if HTTP access is denied, if there are incorrect credentials on the –Pswitch, or if the user exits.



    In the IIS snap-in, on the Web Site tab, on the TCP port it is 80 and in the SSL port it is 443, and the IP is the IP address of the Exchange Server(it's on one machine with Windows 2003 Server).


    Can Someone help me, please. I want to Run the Outlook outside and I think this is the prevention. It is a certificate error or what ??? I have a self signed certificate, which I imported in the Root Certificate Authority

    Saturday, December 07, 2013 9:11 PM

All replies

  • Hi,

    Let’s begin with the following article:
    The error you mentioned above may be caused by that HTTP access is denied or credentials is incorrect on the –P switch.

    Thus, let’s try the troubleshooting below:
    1. check if enalbing Outlook Anywhere and install the RPC over HTTP component. Because  external Outlook clients use Outlook Anywere connect to the Exchange server:
    2. since it’s a self-signed certifictae in your environment, please check if you have installed the certificate on all outside clients.

    Additionally, to narrow down the cause, we can use ExRCA to check Outlook Anywhere connectivity:
    ExRCA: https://testconnectivity.microsoft.com/   
    How to use EXRCA: http://www.msexchange.org/articles-tutorials/exchange-server-2007/tools/exchange-server-remote-connectivity-analyzer-tool-part1.html

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.



    Angela Shi
    TechNet Community Support

    Monday, December 09, 2013 6:42 AM
  • we have 3rd party certifcates for our mail.domain.com for owa and rpc.

    I have addes the valid ports 6001 6002 6004 in rgistry........\rpcproxy. after this

     have get this error in cmd from remote computer. 

    rpcping -t ncacn_http -s mail.warrene.com -o RpcProxy=mail.warrene.com -P "testrpc,warrene.com,*" -I "testrpc,warrene.com,*" -H 2-u 10 -a connect -F 3 -v 3 -E -R none

    RPCPing v2.12. Copyright (C) Microsoft Corporation, 2002
    OS Version is: 6.2
    Enter password for server:
    Enter password for RPC/HTTP proxy:

    RPCPinging proxy server mail.warrene.com with Echo Request Packet
    Sending ping to server
    Response from server received: 405
    Ping failed.

    Kindly please help on this.................job may be gone on this issue. it is little but now big as giant.


    Monday, December 09, 2013 7:59 PM
  • Hi,

    Sorry for delay reply.

    As far as I know, 405 errors often arise with the POST method. Thus, we can use Network Monitor to confirm it:


    Alternatively, I’d like to confirm if there is any firewall or some other device blocking the method in your environment. And we can use a local computer to test it.

    Best regards,

    Angela Shi
    TechNet Community Support

    Monday, December 23, 2013 5:11 AM