RE: Questions about RPC over HTTP

  • From: "Michael B. Smith" <michael@xxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Fri, 4 Mar 2005 10:05:22 -0500

That is old school - pre-RTM of Exchange 2003.
You don't dare open port 593 - and it isn't required anyway - that's
And port 6002 is no longer required.
You need to talk to the server that is doing the RPC-proxy, and you need
ports 6001 and 6004 and you need the internal FQDN, the external FQDN,
and the NetBIOS name. For some companies the internal FQDN and the
external FQDN are the same. The external FQDN should be the same thing
as whatever FQDN you have the SSL certificate for.


From: Andrew English [mailto:andrew@xxxxxxxxxxxxxxxxxxxxxx] 
Sent: Friday, March 04, 2005 10:01 AM
To: [ExchangeList]
Subject: [exchangelist] Questions about RPC over HTTP

I am looking through "Global Learning - Exchange Server 2003 -
Instructor Guide" reading up on what they say about deploying RPC over
HTTP and I have gotten down to the configuration of the rpcproxy
registry entries. This is what they say should be in your Exchange 2003
rpcproxy registry setting for VaildPorts:




I see that everyone has their own opinion on how to setup Exchange 2003
especially when it comes to the rpcproxy port values, is there any
correct way of going? Is this the correct way?




List Archives:
Exchange Newsletters:
Exchange FAQ:
Other Internet Software Marketing Sites:
World of Windows Networking:
Leading Network Software Directory:
No.1 ISA Server Resource Site:
Windows Security Resource Site:
Network Security Library:
Windows 2000/NT Fax Solutions:
You are currently subscribed to this Discussion List as:
To unsubscribe visit
Report abuse to listadmin@xxxxxxxxxxxxxx 

Other related posts: