RPC over HTTP failing with 400 Bad Request on Proxy

[Ray]

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?

[Alan Sun [MSFT]]

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" <NJ...@anon.postalias>
---- From: "Ray" <NJ...@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: <#JXTnZJr...@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?
----
----
----

[Ray]

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-a...@online.microsoft.com> wrote in message
news:Nq7d1sQ...@cpmsftngxa06.phx.gbl...

[Alan Sun [MSFT]]

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" <NJ...@anon.postalias>
---- From: "Ray" <NJ...@anon.postalias>

---- References: <#JXTnZJr...@TK2MSFTNGP10.phx.gbl>
<Nq7d1sQ...@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: <emVm1xVr...@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-a...@online.microsoft.com> wrote in message
---- news:Nq7d1sQ...@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" <NJ...@anon.postalias>
---- > ---- From: "Ray" <NJ...@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: <#JXTnZJr...@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?
---- > ----

---- > ----
---- > ----
---- >
----
----
----

[Alan Sun [MSFT]]

Hi Ray,

Just checking in to see if the information I provided can help on this
issue.
Please let us know if you would like further assistance.

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.

--------------------
X-Tomcat-ID: 130782485
References: <#JXTnZJr...@TK2MSFTNGP10.phx.gbl>
<Nq7d1sQ...@cpmsftngxa06.phx.gbl>
<emVm1xVr...@TK2MSFTNGP12.phx.gbl>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
From: v-a...@online.microsoft.com (Alan Sun [MSFT])
Organization: Microsoft
Date: Mon, 11 Oct 2004 06:22:48 GMT

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

X-Tomcat-NG: microsoft.public.exchange.connectivity
Message-ID: <WUIToq1...@cpmsftngxa06.phx.gbl>
Newsgroups: microsoft.public.exchange.connectivity
Lines: 222
Path: cpmsftngxa06.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.exchange.connectivity:99017
NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122

[Alan Sun [MSFT]]

Hey Ray,

As I have not got a response for you, I would like to verify whether the
issue has been resolved.

If there is anything unclear in my previous reply, please do not hesitate
to let me know.

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.

--------------------
X-Tomcat-ID: 219092246
References: <#JXTnZJr...@TK2MSFTNGP10.phx.gbl>
<Nq7d1sQ...@cpmsftngxa06.phx.gbl>
<emVm1xVr...@TK2MSFTNGP12.phx.gbl>
<WUIToq1...@cpmsftngxa06.phx.gbl>

MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
From: v-a...@online.microsoft.com (Alan Sun [MSFT])
Organization: Microsoft

Date: Tue, 12 Oct 2004 08:56:32 GMT

Subject: Re: RPC over HTTP failing with 400 Bad Request on Proxy
X-Tomcat-NG: microsoft.public.exchange.connectivity

Message-ID: <XdyGWlDs...@cpmsftngxa06.phx.gbl>
Newsgroups: microsoft.public.exchange.connectivity
Lines: 288
Path: cpmsftngxa06.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.exchange.connectivity:99050
NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122

[Ray]

Alan,
Sorry for the delayed response, I was away in Europe last week.

I have the IIS virtual directories set up as you suggested which corresponds
to the original directions I followed here
http://support.microsoft.com/?id=833401 .

I am still getting the same result.

Ray

"Alan Sun [MSFT]" <v-a...@online.microsoft.com> wrote in message

news:vbt%238bdsE...@cpmsftngxa10.phx.gbl...

[Alan Sun [MSFT]]

Hi Ray,

Thanks for your posting back.

As for the current situation, I suggest you go through all the steps in the
following article:

833401 How to configure RPC over HTTP in Exchange Server 2003:
http://support.microsoft.com/?id=833401

Especially check the registry key for ports configuration.

I am looking forward to hearing from you. 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" <NJ...@anon.postalias>
From: "Ray" <NJ...@anon.postalias>

References: <#JXTnZJr...@TK2MSFTNGP10.phx.gbl>
<Nq7d1sQ...@cpmsftngxa06.phx.gbl>
<emVm1xVr...@TK2MSFTNGP12.phx.gbl>
<WUIToq1...@cpmsftngxa06.phx.gbl>

<XdyGWlDs...@cpmsftngxa06.phx.gbl>
<vbt#8bdsEH...@cpmsftngxa10.phx.gbl>

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

Date: Tue, 19 Oct 2004 11:20:27 -0400
Lines: 397
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: <eZi#s7etEH...@TK2MSFTNGP09.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!TK2MSFTNGP09.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.exchange.connectivity:99156
X-Tomcat-NG: microsoft.public.exchange.connectivity

[Ray]

I stepped through the procedure again with no luck.
I also had another tech walk through the steps to verify that our set up
follows the instructions and we can't find anything that's misconfigured.

"Alan Sun [MSFT]" <v-a...@online.microsoft.com> wrote in message

news:cKSe17yt...@cpmsftngxa10.phx.gbl...

