Re: RPC over HTTP Problems
- From: Bilbo <wlp<faux>fake<at>email<dot>hal-pc.org>
- Date: Fri, 17 Nov 2006 22:23:52 -0600
Hi Chace,
I've replied to your email address with the findings.
Have a good weekend,
Bilbo
On Thu, 16 Nov 2006 06:16:46 GMT, v-chacez@xxxxxxxxxxxxx (chace zhang)
wrote:
Hi,
Thank you for posting here.
According to your description, I understand this issue is: RPC-OVER-HTTP is
not working (it was setup by someone else). If I'm off base please feel
free to let me know.
To get a clear picture on this issue, please let me know the following
questions:
Does this issue occur on internal network or external?
Do you install ISA Server on SBS Server?
First, I suggest we double-check the RPC over HTTP settings by referring
the following information:
A. Click Start on your SBS server, click Server Management.
B. Click To Do List and then click "Connect to the Internet".
C. Click Next, select connection type and click Next.
D. Select Enable firewall and click Next.
E. Click Next, go through the steps until the Web Services Configuration
page shows, ensure "Outlook over the Internet" and "Remote Web Workplace"
are selected. Click Next.
F. Go through the steps until the Web Server Certificate page shows. Select
"Create a new Web server certificate", and type your FQDN
(mail.something.com) in the "Web server name" text box.
IMPORTANT: The FQDN that you type in the "Web server name" box must be the
same name that you use to connect to the Web site from the Internet. For
example, if the URL that you use to connect to OWA
<https://mail.something.com/exchange>, type "mail.something.com" (without
the quotation marks) in the "Web server name" box.
G. Click Next, and follow the instructions to finish.
H. On the remote client, log on to RWW, click "Configure Outlook via the
Internet".
I. 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.
J. Test if the you can connect at this time.
II. If the issue persists, please perform the following steps to
troubleshoot this issue:
Test the RPC virtual directory configuration
Verify that you can connect to the Rpc application on the single Exchange
Server 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 in your LAN, type the
fully qualified domain name (FQDN) address in Internet Explorer, and then
click Go: For example, type
https://mail.contoso.com/rpc
Note Substitute the FQDN of your RPC proxy server for mail.contoso.com.
If IIS is functioning correctly, and if you can successfully access the Rpc
application, (If you have applied Windows Server 2003 Service Pack 1
(SP1)), 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)
This error message is the expected behavior. This error message indicates
that the RPC Virtual Directory on the server is correctly configured.
If you have seen any other message, please capture a screen shot of the
message and send to me directly: v-chacez@xxxxxxxxxxxxxx
How to Verify RPC Virtual Directory Configuration
http://www.microsoft.com/technet/prodtechnol/exchange/guides/E2k3RPCHTTPDep/
e0bf4772-b67e-415e-beac-be082c603d80.mspx?mfr=true
2. If URLScan is installed on the SBS server, in some configurations, it
is necessary to make the following changes in urlscan.ini (which is located
in the %SystemRoot%\system32\inetsrv\urlscan folder by default) in order
for RPC over HTTP to work:
[RequestLimits]
; The entries in this section impose limits on the length
; of allowed parts of requests reaching the server.
MaxAllowedContentLength=2000000000
MaxUrl=16384
MaxQueryString=4096
You also need to add the following verbs to the Allow Verbs:
RPC_IN_DATA
RPC_OUT_DATA
After editing the ini file, restart IIS Admin Service and Microsoft ISA
Server Control services.
3. Please use RPCPing utility to check the communication. To do so, use
the following syntax:
"rpcping -t ncacn_http -s ExchangeMBXServer(ExchangeServerName) -o
RpcProxy=RpcProxyServer(SBSFQDN) -P "user,domain,*" -I "user,domain,*" -H 1
-u 10 -a connect -F 3 -v 3 -E -R none" (without the quotation marks)
If the command is not completed, please let me know the exact error
message. And in order to have a more concrete idea about the issue, please
let me know the following information.
Please create a test account for me, and let me know the following
information
- Test account credential
- Exchange Server name
- FQDN name of Proxy Server
- Domain name
I will try RPC over HTTP connection to your Exchange Server in my site.
For more information, please refer to the following article:
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/kb/831051
More detailed information:
827330 How to troubleshoot client RPC over HTTP connection issues in Office
Outlook 2003
http://support.microsoft.com/?id=827330
I appreciate your time and cooperation. If anything is unclear, please feel
free to let me know. I am looking forward to hearing from you.
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 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.
--------------------
| From: Bilbo <wlp<faux>fake<at>email<dot>hal-pc.org>
| Subject: RPC over HTTP Problems
| Date: Wed, 15 Nov 2006 14:33:02 -0600
| Message-ID: <b7tml2tv93o51s4l08ab92qc4k5jv9mc2t@xxxxxxx>
| X-Newsreader: Forte Agent 1.93/32.576 English (American)
| MIME-Version: 1.0
| Content-Type: text/plain; charset=us-ascii
| Content-Transfer-Encoding: 7bit
| Newsgroups: microsoft.public.windows.server.sbs
| NNTP-Posting-Host: h-67-101-68-35.hstqtx02.dynamic.covad.net 67.101.68.35
| Lines: 1
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:312956
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| We're trying to set up "RPC over HTTP" on a SBS 2K3 Std. SP1 (Exch 2K3
| SP2) that was set up by someone else and it's not working. It was a
| clean install -- i.e., not an upgrade.
|
| Following the client setup instructions from the RWW page ("Using
| Outlook via the Internet") are geting us nowhere and I'm surely
| looking for some help. The client profile is setup EXACTLY per these
| instructions -- at least, to the best of my ability. OWA works just
| fine and the correct certificate was saved so that no questions about
| certificates are presented at any time.
|
| Someone (not known to me) has made some changes SOMEHOW so that there
| is no named "Default Web Site". (see IIS plug-in expansion below).
| This has done a fine job of confusing me to the point I'm unsure what
| to look for in the IIS configuration.
|
| When attempting to connect, SBS presents logon dialogue but entering
| password leads to a somewhat long delay followed by re-presentation of
| the logon dialogue. Re-entering the password leads to a very prompt
| re-presentation of the logon dialogue.
|
| This server apparently had something go wrong during the application
| of SP1 to SBS 2Ke and so the Service Pack was re-applied. (The
| Windows 2K3 Server SP1 was not apparently faulty nor was the Exchange
| 2003 SP2 application - as nearly as I'm able to tell at this point).
|
| After re-application of SBS 2K3 SP1, CEICW and RAW were re-run to no
| apparent effect. CEICW "Web Services Configuration" specifies :
| "Outlook Web Access", "Remote Web Workplace", "Server performance and
| usage reports", "Outlook via the Internet".
|
| The FQDN of local server is = 15-charhost.owneridElectricalInc.local
|
| There is a properly registered public domain (much shorter) which
| properly maps to the static IP of the local router used as a front end
| (Netgear RP614v2).
|
| The server itself is home-built and centered around an AMD Athlon 64
| 3200+ CPU on an ASUS A8N-SLI Deluxe mobo.
|
| Examination of the IIS plug-in in Server Management reveals the
| following:
|
| - Internet Information Services
| - 15-charhost (local computer)
| + FTP Sites
| + Application Pools
| - Web Sites
| + ownerid Electrical Local Web Site
| + SPAMfighter Administration
| + Microsoft Sharepoint Administration
| + Sharepoint Central Administration
| + companyweb
| + OfficeScan
| + Windows Media Administration
|
| (The string "ownerid" is indeed 7 characters long.) The web site
| named "ownerid Electrical Local Web Site" expands as follows:
|
| - ownerid Electrical Local Web Site
| + _vti_bin
| + Backup
| + ClientHelp
| + ConnectComputer
| + Exadmin
| + Exchange
| + Exchange-oma
| + ExchWeb
| + Microsoft-Server-ActiveSync
| + Monitoring
| + OMA
| + Printers
| + Public
| + Remote
| + Rpc
| + RpcWithCert
| + Server shares
| + tsweb
| + aspnet_client
| + images
| + _private
| + _vti_cnf
| + _vti_log
| + _vti_pvt
| + _vti_script
| + _vti_txt
| + hpLaserJ
|
| It "looks" (to me) much like the "Default Web Site" should look but
| I've no idea if it suffices.
|
| All insights gratefully received.
|
| --
| BilBo
|
--
BilBo
.
- References:
- RPC over HTTP Problems
- From: Bilbo
- RE: RPC over HTTP Problems
- From: chace zhang
- RPC over HTTP Problems
- Prev by Date: Re: Big Problem w/ Admin accounts locked out
- Next by Date: Re: Second email for user
- Previous by thread: RE: RPC over HTTP Problems
- Next by thread: Several SBS services dead
- Index(es):
Relevant Pages
|
