Re: HELP RPC over HTTP
From: Mark Arnold [MVP] (mark_at_mvps.org)
Date: 08/17/04
- Next message: Rolf Löchter: "Web Link im Aufgabenberei"
- Previous message: Mark Arnold [MVP]: "Re: Exchange 5.5 Database"
- In reply to: Exchange disaster recovery: "HELP RPC over HTTP"
- Next in thread: Exchange disaster recovery: "Re: HELP RPC over HTTP"
- Reply: Exchange disaster recovery: "Re: HELP RPC over HTTP"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 17 Aug 2004 10:17:54 +0100
"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
- Next message: Rolf Löchter: "Web Link im Aufgabenberei"
- Previous message: Mark Arnold [MVP]: "Re: Exchange 5.5 Database"
- In reply to: Exchange disaster recovery: "HELP RPC over HTTP"
- Next in thread: Exchange disaster recovery: "Re: HELP RPC over HTTP"
- Reply: Exchange disaster recovery: "Re: HELP RPC over HTTP"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
