My current set up is Exchange 2007 single server, ALL of my internal/external URLs have been modified to use https://webmail.company.com/ I have a verisign cert installed on CAS and that cert is for webmail.company.com. Internal DNS points internal clients to the webmail address. I have recently added ISA 2006 and it does not have its own certificate. I imported the certificate from my CAS for my ISA listner and published sites all use the same listner. Here is the issue: I am testing my ISA by connecting a laptop remotely via an air card. With OWA, mail works perfectly and free busy data is pulled when creating a meeting request. With Outlook anywhere, mail is also working fine but free/busy data is not retrieved when creating a meeting request. Why would OWA pull free/busy data but Outlook Anywhere does not? Don't they both use the same URL? Again, this is only occuring when coming in through the ISA. The iSA is performing reverse proxy only and is using LDAP authentication. Outlook anywhere and all virtual directories are set to use basic authentication as well as the ISA is using basic authentication. Thank you!

Which version of Outlook? 2003 or 2007? Outlook 2007 uses the same URL as Outlook Web Access.Jim McBee - Blog - http://mostlyexchange.blogspot.com

Outllok 2007. My guess is I need an certificate for the ISA server or some traffic is trying to come back to the Outlook client that is failing.

Also, I am seeing a failure on the ISA server, port 6002 RPC_IN and RPC_OUT are failing with error code 64, the specified network name is no longer available. I weas under the impression the RPC traffic was now directed over 443?

Hi,Does the affected user have the same experience accessing Free/Busy for Outlook Anywhere in the internal environment?Please enable Outlook Logging to diagnose this issue:1. Open Outlook.2. On the Tools menu, click Options.3. On the Other tab, click Advanced Options.4. Select the Enable logging (troubleshooting) check box, and then click OK two times.5. Restart Outlook.Please locate the %Temp%\olkas folder, find the log type FB, then send it to me at v-allson@microsoft.comAdditionally, for the remote user, please press Ctrl+right click the Outlook icon in the System Tray, selete Test E-mail AutoConfiguration, uncheck Use Guessmart, click Test button, then post the result on the forum.A good online testing can help you teston this issue:https://www.testexchangeconnectivity.com/ThanksAllen

Allen,Thank you. The issue definately appears to be related to the external URL. I am going to email you the log. Thanks.~Eric

Hi,Thank you for your information.From the log, apparently the AS URL failed to be generated via Autodiscover. Please understand that the external URl of AS, OABis retrieved by using Autodiscover. For the Outlook Anywhere,Outlook takes the email address reqequest from the the end user and pares out the domain (SMTP suffix), then using the suffix Outlooks makes connection attempts using a predetermined order of URls:https://domain.com/autodiscover/autodiscover.xml or https://autodiscover.domain.com/autodiscover/autodiscover.xmlFor more information, please refer to the below article:http://technet.microsoft.com/en-us/library/bb332063.aspxThus, we need to create the corresponding the DNS entries for the external Autodiscover URL. Based your scenario, all four email domains need to be created in the DNS, and the https://webmail.bioplate.comalso need to be created since you set it as the external url for the AS.The listener and a certificate also is needed on the ISA.About this issue, you can view the below article:http://www.isaserver.org/tutorials/Publishing-Exchange-2007-Outlook-Autodiscover-2006-ISA-Firewalls.htmlhttp://technet.microsoft.com/zh-cn/library/bb794751(en-us).aspxThanksAllen