Exchange Server

Robert Bird · Guest

I have been trying to get RPC Over HTTP working on our Server. As this is for
a charity and we got better prices buying the individual products rather than
SBS 2003 Premium so we have one server running Windows 2003, ISA 2000 and
Exchange 2003 - the money situation as a charity was never going to allow for
more than one server.

First does anyone know if you can get RPC Over HTTP running on this setup (I
know it works on SBS 2003 premium so I guess so).

I have setup the server as per the defacto Microsoft KB833401.
My certificate is OK - I can connect to https://mail.mydomain.org.uk/rpc and
get the "HTTP Error 403.2 - Forbidden: Read access is denied" with out any
Certificate prompting to prove it.

I have setup ISA server for Web Publishing as per Thomas W Shinder's
excellant article.

I have first used RPCPing to test the connection and couldn't get any joy.
This turned out to be because I had URLScan installed and need to add the
RPC_IN_DATA and RPC_OUT_DAT verbs to it. Once that was done I ran:

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 -R none

And get the response:

RPCPinging proxy server mail.naocn.org.uk with Echo Request Packet
Sending ping to server
Response from server received: 200
Pinging successfully completed in 1297 ms

So I though everything was OK but Outlook will not connect. So ran:

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 this produced the following:

Exception 1818 (0x0000071A)
Number of records is: 1
ProcessID is 400
System Time is: 12/21/2004 19:26:50:923
Generating component is 8
Status is 1722
Detection location is 323
Flags is 0
NumberOfParameters is 0

After 15 minutes (too long)!

Checking the IIS web log I can see:

2004-12-21 19:26:51 10.0.0.1 RPC_IN_DATA /rpc/rpcproxy.dll
server.mydomain.local:6002 443 mydomain\adminuser 10.0.0.1 MSRPC 200 0 0
2004-12-21 19:26:51 10.0.0.1 RPC_OUT_DATA /rpc/rpcproxy.dll
server.mydomain.local:6002 443 mydomain\adminuser 10.0.0.1 MSRPC 200 0 0
2004-12-21 19:28:54 10.0.0.1 RPC_IN_DATA /rpc/rpcproxy.dll
server.mydomain.local:6002 443 mydomain\adminuser 10.0.0.1 MSRPC 400 0 64
2004-12-21 19:41:51 10.0.0.1 RPC_OUT_DATA /rpc/rpcproxy.dll
server.mydomain.local:6002 443 mydomain\adminuser 10.0.0.1 MSRPC 200 0 0

I get 3 with return 200 (which are fine) and a 400 which isn't. You can see
from the time that it took dead on 15 mintues before it came back (does this
imply the third line with the 400 error timed out?)

The ISA Web Log shows:

194.106.59.137 anonymous MSRPC 2004-12-21 19:26:50 SERVER -
mail.mydomain.org.uk 10.0.0.1 443 http RPC_IN_DATA
http://mail.mydomain.org.uk:443/rpc/rpcproxy.dll?server.mydomain.local:6002
Inet 200
194.106.59.137 anonymous MSRPC 2004-12-21 19:26:50 SERVER -
mail.mydomain.org.uk 10.0.0.1 443 http RPC_OUT_DATA
http://mail.mydomain.org.uk:443/rpc/rpcproxy.dll?server.mydomain.local:6002
Inet 10054
194.106.59.137 anonymous MSRPC 2004-12-21 19:28:53 SERVER -
mail.mydomain.org.uk 10.0.0.1 443 http RPC_IN_DATA
http://mail.mydomain.org.uk:443/rpc/rpcproxy.dll?server.mydomain.local:6002
Inet 1460
194.106.59.137 anonymous MSRPC 2004-12-21 19:41:51 SERVER -
mail.mydomain.org.uk 10.0.0.1 443 http RPC_OUT_DATA
http://mail.mydomain.org.uk:443/rpc/rpcproxy.dll?server.mydomain.local:6002
Inet 10054

I think the return codes at the end may be of use but don't know - 200,
10054, 1460 and 10054 again.

I have tried this with the 6001 and 6004 with much the same result.

I have re-checked article 833401 until it hurts and all registry entries are
present and correct. I also look after another SBS2003 standard install
elseware and that works fine, so I know my configuration when setting Outlook
2003 is correct (which runs on Windows XP SP2).

I checked the ports 6001, 6002 and 6004 were running on the right processes
using "netstat -ano" and checking the PID against the processes in Task
Manager and all OK. I think until I can get the basic RPCPIng of port 6002 /
6001 working Outlook never will.

I have noticed that there is a difference between the 833401 article and
Microsoft's "Exchange Server 2003 RPC over HTTP Deployment Scenarios.doc" In
the Word doc for a single server and Exchange SP1 installed is says to also
go into the Exchange GUI, bring up the properties of the Exchange Server, and
in the RPC-HTTP tab select the RPC-HTTP Back-end server. I have also done
this as well, rebooted the server and still the same happens. As there is a
difference between these to Microsoft articles I am not 100% sure which is
correct.

Any ideas on how I could move this forward (without having to blat and
install SBS 2003!) would be much welcomed :-)

Rob

PS As an aside I tried connecting up Outlook on the Internal network and
setting the "DisableRpcTcpFallback" registry entry so that it forced HTTPS
only, but it still insists on connecting with TCP/IP (started Outlook with
the /rpcdiag switch) - any ideas why this is so - if I could just connect up
internally via HTTPS then I can blame ISA server but until then I am not so
sure.

PPS When I initially addded in the "RPC over HTTP Proxy" networking service
from the Windows Components it DID NOT add the RPC virtual directory for some
reason. I had to create this manually and also add the RPCProxy.dll to the
Allowed Web Extensions. I have compared this to the setup on the working
SBS2003 server I also have and it looks OK. The fact the first RPCPing
command above worked, I think comfirms this.

Jim Scheirer · Guest

Robert,

Have you found your problem yet? I have the exact same issue.. I can
ping it just fine, but when i try to ping 6001, 6002 or 6004 it sits there
for about 15-20 minutes then gives me a Exception 1818 (0x0000071A) error

can't find that error listed anywhere.

Jim Scheirer

Robert Bird · Guest

Jim,

Due to an office move the server was off over Christmas so I couldn't get
any further. This has led to another problem as I had to change the IP
address of the WAN interface due to new broadband connection and now get a
binding error when I do the rpcping, so I'll have to fix that first before I
can continue my quest!

I am getting a spare hard drive this week, so I can do a test rig and see if
I get the same problem or not - I'll post again what results I get.

Can you tell me what your software setup is - to see if you have the same as
me - we have one server running Windows 2003 Server, Exchange 2003 and ISA
2000 (like SBS2003 but with separate versions). Is yours the same? The reason
for asking is that I am not 100% sure it isn't the ISA causing the grief, but
if you haven't got that (on the same server) then I guess it isn't.

Let me know.

Rob

n1troboy · Joined: 18 May 2007 Posts: 1

I have the exact same problem and I only have a single exchange exchange backend with all the other components seperate.

any pointers would be great.

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