RPC over HTTP/Outlook 2003 problem
Bitbob
the most part they have all setup fine and work fine. There is one machine
that continues to give me fits because it will not log onto the exchange
sever. I have checked all the setup parameters over and over again and they
are prcisely the same as all the other workstations that have been set up and
workked. This station can log on to outlook on the web just fine with the
same username & password but it refuses to accept the same when used for the
rpc login. I have checked the certificate and it is described properly in the
setup. The other workstations are working fine with the same parameters
except the username and password. Any ideas???
Nathan Liu [MSFT]
Thank you for posting in the SBS newsgroup.
According to your description, I understand that the Outlook 2003 cannot
connect to Exchange Server by using RPC over HTTP on a specific client. If
I have misunderstood the problem, please don't hesitate to let me know.
First of all, since this issue only occurs with a specific client, this
issue is most related to client side. Here, I'm glad to provide the
following information for your convenience:
1. Please kindly help me double-confirm these settings:
a. On the specific client, open IE and go to https://SBSServerFQDN/remote,
log on to RWW, click "Configure Outlook via the Internet".
b. Then the Web page "Using Outlook via the Internet" will appear which has
pretty much a step by step list of instructions to configure Outlook over
HTTP on the client. If it tells you to use "server.domain.local", use that.
If it tells you to use "server.domain.com", use that. Follow the steps
exactly.
c. Test if the you can connect at this time.
2. From the specific client, browse to https://SBSServerFQDN/rpc. In order
for RPC over HTTP to work, you must be able to browse to this URL without
getting a popup warning about the certificate. You will receive the
following error on the page:
The page cannot be displayed
HTTP Error 403.2 - Forbidden: Read access is denied.
Internet Information Services (IIS)
This is normal. The idea is to be able to get to that page without getting
the popup warning about the certificate.
If the Security Alert appears, please click View Certificate, and then
click Install Certificate. Follow the on-screen instructions to install the
certificate, restart IE and check if you still receive the warning.
3. Let's use RPCPing to see the result returned by the utility according
the article below:
rpcping -t ncacn_http -s servername -o RpcProxy=proxyserver.company.com -P
"user,domain,*" - I "user,domain,*" -H 1 -u 10 -a connect -F 3 -v 3 -E -R
none
How to Use the RPC Ping Utility to Troubleshoot Connectivity Issues with
the Exchange Over the Internet Feature in Outlook 2003
http://support.microsoft.com/?id=831051
4. Please kindly refer to the following KB article to troubleshoot this
issue:
827330 How to troubleshoot client RPC over HTTP connection issues in Office
Outlook 2003
http://support.microsoft.com/?id=827330
833401 How to configure RPC over HTTP on a single server in Exchange Server
2003
http://support.microsoft.com/?id=833401
325930 How to troubleshoot connectivity issues that are caused by RPC
client protocol registry entries
http://support.microsoft.com/?id=325930
Best regards,
Nathan Liu (MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS 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/Outlook 2003 problem
>thread-index: AcX1OBTVf0Y48UljSYG9k+kLOkY0bA==
>X-WBNR-Posting-Host: 69.88.120.138
>From: =?Utf-8?B?Qml0Ym9i?= <Bit...@discussions.microsoft.com>
>Subject: RPC over HTTP/Outlook 2003 problem
>Date: Tue, 29 Nov 2005 14:56:06 -0800
>Lines: 10
>Message-ID: <D0628E74-4760-4D27...@microsoft.com>
>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.0
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:226468
>X-Tomcat-NG: microsoft.public.windows.server.sbs