Re: RPC over HTTP failing with 400 Bad Request on Proxy

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Alan Sun [MSFT] (v-asun_at_online.microsoft.com)
Date: 10/11/04 

Date: Mon, 11 Oct 2004 06:22:48 GMT

Dear Ray,

Thanks for your posting back.

According to the current situation, I suggest you check the Authentication
setting on RPC Virtual Directory.To do this, follow these steps:
1. Click Start, point to Administrative Tools, and then click Internet
Information Services (IIS) Manager.
2. Expand servername (local computer), expand Web Sites, expand Default Web
Site, right-click Rpc, and then click Properties.
3. Click the Directory Security tab, and then click Edit under
Authentication and access control.
4. Click to clear the Enable anonymous access check box.
5. Click to select the Basic authentication (password is sent in clear
text) check box.

You receive the following message:
The authentication option you have selected results in passwords being
transmitted over the network without data encryption. Someone attempting to
compromise your system security could use a protocol analyzer to examine
user passwords during the authentication process. For more detail on user
authentication, consult the online help. This warning does not apply to
HTTPS(orSSL) connections.

Are you sure you want to continue?Note In this error message, the word
"HTTPS(orSSL)" is a misspelling for the words "HTTPS (or SSL)."
6. Click Yes, and then click OK.
7. Click Apply, and then click OK.

The RPC virtual directory is configured to use basic authentication. We
recommend that you use SSL together with basic authentication. To enable
SSL on the RPC virtual directory, you must obtain and publish a
certificate. This procedure assumes that you have obtained and published
certificate. To configure the RPC virtual directory to require SSL for all
client-side connections, follow these steps:
1. Click Start, point to Administrative Tools, and then click Internet
Information Services (IIS) Manager.
2. Expand Web Sites, expand Default Web Site, right-click Rpc, and then
click Properties.
3. Click the Directory Security tab, and then click Edit under Secure
communications.
4. Click to select the Require secure channel (SSL) check box and the
Require 128-bit encryption check box.

Note We recommend that you click to select the Require 128-bit encryption
check box. However, RPC over HTTP functions correctly even if you do not
require 128-bit encryption.
5. Click OK, click Apply, and then click OK.

You need to check this setting on OWA virtual directory as well.

Please inform me of the results at your convenience. I am waiting for your
update. Have a nice day!

