Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

RPC over HTTP with no front end

0 views
Skip to first unread message

ylw...@gmail.com

unread,
Jul 27, 2005, 4:25:21 PM7/27/05
to
hi Folks,

Having an issue getting Outlook 2003 clients to communicate with
Exchange 2003 Enterprise SP1. My environment is as follows:

Enterprise server 2003 SP1 which is the (PDC, GC)
Enterprise server 2003 SP1 with exchange enterprise 2003 sp1 on top of
it. System is in the domain but not a DC or GC.

Install RPC and configure as backend, make the registry entries as
suggested for my scenario on the MS site and in this group.

RPC does not work. It seems from the documentation that I have read
that my exchnage server also needs to be the GC, but that means
promoting it to be a DC which I do not want to do. If this is not the
case then which servers need which registry entries. I have tried many
combinations but no luck.

Thanks for any help.

Kevin

Ben Hoffman

unread,
Jul 27, 2005, 6:09:48 PM7/27/05
to
Hi Kevin,

Your Exchange server does NOT need to be a DC/GC server.

Do you have a certificate installed on your Virtual server and do your
clients have the CA as a trusted Enterprise Root CA? This is a requirement.


Apart from that just make sure you have the following registry key set:

HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy
ValidPorts

Enter both the FQDN and NetBIOS name for each of these servers and port
ranges, as follows:

ExchangeServer:6001-6002;ServerName.companyname.com:6001-6002;ExchangeServer:6004;ServerName.companyname.com:6004;

Regards
--
Ben Hoffman
MCP (Win2000 Pro/Server & Exchange 2003 Admin)
http://www.ExchangeIS.com

<ylw...@gmail.com> wrote in message
news:1122495921.2...@o13g2000cwo.googlegroups.com...

ylw...@gmail.com

unread,
Jul 28, 2005, 10:32:41 AM7/28/05
to
Ben, Thanks for the reply. I am looking into the cert issues. One
more question, the registry entries that you recommend these go on the
exchange server correct? Not the pdc/gc. So there is no need to have
the RPCproxy software on the pdc/gc at all.

Thanks again, your really clearing this up for me.

-Kevin

ylw...@gmail.com

unread,
Jul 28, 2005, 4:18:16 PM7/28/05
to
Thanks Ben, it was a certificate issue. My web server cert did not
match the site in the issued to field.

Ben Hoffman

unread,
Aug 7, 2005, 2:50:25 AM8/7/05
to
Hi Kevin,

Thats correct the RCP/HTTP netwoking component is not required on the GC,
but for a single Exchange server deployment
"Step 4: (Optional) Setting the NTDS Port for Global Catalog Servers Acting
as Exchange 2003 Back-End Servers"
is Required.

Regards
--
Ben Hoffman
MCP (Win2000 Pro/Server & Exchange 2003 Admin)
http://www.ExchangeIS.com

<ylw...@gmail.com> wrote in message
news:1122561160.9...@z14g2000cwz.googlegroups.com...

0 new messages