Re: HELP RPC over HTTP

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Exchange disaster recovery (Exchangedisasterrecovery_at_discussions.microsoft.com)
Date: 08/17/04 

Date: Tue, 17 Aug 2004 07:55:05 -0700

Hey Mark,

thanks for the reply.

I have a question for you. We do have our own certificate but we are able
to access OWA internally and externally with no problems. The alias for our
cert is www.xyz.com. Would this cause a problem?? Should we make it
mail.xyx.com??

Also can you give me an example on the host file edit you mentioned about.

Example names
server name internally: exch1
FQDN of exchange server: exch1.xyz.com
outside address for exchange: mail.exch1.com
IP of exch1: 121.22.37.57
According to that naming example what should I add to the host file.

I have added a few entried into the host file with no luck, want to make
sure I am not doing something wrong.

thanks for all your help.

"Mark Arnold [MVP]" wrote:

> "Exchange disaster recovery"
> <Exchangedisasterrecovery@discussions.microsoft.com> wrote:
>
> >Hi, I have a huge problem. I need to setup rpc over http, I have followed
> >all the step in the KB article, Ran all updates on client machine XP pro and
> >exchange 2k3 sp1 single server configuration. I have made all registry
> >changes for the 6001...6004 addeded the ncacn registry entry. After
> >completing all these steps I am still unable to get into outlook from the
> >outside. It works fine internally but no luck from the outside. I changed
> >the authentication to basic. When testing the https://domain/rpc I get the
> >error message that you are supposed to get. I am running out of ideas an time
> >my boss this wants this up and running soon. What else am I missing or what
> >else can I look for to troubleshoot this. Do I need to open any other ports
> >on the firewall besides 80 443?
> >
> >When I try to connect I get prompted for a user name and password but then I
> >get the following to messages depending on the settings that I change withing
> >outlook. Make sure you have access to the network and the exchange server it
> >up and running. I have also ran the outlook/rpc with no luck it never
> >connects. But It is successful when I run it internally.
> >
> >Unable to contact the MS exchange server.
> >
> >I am unable to check name when attempting to connect or configuring outlook.
> >
> >Any help would be greatly appreciated as I have been at this for the last
> >four days with no luck and running out of ideas.
> >
> >thanks
> >
>
> If it works fine internally but not externally you would want to check
> firstly the firewall to make sure 443 is open to the box. Check OWA
> and make sure that comes up ok.
> Next thing is a point that has come up quite a lot over the past
> couple of weeks and is around certificates.
> For testing, people have been using a Windows certificate on the box
> and addressing the machine by https://servername.domain.com/exchange.
> This is fine internally but when they take their laptops home and
> address https://dnsname/domain.com/exchange they fail to connect. They
> run an OWA session to https://dnsname.domain.com/exchange and accept
> the little pop up box about the certificate and get on with OWA.
> This is the problem. With RPC/HTTPS you need to have a name to
> certificate match as the pop up box doesn't happen.
> The way around it is to use a hosts file which will allow you to
> connect to htps://servername.domain.com/exchange from the Internet.
> The other workaround is to use a normal, trusted certificate when
> you're ready to go into production.
>
>
> Mark Arnold MCSA MCSE+M MVP,
> FAQ: http://www.swinc.com/resource/exchange.htm
>

Relevant Pages

  • Re: Remote access to OWA
    ... After trying to access your OWA and remote sites, we found the certificate ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: OWA published in ISA (SBS 2000)
    ... You don't have to be hosting a public website (other than OWA). ... access a website using SSL, your browser checks the SSL certificate for 3 ... 1) the name on the certificate matches the name of the website. ... SSL certificate on a site was not issued by a trusted publisher, ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: OWA and RPC over HTTP
    ... traffic to be forwarded onto our Exchange server 2003. ... OWA is enabled do a private domain, but for remote users, they ... cert error because its been issued to our internal domain. ... certificate is not trusted? ...
    (microsoft.public.exchange.admin)
  • RE: RWW, OWA, mobile device sync mystery
    ... the certificate problem will not cause RWW and OWA ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Configuring SBS2003 for OWA and RWW
    ... managed newsgroups are staffed weekdays by Microsoft Support professionals. ... Western European when they access the OWA logon page. ... Microsoft CSS Online Newsgroup Support ... |>> There are two certificate issues: one arises if your certificate is not ...
    (microsoft.public.windows.server.sbs)