Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ISA 2004 blocking ports 6001:6004 to exchange server for rpc/http

Status
Not open for further replies.

DannoSV

Technical User
Jul 7, 2003
37
US
Hello,

My Front End Exchange server is on a "perimeter" network and the Back End Exchange server is on a "internal" network on the ISA server. There is a third network named "external" that is connected to the Internet.

When attempting to connect an Outlook 2003 client on the Internal network using RPC over HTTP, the following event is logged in ISA Server 2004 Standard Edition:

Destination IP Destination Port Protocol Action Rule Client IP Source Network Destination Network

BackEnd Exchange 6002 Unidentified IP Traffic Denied Connection Default rule FrontEnd Exchange Perimeter Internal

There is an existing policy that allows the Front End / Back End communication which includes http/https/rpc and other protocols. Why isn't this recognized by that rule?

Thanks for any input.
 
I created a user defined protocol for the rpc/http ports and created an access rule on the isa server to allow the exchange servers to communicate using this user defined protocol and all works.

now we need to upgrade to 2006 to take advantage of the web listeners ability to fall back to Basic Authentication when a non-browser client tries to access using FBA so we can setup OWA and RPC/HTTP using the same IP address and name space.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top