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.
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.