Exchange Server - Outlook Anywhere - Autodiscovery and ISA 2006

Asked By Sven
25-Feb-08 10:40 AM
I've been testing OWA and Outlook Anywhere publishing (including
autodiscovery) in a test lab and I have the following issue:
OWA works fine but Autodiscovery and Outlook Anywhere don't work from the
Internet.

This is the setup:
ISA server - single NIC, workgroup, in DMZ, used for publishing only, LDAP
authentication
additional edge firewall
Exchange 2007 - mailbox, HT and CAS role

Autodiscovery works internally but Outlook Anywhere does not work from the
LAN nor from Internet.
RPCping troubleshooting gives me a "successfully completed result" but the
ISA logs give me results like
Status: 12239 Server requires authorization. Access to web server denied.
Status: 0x80004005
This is the result when testing autodiscovery from the Internet.
As already mentionned there are no issues with OWA (from the LAN or
Internet)4
The account I use for testing also works. I've already checked the
troubleshooting post on the ISA team blog.

Any help would be really appreciated
Sven
Exchange Server
(1)
Outlook
(1)
Autodiscovery
(1)
Firewall
(1)
Dans
(1)
Lab
(1)
RPC
(1)
  Stephen ROUX replied...
03-Apr-08 09:21 AM
Did you install RPC Proxy service on the Exchange Server ? This service is
mandatory for Outlook Anywhere to work.
Also, could you please provide more informations about your publishing rules
on ISA Server ?
help
Can nyone assist? Exchange Server Hi all, Our Two node Exchange 2003 A / P exchange HTTP virtual server failed once per week. In case I need to copy or Metabse.XML on node 2 to node 1, can anyone offer me steps how to do this? Thank you! Exchange Admin Discussions Microsoft Exchange (1) Virtual Server (1) IIS (1) DwMonitorPrimaryThread (1) DwCheckProtocolBanner (1) ExchangeCheckIsAlive (1) DwSetInstanceState (1) SMTP (1) Why would
What should I do to bring this resource online? Exchange Server Hi all, We have two node A / P exchange 2003 cluster. today, users complaint about not able to use OWA. then I find out the exchange http virtual server is offline. No matter how I try it and still not able to bring it 9 / 2008 Time: 10:57:44 AM User: N / A Computer: NODE1 Description: Cluster resource 'Exchange HTTP Virtual Server Instance 100 (EXCHANGE VIRTUAL NAME)' in Resource Group 'exchange Virtual Server' failed. For more information, see Help and
Exchange 2007 & Outlook 2007 autodiscover service Exchange Server Hi, I believe I have a pretty good handle on how the autodiscover service works in Exchange 2007. I have everything setup so that autodiscover works externally - it successfully gives the right configuration for the various Exchange web services (availability service, OOF, OAB and Unifed Messaging service) and they all work fine Outlook Anywhere even works correctly (as configured by the autodiscover service). These services are all published I have different URLs configured for the internal and external versions of each of the Exchange web services. If I choose the "test autoconfiguration" option in Outlook 2007 I can see
issues with Out of Office (Exchange Server 2007 SP1. . . . Outlook 2007 SP1) Exchange Server Good afternoon! Okay, this can possibly be one of the longest posts in the history will try to keep it short and sweet (which means 20 pages instead of 60!). Exchange Server 2007 SP1 MS Outlook 2003 SP3 / MS Outlook 2007 SP1 WIN2003 SP2 AD Four AD Sites (EXCH2007 - on box
Domain Change on SBS2003 R2 w / exchange 2003 Exchange Server I have posted this to 2 differnt groups not knowing which would actually be the for connectivity reasons and tried to use "location.orig-domain.com" as my 2nd mail server so I could utilize SharePoint and the Exchange features on the server. I have found out, not sure if it is correct or not that I cannot make "location.orig-domain.com" resolve correctly as a mail server, so as an alternative I have acquired a second url "new-domain.com" , that I configuration was correct. With the original domain no mail would send or recieve through the exchange server. DNS was set to point the URL "location.orig-domain.com" to the IP