RE: RPCPING error 12007

Thanks for getting back to me.

In response to your items:

(1) Mailbox definately exists. Please keep in mind that I'm not even
concerned about accessing a mailbox yet. I am not able to browse
successfully to https://"server"/rpc. When I do I get "Page Not Displayed".
RPCPing also fails with “Error 12029 returned in the WinHttpSendRequest”.

(2) Confirmed that RPC Proxy is using default ports, I THINK. SSL for
default web site is set to 443.

(3) I can NOT access OWA via HTTPS but I can via HTTP. Port Query tool
reports that HTTP and HTTPS are both listening.

(4) Mailbox can be accessed on the internal network using Outlook. RPCPing
test fails internally.

"Martin Qiu [MSFT]" wrote:

> Hello Nick,
>
> Thank you for posting here!
>
> According to your description, I understand this issue to be as follows:
>
> You are unable to use RPC over HTTP to connect to the Exchange Server. When
> running RPCPing, you get the "Error 12029 returned in the
> WinHttpSendRequest".
>
> If I have misunderstood your concern, please let me know.
>
> Based on my experience, this issue may be caused by 443 ports blocked or
> other potential factors. Please perform the steps below to narrow down the
> problem.
>
> 1. Firstly, please double confirm that the mailbox you try to access via
> RPC over HTTP hosts in the Exchange 2003 Server. Based on my knowledge, the
> issue is not related to whether Exchange Server is also DC.
>
> 2. Double confirm that you have configured the RPC proxy server to use the
> default ports for RPC over HTTP that are specified inside the corporate
> network.
>
> (1) On the RPC proxy server, start Registry Editor.
> (2) Locate and then click the following registry subkey:
>
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\RpcProxy
>
> (3) In the right pane, right-click "ValidPorts", and then click "Modify".
> (4) Remove all the information from the "Value data" box, and then type the
> following information:
>
> <ServerNETBIOSName>:6001-6002;<ServerFQDN>:6001-6002;<ServerNetBIOSName>:600
> 4;<ServerFQDN>:6004
>
> (5) Click "OK", and then quit Registry Editor.
>
> For more detailed information, please refer to the following Knowledge Base
> article:
>
> 833401 How to configure RPC over HTTP on a single server in Exchange Server
> 2003
> http://support.microsoft.com/?id=833401
>
> 3. Please check whether you can access OWA via
> https://exchangeserver/exchange/. We can also use the PortQueryUI tool to
> test whether the issue is related to RPC connection or port problems.
>
> The PortQueryUI tool is available for download from the following Microsoft
> Web site:
> http://download.microsoft.com/download/3/f/4/3f4c6a54-65f0-4164-bdec-a3411ba
> 24d3a/PortQryUI.exe
>
> Then, you can use the Port Query tool to query your Exchange Server and
> double check whether 80 and 443 ports respond as "NOT LISTENING". For more
> detailed information about the Port Query tool, please refer to the
> following Knowledge Base article.
>
> 310298 How to Use Portqry.exe to Troubleshoot Microsoft Exchange Server
> http://support.microsoft.com/?id=310298
>
> 4. Finally, please double check whether the user is able to access mailbox
> in the internal network in Outlook. You can also perform the RPCPing test
> in the internal work too.
>
> Please don't hesitate to let me know in case you have any further updates
> or concern.
>
> Have a nice day!
>
>
>
> Regards,
>
> Martin Qiu
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> Business-Critical Phone Support (BCPS) provides you with technical phone
> support at no charge during critical LAN outages or "business down"
> situations. This benefit is available 24 hours a day, 7 days a week to all
> Microsoft technology partners in the United States and Canada.
>
> This and other support options are available here:
>
> BCPS:
> https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
> Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
>
> If you are outside the United States, please visit our International
> Support page:
> http://support.microsoft.com/common/international.aspx
> =====================================================
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
.

Relevant Pages

  • Re: Exchange, Outlook and DNS problem
    ... > Company deceided to switch from ISP POP3 to local Exchange server. ... > Cisco routes to local ISA IP address.ISA is configured to do RPC over ... > HTTP routing for Exchange which is also located in internal network. ... > Outlook while connected internal network. ...
    (microsoft.public.win2000.dns)
  • RE: RPC over HTTP troubleshooting
    ... When we connect to the server through RPC over HTTPS, ... HTTP Error 401.3 - Unauthorized: Access is denied due to an ACL set on the ... 833401 How to configure RPC over HTTP on a single server in Exchange Server ...
    (microsoft.public.exchange.connectivity)
  • RE: Is it possible to send fax from Outlook over http/rpc ?
    ... can send fax via RPC over HTTP. ... Based on my knowledge, in a local area network, Outlook communicates ... RPC over TCP/IP. ... Exchange Server accounts from the Internet when they are working outside ...
    (microsoft.public.windows.server.sbs)
  • Re: RPC Over HTTP Security
    ... 833401 How to configure RPC over HTTP in Exchange Server 2003 ... >> select the "encrypt" option on the security page in the Outlook email ...
    (microsoft.public.exchange2000.general)
  • Re: Server ActiveSync gives HTTP error 500
    ... Usually an HTTP error 500 is a genral bucket for INTERNAL_SERVER_ERROR. ... Could you please verify that it was the Exchange Server returning ... >> because I managed to fix the problem by ExMerging-out my entire mailbox ...
    (microsoft.public.pocketpc.activesync)