Re: Outlook RPC over HTTp deosn't work
- From: "Les Connor [SBS MVP]" <les.connor@xxxxxxxxxxxx>
- Date: Sat, 1 Dec 2007 10:25:01 -0600
You don't need to export anything.
With XP workstations: Go to remote web workplace (or Outlook Web Access), accept the certificate prompt, 'view', and 'install' the certificate - accepting all the defaults. With Vista clients, you have to run IE as adminstrator, and then install the certificate in the specific store - trusted root certification store.
--
Les Connor [SBS MVP]
"Barry Lee" <BarryLee@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:5B3D05DB-4DB7-42AB-912A-A52756BF4774@xxxxxxxxxxxxxxxx
i have same problem .and try to export certificate to a pfx file .andinstall it to my local computer but still can't check name
can you help
"Barry Lee" wrote:
HI Nathan
i have same problem .and try to export certificate to a pfx file .and
install it to my local computer but still can't check name
can you help
barry
"Nathan Liu [MSFT]" wrote:
> Hello Lily,
>
> Thank you for posting in the SBS newsgroup.
>
> According to your description, I understand that you received the error
> message "'The connection to the Microsoft Exchange Erver is > unavailable¡"
> when you try to use RPC over HTTP to connect the Exchange Server. If I > have
> misunderstood your concern, please don't hesitate to let me know.
>
> 1. In SBS 2003, we don't have to manually configure RPC over HTTP. We > can
> follow the steps below to enable RPC over HTTP:
>
> A. Make sure you have enabled "Outlook over the Internet" and "Remote > Web
> Workplace" in the CEICW (Configure E-mail and Internet Connection > wizard),
> then you will logon to the Remote Web Workplace > (https://serverfqdn/remote)
> as a user from the remote client and look at the link for "Configure
> Outlook via the Internet". You can see it from the server by going into
> https://localhost/remote. If the option is not displayed, then the > feature
> is not configured on the server.
>
> B. Click "Configure Outlook via the Internet" and then the Web page > "Using
> Outlook via the Internet" will appear which has pretty much a step by > step
> list of instructions. 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.
>
> References:
>
> 825763 How to configure Internet access in Windows Small Business > Server
> 2003
> http://support.microsoft.com/?id=825763
>
> Windows Small Business Server 2003 Getting Started Guide
> Appendix C - Network Configuration Settings
> http://www.microsoft.com/technet/prodtechnol/sbs/2003/plan/gsg/appx_c.mspx
>
> 2. To troubleshooting RPC over HTTP related issue:
>
> A. From the Internet client, browse to https://FQDN/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.
>
> B. If URLScan is installed on the SBS server, in some configurations, > it is
> necessary to make the following changes in urlscan.ini 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
>
> In addition, you 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.
>
> Reference:
>
> 823175 Fine-tuning and known issues when you use the Urlscan utility in > an
> Exchange 2003 environment
> http://support.microsoft.com/?id=823175
>
> 3. Start outlook with the /rpcdiag switch, does that provide any > direction?
>
> 4. On the SBS server, verify if it trusts the certificate:
>
> A. Open Internet Explorer, and then in the address bar type:
> https://publishing.yourdomain.local/remote
>
> B. If the certificate is not trusted, a warning popup appears. Click > View
> Certificate, click Install Certificate, and then follow the > instructions.
>
> 5. On the SBS server, open IIS Manager, expand your server\Web Service
> Extensions, is RPC Proxy Server Extension allowed? If so, double-click > it,
> check if it is using "C:\WINDOWS\system32\rpcproxy\rpcproxy.dll". If it > is
> using "C:\WINDOWS\system32\rpcproxy.dll", remove it and add
> "C:\WINDOWS\system32\rpcproxy\rpcproxy.dll" on the Required Files tab. > Run
> "iisreset" and see how it goes.
>
> 6. How many NIC installed on your SBS server. Is ISA also installed? > Is
> there any software firewall enabled on the SBS server? Generally, for > RPC
> over HTTP, we just need to open the incoming TCP port 80 and 443 on the
> hardware firewall.
>
> 7. Please do a screen capture of this issue on the Outlook client, and > then
> attach it in your reply.
>
> I am appreciated your time and cooperation. If anything is unclear, > please
> feel free to let me know. I am looking forward to hearing from you.
>
> Best regards,
>
> Nathan Liu (MSFT)
> Microsoft CSS Online Newsgroup 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.
>
> --------------------
> >Thread-Topic: Outlook RPC over HTTp deosn't work
> >thread-index: AcWFxQ2Hc31WhoftSi61Vr9ffXKqNQ==
> >X-WBNR-Posting-Host: 203.25.66.146
> >From: "=?Utf-8?B?TGlseQ==?=" <Lily@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >Subject: Outlook RPC over HTTp deosn't work
> >Date: Sun, 10 Jul 2005 20:03:03 -0700
> >Lines: 13
> >Message-ID: <2FD717CC-D301-49FD-90A2-79440BF9D862@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.0
> >Newsgroups: microsoft.public.windows.server.sbs
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:134554
> >X-Tomcat-NG: microsoft.public.windows.server.sbs
> >
> >Hi!
> >I enabled Outlook RPC over HTTP on SBS 03 server, and followed the
> >instructions to configure Outlook 03.
> >But now Outllok can't connect anymore, at all. When it starts - comes > >up
> >with a message:
> >'The connection to the Microsoft Exchange Erver is unavailable.Outlook
> must
> >be online or connected to complete this action.' and then:
> >'Unable to open your default email folders. The information store > >could be
> >opened.'
> >
> >Please help!
> >-- > >Thanks, Lily!
> >
>
>
.
- References:
- RE: Outlook RPC over HTTp deosn't work
- From: Barry Lee
- RE: Outlook RPC over HTTp deosn't work
- From: Barry Lee
- RE: Outlook RPC over HTTp deosn't work
- Prev by Date: RE: Outlook RPC over HTTp deosn't work
- Next by Date: Re: Outlook RPC over HTTp deosn't work
- Previous by thread: RE: Outlook RPC over HTTp deosn't work
- Next by thread: RE: Outlook RPC over HTTp deosn't work
- Index(es):
Relevant Pages
|
