I followed the 5 part article on setting up owa & rpc/http after upgrading to ISA 2006. Only difference with our configuaration is that we have exchange on the DC, and the ISA server is on the domain and is using windows authentication instead of LDAP. We're also using a commercial certificate.
OWA is still working great (as it was with ISA 2004) but I've shad no sucess get RPC/HTTP to work.
When trying to connect in Outlook 2003, I get the basic authentication window but a long timeout and then an error. Looking at the ISA server monitor I see at the same time a whole load of requests on port 135 are denied.
Do I also need to add an access rule to allow inbound/outbound access on port 135 for all users?
Also do I need to open ports 6001,6003 and 6004 on our DSL router/firewall?
Had a closer look at the ISA server monitoring log, before the denied on port 135 entries there are 4x port 443 entries for the OWA & RPC/HTTPS rule (allowed/failed/allowed/failed). Is this normal?
Also when trying to access https://mail.ourcompany.com/rpc externally, it redirects to the OWA login, where as internally we get a username/password dialog box that always leads to a 401.3 error even with an administrator username/password.
I'm guessing /rpc shouldn't redirect to the OWA login, but not sure why it would since I followed your instructions to the letter and the paths are fine in the OWA & RPC/HTTPS rule.
Problem was with part 2 of the instructions, section "Configure the RPC Proxy Server to Use Specified Ports for RPC over HTTP". Our internal FQDN differs from the external FQDN, as soon as I added the external FQDN it was ok.
Previously I only add the netbios name and the internal FQDN.