RPC Over HTTP Name Resolution

[Michael Brown]

I've successfully implemented RPC over HTTP internally
and would now like to expand to allow access outside the
firewall.

Currently in place: 1 ES03 BE Server, 1 ES03 FE Server
(OWA and RPC Proxy), 1 ISA Server (acting as
firewall/reverse proxy for Web publishing of OWA site).

I'm a little confused as to the name resolution
requirements. The Outlook profile needs to contain the
FQDN of the RPC Proxy server. Is this the external (ISA
published) name, or the internally resolved name? If I'm
externally publishing OWA for mail.company.com and the
internal name from the FE server is FE.company.internal,
how should the Outlook profile be configured?

Thanks in advance.

mb

 

[Diane Poremsky [MVP]]

we use internal FQDN on the first dialog account set up, same as you do when
connecting from inside. On the HTTP setup dialog we use the OWA URL that is
used from the internet.

In the reg key for the rpcproxy use all of the names that outlook will use
to locate the server - the getting started instructions appear to say it's
ok to use just NetBIOS. rpcporxy don't resolve names, so you need any and
all included in the key.

once the profile is working inside, it should work ok from outside, as long
as the URL is correct on the RPC/HTTP dialog.


--
Diane Poremsky [MVP - Outlook]
http://www.poremsky.com - http://www.cdolive.com

Expert Zone http://www.microsoft.com/windowsxp/expertzone

Search for answers: http://groups.google.com
Most recent posts to the Outlook newsgroups:
http://groups.google.com/groups?as_ugroup=microsoft.public.outlook.*&num=30