Re: OWA/RPC over HTTP troubleshooting tips

Ken,
Thanks for your prompt response!

I suggest you first refer to the following article to confirm if you have
configured ISA Server to publish RPC over HTTP
I believe that it is properly set-up and we have been using it for over two
years without any difficulty.

Based on your description, do you mean the issue reoccurs regularly every
two weeks?
No...it does not happen regularly. It is very intermittent and occurs at
any time during the day or week.

Does the issue only occur on the external users who attempt to access OWA
with RPC over HTTP?
The issue occurs when external users try to access the Exchange server
using their Outlook 2003 client via RPC over HTTP or when users try to
access OWA via a browser connection to the Internet.

Internal users and VPN users have not the access issue. Is it right?
This is correct for the internal users and for the external users that
utilize the Outlook 2003 client via a VPN connection.

In addition, when the issue occurs, what is the error message when the users
try to access OWA with RPC over HTTP?
I am not positive on the verbiage but it states something like "a
connection could not be made to the back end server".
I am not clear on your reference "OWA with RPC over HTTP". I thought that
OWA utilized a different protocol than RPC over HTTP.

I will review the other links you provided to help me gain a better insight
on what possibilities may exist to troubleshoot the problem. As you are no
doubt aware, e-mail is a very critical system within every organization so
my window of opportunity to troubleshoot the issue is very narrow.

Thanks again for your response and I look forward to whatever other
information you can provide.

Martin


""Ken Zhao [MSFT]"" <v-kzhao@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:N5m9Qp81GHA.4280@xxxxxxxxxxxxxxxxxxxxxxxx
Hello Martin,

Thank you for using newsgroup!

From your post, I suggest you first refer to the following article to
confirm if you have configured ISA Server to publish RPC over HTTP.
884506: How to configure ISA Server 2004 to allow for RPC over HTTP client
connections from Office Outlook 2003 to Exchange Server 2003
http://support.microsoft.com/?scid=kb;en-us;884506

Based on your description, do you mean the issue reoccurs regularly every
two weeks? I know the ISA server will not pass any connections to my
back-end Exchange 2003 server. Does the issue only occur on the external
users who attempt to access OWA with RPC over HTTP? Internal users and VPN
users have not the access issue. Is it right?

In addition, when the issue occurs, what is the error message when the
users try to access OWA with RPC over HTTP?

More Reference:
===============
How ISA Server 2004 Provides SSL VPN Functionality for Outlook Web Access
and RPC over HTTP
http://www.microsoft.com/technet/community/columns/secmvp/sv0405.mspx

Using ISA Server 2004 with Exchange Server 2003
http://www.microsoft.com/technet/isa/2004/plan/exchage2003.mspx

Thanks & Regards,

Ken Zhao

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.




--------------------
| From: "Martin" <bstsolutions@xxxxxxxxxxxxxxxx>
| Subject: OWA/RPC over HTTP troubleshooting tips
| Date: Wed, 13 Sep 2006 16:52:49 -0700
| Lines: 20
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
| X-RFC2646: Format=Flowed; Original
| Message-ID: <e6jP5#41GHA.1548@xxxxxxxxxxxxxxxxxxxx>
| Newsgroups: microsoft.public.isa
| NNTP-Posting-Host: 207.47.90.94.static.nextweb.net 207.47.90.94
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.isa:68280
| X-Tomcat-NG: microsoft.public.isa
|
| Hi All,
|
| First of all I apoligize if this is not the correct forum for this post
but
| I just do not know where to start with this one.
| I have ISA 2004 SP2 hosting forms based authentication to OWA over
SSL.in
| addtion to RPC over HTTP. My problem is that every once in a while
| (approximately every two weeks) the ISA server will not pass any
connections
| to my back-end Exchange 2003 server. There are no entries in any event
log
| on either the ISA or Exchange machine and the only way to re-establish
| connectivity is to reboot the Exchange server.
| I am posting it here because the internal users are not affected nor are
| those who access via a VPN connection. My goal is to either have someone
| respond if they have had this problem or get feedback on possible
| troubleshooting techniques to resolve the problem.
|
| Many thanks in advance,
|
| Martin
|
|
|



.

Relevant Pages

  • Re: OWA/RPC over HTTP troubleshooting tips
    ... very critical system and you have not more chances to troubleshoot the ... | configured ISA Server to publish RPC over HTTP ... | Does the issue only occur on the external users who attempt to access OWA ...
    (microsoft.public.isa)
  • RE: OWA/RPC over HTTP troubleshooting tips
    ... confirm if you have configured ISA Server to publish RPC over HTTP. ... I know the ISA server will not pass any connections to my ...
    (microsoft.public.isa)
  • Re: RPC over HTTP not working anymore after profile re-created
    ... I can access OWA yes and sucessfully also. ... How do i try to connect RPC over HTTP within the LAN? ...
    (microsoft.public.exchange.admin)
  • Re: RPC to HTTP with ISA!
    ... What specifically is not working with RPC over HTTP? ... > working on SBS 2003, Thank for the answer, but I forget to ... > I have SBS 2003 Premium, I have installed ISA server, ...
    (microsoft.public.windows.server.sbs)
  • RPC over HTTP not working externally
    ... I have the following configuration and have everything working except RPC ... I'm sure this must be an ISA issue since RPC over HTTP to the exchange ... OWA works from the internet ... ISA SERVER 2004 ...
    (microsoft.public.isa.configuration)