RE: RPC over HTTP troubleshooting
- From: v-chacez@xxxxxxxxxxxxx (chace zhang)
- Date: Wed, 03 Jan 2007 05:44:18 GMT
Hi,
Thank you for posting here.
From you post, I understand you can not establish RPC-OVER-HTTPS fromexternal network with non-domain account. First of all please confirm that
your situation is: login computer with a non-domain account, like a local
administrator, after that when you create an outlook profile to enable
rpc-over-http, during this period, you enter a domain credential however it
doesn't work If I'm off base, please feel free to let me know.
As you are able to use RPC-OVER-HTTPS with domain accounts, I suppose the
RPC over HTTPS issue of the Exchange servers could be caused by the
certificate trust. The web server certificate is not trusted by the IE
client natively. When we connect to the server through RPC over HTTPS,
since there is no mechanism to prompt the certificate security alert (as IE
does) to let the user to confirm the connection, if the certificate is not
trusted by the client computer, the RPC-HTTPS would not be established. At
this point, please log on OWA, do you see any security warning, if it's
ture please install this certificate as well, also please make sure that
you input the published FQDN during outlook configuration. In Exchange
Proxy Settings diaglog windows, input the vaild fqdn in "Use this URL to
connect to my proxy server for Exchange"
Also please test the RPC virtual directory configuration
Verify that you can connect to the Rpc application on the Front-End by
using SSL. This confirms that IIS is working correctly and that the
RpcProxy.dll file is working correctly. To use Internet Explorer to test
RPC and IIS functionality, in a workstation outside your LAN, type the
fully qualified domain name (FQDN) address in Internet Explorer, and then
click Go: For example, type
https://mail.mycompany.com/rpc
If you have applied Windows Server 2003 Service Pack 1 (SP1) on RPC Proxy
Server, you will receive a prompt to enter credentials three times in the
previous RPC and IIS functionality test. After you enter your credentials
on the first prompt, click OK on the second and third prompts. You do not
have to enter your credentials again.
After you have clicked OK on the second and third prompts, you receive the
following error message:
You are not authorized to view this page. You do not have permission to
view this directory or page due to the access control list (ACL) that is
configured for this resource on the Web server.
HTTP Error 401.3 - Unauthorized: Access is denied due to an ACL set on the
requested resource.
Internet Information Services (IIS)
Please let me know the result, also please configure RPC OVER HTTP on
another computer and check how will things go?
For further analysis please create a test account for me, and let me know
the following information at v-chacez@xxxxxxxxxxxxx
- Test account credential
- Exchange Server name
- FQDN name of Proxy Server
- Domain name
Reference:
833401 How to configure RPC over HTTP on a single server in Exchange Server
2003
http://support.microsoft.com/?id=833401
Hope this helps, if anything unclear, please feel free to let me know. I
look forward to your update.
Have a nice day!
Best Regards,
Chace Zhang (MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on Exchange technical issues. If you have
issues regarding other Microsoft products, you'd better post in the
corresponding newsgroups so that they can be resolved in an efficient and
timely manner. You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Thread-Topic: RPC over HTTP troubleshooting
| thread-index: Accuov/LY9atKAb4TwmdqiXnt8VukA==
| X-WBNR-Posting-Host: 162.42.230.150
| From: =?Utf-8?B?QnJpYW4=?= <c49a36a4-2142028833@xxxxxxxxxxxxxx>
| Subject: RPC over HTTP troubleshooting
| Date: Tue, 2 Jan 2007 11:20:01 -0800
| Lines: 12
| Message-ID: <1E59DF2C-4E33-47FA-814D-F5EA7B26F2B3@xxxxxxxxxxxxx>
| 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.2757
| Newsgroups: microsoft.public.exchange.connectivity
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.exchange.connectivity:252
| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| X-Tomcat-NG: microsoft.public.exchange.connectivity
|
| Trying to set up RPC over HTTP. Read thru Exchange Server 2003 Rpc over
Http
| deployment white paper from MS. Got it all set up and it works only if I
| login to connecting client as domain user. If I login as another user on
| client, it prompts for credentials, I enter domain\username and password
and
| it says Exchange server is not available. On same PC I can login as
domain
| user then open Outlook and it makes the RPC over HTTP connection just
fine.
| The client is XP sp 2 all updates, Outlook 2003, RPC over HTTP is set to
use
| same IP as OWA and OMA do minus the /exchange part. The server is
Exchange
| 03 sp1 all updates, it uses SSL for OWA and OMA that white paper said
would
| work for this as well. No front end server. The rpcproxy.dll is in the
| windows\syy32\rpcproxy\ folder as the white paper specifies. What else
could
| be the issue here? Thanks
|
.
- Follow-Ups:
- RE: RPC over HTTP troubleshooting
- From: Brian
- RE: RPC over HTTP troubleshooting
- Prev by Date: Re: SOLVED
- Next by Date: Re: RPC over HTTP troubleshooting
- Previous by thread: Re: SOLVED
- Next by thread: RE: RPC over HTTP troubleshooting
- Index(es):
Relevant Pages
|
Loading
