Re: Problem with RPC over HTTP
- From: "Steve" <newsgroup@xxxxxxxxxx>
- Date: Sat, 17 Jun 2006 21:06:43 -0700
Is this ISA 2004 server actually separate from the SBS? If it is the
integrated package from Premium Edition SP1 then just running the CEICW
should have set it up on the server side without any need to set permissions
on virtual folders etc. You should also follow exactly the link to info on
the RWW page for Outlook over the Internet.
"Marcello Gorlani" <MarcelloGorlani@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:5244688D-E97D-46F5-AECA-CB0ACCD25947@xxxxxxxxxxxxxxxx
Hi,
I'm trying to set up RPC over HTTP(s) on a SBS2003 SP1 setup (Echange SP2
w/all patches).
This server is published by an ISA 2004 server.
The publishing of OWA over HTTPS works fine, certificates are trusted and
I
see my email ok.
Now I followed ALL the procedures for setting up RPC over HTTP(s):
- set the permissions on the /rpc virtual folder
When I try to use a local LAN client to test my internal setup
(outlook.exe
/rpcdiag) I always see that the client really doesn't try to use http,
always
uses tcp/ip and connects fine. I also read that this is fairly normal.
So from the outside I checked EVERY troubleshooting guide to see if the
RPC
is published correctly, and all seems ok.
Now I setup a new outlook profile on a remote client, start outlook and
I'm
asked for the username/password for the account. Looking at ISA logs, I
see
the https communication between my remote client and the internal SBS2003.
I authenticate and after a while i get:
---------------------------
Microsoft Office Outlook
---------------------------
The connection to the Microsoft Exchange Server is unavailable. Outlook
must
be online or connected to complete this action.
---------------------------
ISA log contains a lot of lines, all of them say It's all right, except
some
that display like:
Original Client IP Client Agent Authenticated Client Service Server
Name Referring Server Destination Host Name Transport MIME Type Object
Source Source Proxy Destination Proxy Bidirectional Client Host Name
Filter
Information Network Interface Raw IP Header Raw Payload Source
Port Processing Time Bytes Sent Bytes Received Result Code Cache
Information Log Record Type Log Time Client IP Destination IP Destination
Port Protocol Action Rule Client Username Source Network Destination
Network HTTP Method URL HTTP Status Code Error Information
0.0.0.0 MSRPC No Reverse
Proxy ISANAME private.siderweb.com TCP Internet - - - - - - 0 94 0 413 0x8
Web
Proxy Filter 17/06/2006
16.25.51 81.118.111.223 192.168.1.100 443 https Failed Connection
Attempt RULE
NAME anonymous External RPC_IN_DATA
http://internal.sbs.2k3:443/rpc/rpcproxy.dll?public.dns.name:593 64 0xb83
I found several people on the net having this problem, but no one with a
working solution.
Any ideas? Am I missing something?
Could the problem be the fact that the publishing certificate (the one for
people from the internet) differs from the one on the SBS2003 (for local
lan)?
I found papers on the way to use this configuration and it works for
OWA...
Bye
.
- Prev by Date: Re: Quick Question
- Next by Date: ISA 2000 clinet cannot ping Public IP
- Previous by thread: Quick Question
- Next by thread: ISA 2000 clinet cannot ping Public IP
- Index(es):
Relevant Pages
|
