Assuming that ISA 2006 SP1 is in a Workgroup situation, and LDAPS is being used to talk to the Domain Controllers. Can a single Web Listener be used using Basic Authentication to publish all three Exchange services?
I currently have OWA and ActiveSync running fine, but Outlook Anywhere client does not seem to be able to contact the Exchange Server, after being prompted for credentials it bombs out with a 'name cannot be resolved' message. ISA logs RPC_OUT_DATA as allowed, RPC_IN_DATA as connection attempt failed and the connection seemingly drops. I think the way that RPC over HTTP works this may not necessarily be an error though.
From: United Kingdom
You cannot benefit from KCD with workgroup so there is no value in using a dedicated listener for OA (this would remove the password prompt in Outlook). Hence a single listener can be used for all three services; you will get a password prompt in Outlook though...this may not bother you...
Thanks for your response, sorry for the late reply as I have been out of action for a few weeks.
I am stumped as to what to try next, I have the single web listener, both OWA and ActiveSync are working. Yet Outlook Anywhere just responce with a host not available.
I have OA enabled in Exchange, with Basic Authentication. If I hit the internal network with IE to /rpc/rpcproxy.dll I can see a log entry for the web page and after logging in I get a blank IE screen.
The publishing rule tests OK in ISA.
If I hit the external page, IE reports Error Code 64 Host not available. The connection to the Web server was lost. I can also see the ISA log pass the LDAP user name.
If I deliberately enter in a non-existing user or a wrong password, I am re-prompted for credentials and the user is logged in ISA as Anonymous.
It seems to me that ISA is not passing the traffic to Exchange, though LDAP component is working.
OK as pointed out by Dr. Shinder in one of his posts, not all problems are actually to do with ISA (even though at first it may look to be so), and as it turns out this particular issue I found to exactly be the case.
I have Exchange 2007 which is running on Windows 2008. I took everything back to basics which meant getting Outlook running in OA mode on the local network. I found that it would not connect via HTTPS.
Apparently RPC component is not able to connect to the DsProxy (port 6004) as it insists on using IPv6, the DsProxy however, is only listening on IPv4 and therefore will never connect.
Now I also happen to be running Exchange 2007 SP1 and have applied Rollup 4, 5 and 6. I am told that this issue apparently was supposed to be addressed in Rollup 4. For me as soon as I applied the workaround mentioned in the technet article above Outlook Anywhere connected using HTTPS locally, and without any changes to ISA started to work for external Outlook clients as well.