Welcome to ISAserver.org

RPC_IN_DATA

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA 2006 Publishing] >> Exchange Publishing >> RPC_IN_DATA

Page: [1]

Message

<< Older Topic Newer Topic >>

RPC_IN_DATA - 14.Aug.2007 1:15:14 PM

garkin88

Posts: 10
Joined: 21.Apr.2005
From: Fort Lauderdale
Status: offline

I have read hundreds of sugeestions and checked configs umpteen times, only to still get a connection refusal from the 2003 Exchange server on the RPC_IN_DATA. RPC_OUT is always allowed and connection inside the firewall works perfect. From outside of the ISA2006, it has never connected.
All the usual settings match Tom's article, http filters match Microsoft recommend, split DNS correct, host entry added to ISA, cert matches SSL is set.

Where is the break? The last thread I followed on the message board, ended with this challenge still hanging.

Please assist or publish the key reasons for this behavior.

Thanks,
Gary

Post #: 1

Featured Links*

RE: RPC_IN_DATA - 14.Aug.2007 2:27:43 PM

spouseele

Posts: 12782
Joined: 1.Jun.2001
From: Belgium
Status: offline

Hi Gary,

check out Jim's blogs at:

- http://blogs.technet.com/isablog/archive/2007/08/13/testing-rpc-over-http-through-isa-server-2006-part-1-protocols-authentication-and-processing.aspx

- http://blogs.technet.com/isablog/archive/2007/08/13/testing-rpc-over-http-through-isa-server-2006-part-2-test-tools-and-strategies.aspx

- http://blogs.technet.com/isablog/archive/2007/08/13/testing-rpc-over-http-through-isa-server-2006-part-3-common-failures-and-resolutions.aspx

HTH,
Stefaan

(in reply to garkin88)

Post #: 2

RE: RPC_IN_DATA - 15.Aug.2007 10:04:35 AM

garkin88

Posts: 10
Joined: 21.Apr.2005
From: Fort Lauderdale
Status: offline

Stefaan;

thanks for the links & reply. It has cleared up some assumptions; however, I am still in the same boat. For Clarity, I will describe the setup and show the challenge, in case anyone has similarly found the solution.

ExchSvr - Exchange(6.5.7638.1), DC, AD, IIS 6.0 - RpcProxy(SSL) & OWA(non SSL), W2003 SP2

FwSrv - ISA 2006, IIS 6.0 (SMTP only), W2003 SP2

MainDC - AD, GC, DNS, W2003 SP2

(cert) webmail.mydomain.com - on ExchSrv IIS & ported to ISA listener
DNS (outside to External ISA NIC), (Inside to Internal NIC)
****
Query ISA for rcp traffic- repeats on several ports in URL
To ExchSrv - 443 - https - allowed connection - rpc over http - ( from client) RPC_OUT_DATA

To Exchsrv - 443 - https - failed Connection Attempt - rpc over http - (from client) RPC_IN_DATA
*****
Using RpcPing - with -t ncacn_http ..... -H 2 -u 10 -a connect -F 3 -v 3 -E -R none
Response from server received: 401
Client is not authorized to ping RPC proxy

I will accept any advice.

Thanks Gary

< Message edited by garkin88 -- 15.Aug.2007 10:19:03 AM >

(in reply to spouseele)

Post #: 3

RE: RPC_IN_DATA - 16.Aug.2007 3:46:57 PM

spouseele

Posts: 12782
Joined: 1.Jun.2001
From: Belgium
Status: offline

Hi Gary,

are you sure RPC over HTTP works on the internal network?
How did you verify it?

HTH,
Stefaan

(in reply to garkin88)

Post #: 4

RE: RPC_IN_DATA - 16.Aug.2007 8:59:41 PM

garkin88

Posts: 10
Joined: 21.Apr.2005
From: Fort Lauderdale
Status: offline

Hey Stefaan;

No it is not working internally either, it is using tcp/ip I discovered through some of the testing. It all seems to be focused around the RPC_IN_DATA not allowed in the ISA. It states from IE that it is blocked through the http filter.

To add to this, OWA has been working for the past 2 years using https from the outside and http from the ISA to Exchange. I have been trying not to affect the OWA and just publish the RPC proxy and ISA rule. I believe I have taken each piece apart and redone them several times. This is surely 1 little item I have not found or am overlooking.

any ideas?
Gary

< Message edited by garkin88 -- 16.Aug.2007 9:11:21 PM >

(in reply to spouseele)

Post #: 5

RE: RPC_IN_DATA - 17.Aug.2007 8:06:25 AM

spouseele

Posts: 12782
Joined: 1.Jun.2001
From: Belgium
Status: offline

Hi Gary,

quote:

No it is not working internally either, it is using tcp/ip I discovered through some of the testing.

You must get it working first internally because it sounds you have a problem with the RPC Proxy server. You can 'force' Outlook to try first RPC over HTTP internally by enabling the flag On fast networks, connect using HTTP first, then connect using TCP/IP. Then use the Outlook Connection Status screen to verify how Outlook has connected.

HTH,
Stefaan

(in reply to garkin88)

Post #: 6