I have an ISA Server 2006 RC array (we are still working on licencing for the array, thus have not moved to RTM), consisting of two servers. Behing the array I have a single Exchange server deployed.
I followed your various posts on publishing Exchange server, and it appears OWA works, as well as mobile (we still need to test it), however RPC over HTTPS is gibing us "Error code 64" when ever we test the rpcproxy.dll in a browser.
It was going pre-rc, was there changes to the way publishing worked that could have broekn this functionality?
It should still work in the RTM version. Are you delegating basic credentails? Is the ISA firewall a domain member? The 2006 ISA firewall should be falling back to basic auth when you have FBA enabled on the listener.
Edit: I found the tutorials, but I still can't get it to work.
I've created a single Exchange Web Client Access publishing rule for both OWA and Outlook RPC/HTTPs. I have a single ISA server acting as an edge firewall with the Exchange server on the internal network. I'm using SSL to the published server from ISA, the web listener uses FBA on port 443, for authentication delegation I've selected basic.
OWA is working fine, but Outlook RPC/HTTPs is not.
I've got external Outlook 2003 client configured as per the tutorial - URL to proxy server for Exchange: https://mail.domain.com, principal name for proxy server: msstd:mail.domain.com, basic authentication.
When I try to send/receive from Outlook 2003 i get the message: 1 of 2 tasks have completed successfully, Task "Microsoft Exchange Server' reported error (0x8004011D): 'The server is not available. Contact your administrator if this condition persists.'
< Message edited by alto59 -- 1.Sep.2006 8:15:01 PM >
Well, clients on the internal network, the same network where the Exchange server resides, are able to pull down their email just fine using Outlook 2003. They aren't going through the ISA server to retreive their email.
Clients on the external network, who can only reach the Exchange server through the ISA server are having problems. As I said before, OWA works fine for them, but RPC/HTTP does not.
I also cannot get RPC over HTTP through ISA to work. I've upgraded from 2004 where it worked perfectly. Now with 2006 I get numerous login prompts and cannot get past that. Everything worked fine with 2004, but with 2006 RPC is not working.
When troubleshooting RPC/HTTP, never use the real time monitoring, it will never help you troubleshoot a problem as the results look the same when its working and it's not working. This is a known issue.
I'm a bit further. It seems to work when you choose 'basic authentication' in Outlook RPC/HTTP configuration. When using the default NTLM authentication you get the numerous password prompts. In ISA 2004, NTLM did work though.
what do you mean by that ? If I delegate it should NTLM work ? I've tried different combinations with Authentication Delegation but all of them give the numerous login prompts when NTLM is selected in outlook.
I have. Problem with using basic authentication is, that the check box 'save password' is gone in the login prompt. So you have to enter your password everytime you start outlook (not a big deal though) but it's different than before.