[Ray]

I've gotten to the point where the RPC ping tool works and returns a 200 in
the IIS log but when I try to connect with Outlook 2003 it still logs a 400
"Bad
Request" in the IIS log. Any ideas?

"Ray" <NJ...@anon.postalias> wrote in message
news:ejBrwpDu...@TK2MSFTNGP15.phx.gbl...

[Alan Sun [MSFT]]

Hi Ray,

Thanks for your posting pack.

As RPCPing tool works properly and Outlook still cannot connect to Exchange
server via RPC over HTTP, it is mostly related to the Outlook problem.
Thusly, I suggest you perform the following steps to troubleshoot the issue:

1. On the external client, add the following entry into the Hosts file:
IP_address_of_the_exchange_server your_exchange_server_internal_FQDN

2. Configure a new profile with an Exchange account using RPC over HTTPS.
During configuration, please use your_exchange_server_internal_FQDN instead
of the external FQDN.

3. Use this profile to test this issue again.

4. Also, test the issue on some internal Outlook client.

Please inform me of the results at your convenience. 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" <NJ...@anon.postalias>
From: "Ray" <NJ...@anon.postalias>
References: <#JXTnZJr...@TK2MSFTNGP10.phx.gbl>
<Nq7d1sQ...@cpmsftngxa06.phx.gbl>
<emVm1xVr...@TK2MSFTNGP12.phx.gbl>
<WUIToq1...@cpmsftngxa06.phx.gbl>
<XdyGWlDs...@cpmsftngxa06.phx.gbl>
<vbt#8bdsEH...@cpmsftngxa10.phx.gbl>

<eZi#s7etEH...@TK2MSFTNGP09.phx.gbl>
<cKSe17yt...@cpmsftngxa10.phx.gbl>
<ejBrwpDu...@TK2MSFTNGP15.phx.gbl>

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

Date: Fri, 22 Oct 2004 14:50:29 -0400
Lines: 551

X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180

X-RFC2646: Format=Flowed; Response

X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180

Message-ID: <ODeQ#eGuEH...@TK2MSFTNGP12.phx.gbl>

Newsgroups: microsoft.public.exchange.connectivity
NNTP-Posting-Host: c7144711.state.nj.us 199.20.71.17
Path:

cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12
.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.exchange.connectivity:99782
X-Tomcat-NG: microsoft.public.exchange.connectivity

[DearK]

Hi Alan/Ray

Please excuse my jumping into this conversation - but - I happen to have
same symptoms. The rpcping returns a 12007 error from teh client via the
internet but it works fine if I try it on the server direct (proxy/exchange
all on one machine).

Whats more puzzling is that it's working for an existing client machine so I
suspect the server is all seup ok.

Any hints?

Many Thanks in Advance for any help,
Dirk in sunny Tassie (Australia)

[Alan Sun [MSFT]]

Hi Dirk,

Thanks for your posting here.

Please understand that our partner newsgroup is an issue based service, and
we usually handle one issue in one post to avoid confusion, as well as to
ensure that our results are accurate. Therefore, if the issue persists
after you try the suggestions I have mentioned, please submit a new post.
Thanks for your understanding.

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.

--------------------
Thread-Topic: RPC over HTTP failing with 400 Bad Request on Proxy
thread-index: AcS9VAXXGiZMc6FtRb6rxkPhOZOZAw==
X-WBNR-Posting-Host: 203.20.58.1
From: "=?Utf-8?B?RGVhcks=?=" <De...@discussions.microsoft.com>

References: <#JXTnZJr...@TK2MSFTNGP10.phx.gbl>
<Nq7d1sQ...@cpmsftngxa06.phx.gbl>
<emVm1xVr...@TK2MSFTNGP12.phx.gbl>
<WUIToq1...@cpmsftngxa06.phx.gbl>
<XdyGWlDs...@cpmsftngxa06.phx.gbl>
<vbt#8bdsEH...@cpmsftngxa10.phx.gbl>

<eZi#s7etEH...@TK2MSFTNGP09.phx.gbl>
<cKSe17yt...@cpmsftngxa10.phx.gbl>

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

Date: Thu, 28 Oct 2004 18:10:04 -0700
Lines: 534
Message-ID: <4694ABCD-75C1-4F06...@microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.exchange.connectivity
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.exchange.connectivity:99853
X-Tomcat-NG: microsoft.public.exchange.connectivity

[Ray]

I'm still having the same problem. The RPC Ping tool works now but Outlook
just hangs when I try to connect with it.
I have been reading all of the other RPC posts in this group and from what
i've read there should be nothing else to set up.
Need help.....

"Ray" <NJ...@anon.postalias> wrote in message

news:ODeQ%23eGuE...@TK2MSFTNGP12.phx.gbl...

[Alan Sun [MSFT]]

Hi Ray,

Thanks for your posting back.

As RPCPing is working properly, the problem seems replacted to the Outlook
clients. I suggest you test the issue on multiple Outlook clients to narrow
down the issue.

If anything is unclear, just post back to let me know. 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" <NJ...@anon.postalias>
From: "Ray" <NJ...@anon.postalias>
References: <#JXTnZJr...@TK2MSFTNGP10.phx.gbl>
<Nq7d1sQ...@cpmsftngxa06.phx.gbl>
<emVm1xVr...@TK2MSFTNGP12.phx.gbl>
<WUIToq1...@cpmsftngxa06.phx.gbl>
<XdyGWlDs...@cpmsftngxa06.phx.gbl>
<vbt#8bdsEH...@cpmsftngxa10.phx.gbl>

<eZi#s7etEH...@TK2MSFTNGP09.phx.gbl>
<cKSe17yt...@cpmsftngxa10.phx.gbl>
<ejBrwpDu...@TK2MSFTNGP15.phx.gbl>
<ODeQ#eGuEH...@TK2MSFTNGP12.phx.gbl>

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

Date: Mon, 13 Dec 2004 09:35:06 -0500
Lines: 575

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; Response
Message-ID: <#uYPHCS4...@TK2MSFTNGP12.phx.gbl>

Newsgroups: microsoft.public.exchange.connectivity
NNTP-Posting-Host: c7144711.state.nj.us 199.20.71.17
Path:

cpmsftngxa10.phx.gbl!TK2MSFTFEED02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12
.phx.gbl
Xref: cpmsftngxa10.phx.gbl
microsoft.public.exchange.connectivity:100514
X-Tomcat-NG: microsoft.public.exchange.connectivity

[Alan Sun [MSFT]]

Hi Dirk,

Thanks for your posting here.

Please first understand that we generally focus on one issue in a post to
avoid misunderstanding. Although the symtoms you encountered is similar, it
may be caused by different reason. You may try the suggestions I provided
in this post, If the issue persists, please submit a new request. Thanks
for your understanding.

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.

--------------------

Thread-Topic: RPC over HTTP failing with 400 Bad Request on Proxy
thread-index: AcS9VAXXGiZMc6FtRb6rxkPhOZOZAw==
X-WBNR-Posting-Host: 203.20.58.1
From: "=?Utf-8?B?RGVhcks=?=" <De...@discussions.microsoft.com>

References: <#JXTnZJr...@TK2MSFTNGP10.phx.gbl>
<Nq7d1sQ...@cpmsftngxa06.phx.gbl>
<emVm1xVr...@TK2MSFTNGP12.phx.gbl>
<WUIToq1...@cpmsftngxa06.phx.gbl>
<XdyGWlDs...@cpmsftngxa06.phx.gbl>
<vbt#8bdsEH...@cpmsftngxa10.phx.gbl>

<eZi#s7etEH...@TK2MSFTNGP09.phx.gbl>
<cKSe17yt...@cpmsftngxa10.phx.gbl>

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

Date: Thu, 28 Oct 2004 18:10:04 -0700
Lines: 534
Message-ID: <4694ABCD-75C1-4F06...@microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.exchange.connectivity
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.exchange.connectivity:99853
X-Tomcat-NG: microsoft.public.exchange.connectivity

[Robert Bird]

Ray,

You seem to be having a similar problem to me ( I have posted under the
title "RPC Over HTTP on Single Server - so close, but I think So far...") on
the 21/12/04.

Can you try running the RPCPing again but this time try explicitly pinging
the 6002 / 6001 port, e.g.

rpcping -t ncacn_http -s server.mydomain.local -o
RpcProxy=mail.mydomain.org.uk -P "adminuser,mydomain,*" -I
"adminuser,mydomain,*" -H 1 -u 10 -a connect -F 3 -v 3 -e 6002

and see what happens and what you get in the IIS logs. On mine this takes 15
minutes to fail (Exception 1818 (0x0000071A)) and logs 4 events in the IIS
log. If this fails then it is unlikely Outlook will work.

It would be interesting if yours was the same. If it is what server setup
are you running - Windows 2003 / Exchange 2003 goes with out says, but ISA
2000 also and on howmany servers?

Hopefully you can reply and try and find some common ground that may help
both of us.

Rob

[Ray]

Robert,
I get the same result as you when I try to ping 6002.
I am not running an ISA server. I have a clustered Exchange 2003 SP1 system
behind a cisco firewall.
There are two nodes in the cluster but I assume that it would be considered
a single server installation since there is only one virtual server.
Ray

"Robert Bird" <Rober...@discussions.microsoft.com> wrote in message
news:FF69A622-7C8A-49A5...@microsoft.com...

[Alan Sun [MSFT]]

Hi Ray,

Thanks for your posting back.

As the RPCPing is OK, we can make sure the configuration on the Exchange
server is all correct. For the current situation, you may try to test the
issue on mutiple Outlook client bypass the ISA firewall.

You may also try to create a new account/mailbox and test the issue.

I am looking forward to your update.