outlook 2007 promted for owa credentials when connected to exchange 2007 server over LAN
im getting a prompt in outlook 2007 when Im connected to my exchange server via the LAN ( and sending and recieving mail is just fine ). I get a prompt for the user name and password to connect to our webmail address. Its says "connect to <webmail address>.net". No matter what I put in the username and password it does not take it. My account settings look fine. If i go to the settings, I am connected to the exchange server name, the cached mode is checked, and my user name is correct. In the advanced settings, on the connection tab, only connect using my LAN is checked. If i click the send/recieve button at the top of outlook, i get the following error, "task <my email address> reported error (0x8004010F) : the opereation failed. An object cannot be found." Looking up this error it states "When you try to synchronize the offline address list on a Microsoft Exchange Server 2007 server or Microsoft Exchange Server 2003 server or Microsoft Exchange Server 2010 server in Microsoft Office Outlook 2003, you may receive the following error message in the Sync Issues folder:" and to resolve it states for Exchange 2007 " In Exchange Management Console, expand Server Configuration, and then click Mailbox. In the Database Management window, right-click Properties on the mailbox store. Click the Client Settings tab, click Browse, and then click the appropriate offline address book. Click OK two times But I only have one OAB and when I check the above settings, and browse, I only have that 1 OAB and it has already been selected. So now I check my OAB settings in EMC under server configuration, client access, and click the OAB distribution tab. I have configured polling intervals for 480 minutes, and set my OAB URL's to https:// <cas>/oab for both internal and external. If i enter that address in my brower i get the same prompt im getting when using outlook. After I cancel out of the pw box, the browser shows "server error. 401 - unauthorized: access is denied due to invalid credentials. You do not have permission to view this directory or page using the credentials that you supplied." So i open IIS manager and open the default web sites and click on OAB. Under IIS i click on authentication and see that basic and windows are enabled. I then go back to the EMC and under Organization Configuration i click on mailbox and click the OAB tab here. There is only one listed here and check its properties. On the address lists tab the include the default global address list is checked. Under the distribution tab only the client support for outlook 2003 sp2 or later (version 4) is checked. Under distribution points, the enable web-based disribution is checked, and under the distribute the offline address book from these virtual directories: I have added the OAB (default web site) from server CAS. The enable public folder distribution is unchecked. So thats my settings in exchange for OAB. Is that what is causing the pw prompt for my outlook 2007. My outlook 2003 users get a sync issues folder added to there folder list and they get email with this error " 15:13:22 Synchronizer Version 11.0.8200 15:13:22 Synchronizing Mailbox 'Mapes, Sonia' 15:13:22 Done 15:13:22 Microsoft Exchange offline address book 15:13:22 0X8004010F "
December 15th, 2010 1:58pm

The error code means cannot find. If you haven't enabled public folder distribution then Outlook cannot connect to the specified directory. Does your webmail address resolve internally to the INTERNAL IP address? If not then that is probably the cause of the prompts. Exchange 2007 and higher with Outlook 2007 and higher makes extensive use of web services. Therefore SSL certificates and the internal and external URLs are key. I would start by running an autodiscover test in Outlook. Hold down CTRL while right clicking on the Outlook icon in the system tray. Choose test email autoconfiguration. Check the URLs that are returned resolve correctly. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources
Free Windows Admin Tool Kit Click here and download it now
December 15th, 2010 7:47pm

I have now enabled public folder distibution. Yes. My webmail address resolves internally to the INTERNAL IP address. I have run the autodiscover test in Outlook in the past, and it has looked fine. NOW when I run it, it says "autoconfiguration was unable to determine your settings". So i have screwed up autodiscover somehow. The powershell output for Get-AutodiscoverVitualDirectory is NAME: Autodiscover (default web site), SERVER: CAS, and InternalUrl: HTTPS://cas/autodiscover. THis looks correct to me. Am I wrong?
December 16th, 2010 11:29am

I have now enabled public folder distibution. Yes. My webmail address resolves internally to the INTERNAL IP address. I have run the autodiscover test in Outlook in the past, and it has looked fine. NOW when I run it, it says "autoconfiguration was unable to determine your settings". So i have screwed up autodiscover somehow. The powershell output for Get-AutodiscoverVitualDirectory is NAME: Autodiscover (default web site), SERVER: CAS, and InternalUrl: HTTPS://cas/autodiscover. THis looks correct to me. Am I wrong? if I put https://cas/autodiscover in the brower it gets the "security certificate presented by this website was issued for a a different website address" messge and wants you to click the "continue to this website" link. When I click it I get the "website cannot display the page" messge. Should not I be getting the xml information? If I use our external address https://webmail.ourName.net/autodiscover (which resolves to cas like above), i get the credentials promp like what happens in my outlook. It wont accept the user name and password though. And there is no display of the XML autodiscover file.
Free Windows Admin Tool Kit Click here and download it now
December 16th, 2010 11:30am

You (or whoever setup the server) have made a very common mistake - setting the autodiscover URL on set-autodiscovervirtualdirectory It should be blank for most deployments. You will need to set it back to $null. The autodiscover URL is actually set on the set-clientaccessserver (note the tripe S in the middle), and is the value AutoDiscoverServiceInternalUri (that is an i not an L at the end). Is your certificate a single name certificate or a UC certificate with the server's NETBIOS and FQDN listed? Simon.Simon Butler, Exchange MVP Blog | Exchange Resources
December 16th, 2010 7:16pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics