Exchange Server

Nick-Mars · Guest

I am having problems setting up RPC over HTTP.

I've set it up on two previous occasions. Went in pretty smoothly although
I can't say I understood the nuances of what I was doing.

This time the environment was a little different but not significantly.
Currently the Exchange server is the second exchange server in the
environment. It is an Exchange 2003 server. The other server is a Exchange
2000 server. We are in the process of migrating to the 2003 server. The
other difference for me is that the Exchange 2003 server initially was not a
DC for the domain. Reading through the requirements I read that it needs to
be a Global Catalog Server in order for RPC/HTTP to work so I made it a DC
after the intial attempt failed.

I have set up a local Certification Authority on the server. It's working
so far as I can tell.

When I attempt to test the RPC virtual directory configuration it fails.
When I use IE to browse to "https://"server"/RPC the page returned is the
standard "This page can not be displayed" error (Cannot find server or DNS
error).

Running RPCPing with the following command line:
rpcping -t ncacn_http -s ctrsv11 -o RpcProxy=RPCProxyServer -P
"mantis,ctrsys,*" -I "mantis,ctrsys,*" -H 2 -u 10 -a connect -F 3 -v 3 -E -R
none

Returns:
RPCPing proxy server RPCProxyServer with Echo Request Packet
Sending ping to server
Error 12007 returned in the WinHttpSendRequest.
Ping failed

Pretty stumped at this point. Any guidance will be appreciated.

Nick-Mars · Guest

Made some progress. Realized that I did not enter the RPC Server name in my
RPCPing command string. When I entered the server name my error message
changed to:

Error 12029 returned in the WinHttpSendRequest.

Research indicates that this may be caused by:
Port 80 or 443 being blocked?
Or the WWW service not running?

Am I on the right track?

Suggestions?

I am issuing the command from the server. I can access OWA leading me to
believe that WWW is running and minimally port 80 is working.

"Nick-Mars" wrote:

Martin Qiu [MSFT] · Guest

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.

Nick-Mars · Guest

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:

Martin Qiu [MSFT] · Guest

Hi Nick,

Thank you for your response.

According to your update, I understand that the Port Query tool reports
that HTTP and HTTPS are both listening, but OWA does not work via HTTPS.

In this case, the issue is most likely related to the specific SSL
certificate you used for HTTPS. Please follow the steps in the following
article to create a new SSL Certificate on your Exchange 2003 Server to
test the issue again.

SSL Enabling OWA 2003 using your own Certificate Authority
http://www.msexchange.org/tutorials/SSL_Enabling_OWA_2003.html

If the issue persists, I suggest you repost a new thread in the following
newsgroup: Microsoft.public.inetserver.iis.security. The reason why we
recommend posting appropriately is you will get the most qualified pool of
respondents, and other partners who the newsgroups regularly can either
share their knowledge or learn from your interaction with us. Thank you for
your understanding.

Thank you for your understanding and 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.

Nick-Mars · Guest

Thanks. Excellent article. Worked.

"Martin Qiu [MSFT]" wrote:

Martin Qiu [MSFT] · Guest

Hi Nick,

Appreciate your update and response. I am glad to hear that the problem has
been fixed. If you have any other questions or concerns, please do not
hesitate to contact us. It is always our pleasure to be of assistance.

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.

	Exchange Server Forum Index -> Connectivity	All times are GMT
Page 1 of 1