Thanks & Regards
Alan Sun
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.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
---- Reply-To: "Ray" <NJRay@anon.postalias>
---- From: "Ray" <NJRay@anon.postalias>
---- References: <#JXTnZJrEHA.1036@TK2MSFTNGP10.phx.gbl>
<Nq7d1sQrEHA.740@cpmsftngxa06.phx.gbl>
---- Subject: Re: RPC over HTTP failing with 400 Bad Request on Proxy
---- Date: Fri, 8 Oct 2004 13:31:40 -0400
---- Lines: 124
---- X-Priority: 3
---- X-MSMail-Priority: Normal
---- X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
---- X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
---- X-RFC2646: Format=Flowed; Original
---- Message-ID: <emVm1xVrEHA.2900@TK2MSFTNGP12.phx.gbl>
---- Newsgroups: microsoft.public.exchange.connectivity
---- NNTP-Posting-Host: c7144711.state.nj.us 199.20.71.17
---- Path:
cpmsftngxa06.phx.gbl!TK2MSFTNGXA03.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP0
8.phx.gbl!TK2MSFTNGP12.phx.gbl
---- Xref: cpmsftngxa06.phx.gbl microsoft.public.exchange.connectivity:98991
---- X-Tomcat-NG: microsoft.public.exchange.connectivity
----
---- Alan,
---- The article you sited is the one I have been using.
----
---- For Test 1 I have my outlook 2003 configured as specified.
---- When I launch outlook with /rpcdiag switch I can see that it is trying
to
---- connect to my mail server.
---- The type is Referral, the conn is --- , and the status is connecting.
----
---- For Test 2.
---- RPCPing fails with the following output.
----
---- RPCPinging proxy server RpcProxyServer with Echo Request Packet
---- Sending ping to server
---- Error 12007 returned in the WinHttpSendRequest.
---- Ping failed.
----
---- Ray
----
----
----
----
---- "Alan Sun [MSFT]" <v-asun@online.microsoft.com> wrote in message
---- news:Nq7d1sQrEHA.740@cpmsftngxa06.phx.gbl...
---- > Hi Ray,
---- >
---- > Thanks for your posting here.
---- >
---- > I suggest you double check the configuration for RPC over HTTP
according
---- > to
---- > the article:
---- >
---- > How to configure RPC over HTTP in Exchange Server 2003
---- > http://support.microsoft.com/?id=833401
---- >
---- > At the mean while, please perform the following tests:
---- >
---- > Test 1: Outlook Configuration
---- > ======================
---- > - Open Outlook.
---- > - Click Tools, click Email accounts.
---- > - Choose view or change existing email accounts and click OK.
---- > - Highlight the Exchange Server account and click Change.
---- > - Click More Settings.
---- > - Click Connection tab and check the "On a fast network, connect
using
---- > HTTP
---- > first, then connect using TCP/IP" option box.
---- > - Test the issue again.
---- >
---- > Test 2: RPCPing
---- > ============
---- > Use the RPCPing utility to check the communication. You need use the
---- > following syntax:
---- > "rpcping -t ncacn_http -s ExchangeMBXServer -o
RpcProxy=RpcProxyServer -P
---- > "user,domain,*" -I "user,domain,*" -H 1 -u 10 -a connect -F 3 -v 3
-E -R
---- > none" (without the quotation marks)
---- > If the command is correct, please let me know the exact error
message.
---- >
---- > For more information, please refer to the following article:
---- > How to Use the RPC Ping Utility to Troubleshoot Connectivity Issues
with
---- > the Exchange Over the Internet Feature in Outlook 2003
---- > http://support.microsoft.com/?id=831051
---- >
---- > Hope this helps. Please let me know if you have any other concerns,
or
---- > need
---- > anything else. Thanks and have a nice day!
---- >
---- > Thanks & Regards
---- > Alan Sun
---- > 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.
---- > =====================================================
---- >
---- > This posting is provided "AS IS" with no warranties, and confers no
---- > rights.
---- >
---- >
---- >
---- > --------------------
---- > ---- Reply-To: "Ray" <NJRay@anon.postalias>
---- > ---- From: "Ray" <NJRay@anon.postalias>
---- > ---- Subject: RPC over HTTP failing with 400 Bad Request on Proxy
---- > ---- Date: Thu, 7 Oct 2004 13:53:58 -0400
---- > ---- Lines: 18
---- > ---- X-Priority: 3
---- > ---- X-MSMail-Priority: Normal
---- > ---- X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
---- > ---- X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
---- > ---- X-RFC2646: Format=Flowed; Original
---- > ---- Message-ID: <#JXTnZJrEHA.1036@TK2MSFTNGP10.phx.gbl>
---- > ---- Newsgroups: microsoft.public.exchange.connectivity
---- > ---- NNTP-Posting-Host: c7144711.state.nj.us 199.20.71.17
---- > ---- Path:
cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
---- > ---- Xref: cpmsftngxa06.phx.gbl
---- > microsoft.public.exchange.connectivity:98966
---- > ---- X-Tomcat-NG: microsoft.public.exchange.connectivity
---- > ----
---- > ---- I have set up RPC over HTTP acording to the many articles
---- > ---- on the net. I have verrified that I can get to my rpc
---- > ---- dir and get the 403.2 when trying to access via IE.
---- > ----
---- > ---- But when I try to connect with an outlook client an error
---- > ---- 400 Bad Request is logged.
---- > ----
---- > ---- Here is a snipit from the IIS log:
---- > ----
---- > ---- 2004-10-07 13:21:19 1.1.1.1 RPC_OUT_DATA /rpc/rpcproxy.dll
---- > mail.x.net:6002
---- > ---- 443 domain\user 2.2.2.2 MSRPC 200 0 0
---- > ---- 2004-10-07 13:21:51 1.1.1.1 RPC_IN_DATA /rpc/rpcproxy.dll
---- > mail.x.net:6004
---- > ---- 443 domain\user 2.2.2.2 MSRPC 400 0 64
---- > ----
---- > ----
---- > ---- Any ideas as to what I could be doing wrong?
---- > ----
---- > ----
---- > ----
---- >
----
----
----

Relevant Pages

  • Re: Outlook using RPC over HTTPS does not authenticate using the Kerberos Realm
    ... RPC over HTTP DOES work using both NTLM and Basic Authentication when using local domain credentials. ... It does not work when using credentials for an MIT-type Kerberos Realm. ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.exchange.admin)
  • RE: RPC over HTTP security
    ... Why not use OWA and secure it with SSL?" ... SSL does not provide Authentication, correct, but it does ... Subject: RPC over HTTP security ...
    (Security-Basics)
  • Re: Help with RPC over HTTP and requests for Credentials
    ... Also what are your settings in Outlook 2003 for Authentication. ... 827330 How to troubleshoot client RPC over HTTP connection issues in Office ... Exchange Server is the one that does not like your Credentials. ... >> My guess is that it is a Web Proxy Authentication issue, ...
    (microsoft.public.exchange.setup)
  • Re: Setting SeSecurityPrivilege on IWbemServices in C++
    ... There is no such a concept of adding a priviledge to an interface pointer. ... An RPC call has the concepts of authentication, ...
    (microsoft.public.win32.programmer.wmi)
  • Re: RPC over HTTP failing with 400 Bad Request on Proxy
    ... Click to select the Basic authentication (password is sent in clear ... The authentication option you have selected results in passwords being ... The RPC virtual directory is configured to use basic authentication. ... recommend that you use SSL together with basic authentication. ...
    (microsoft.public.exchange.connectivity)