Exchange Server - Autodiscovery problem

I have a problem with Autodiscovery, I run a test from Outlook using "Test
E-mail AutoConfiguration" from internal network and get an error 0x800C8203
and 0x80004005

I sow on the net a lot of similar problems, but I was not able to find any
solution that worked for me

Any ideas what I need to check.

  Andy David {MVP} replied...

I think we would need more info what you done so far to troubleshoot
and what is configured in AD and Exchange to support autodiscovery.

  is99 replied...

This is a one server setup, with client access only from the internal
network

All the client use Outlook 2007 "Test E-mail AutoConfiguration" gives errors
If I open the url from the Email Test in IE I get certificate warning (I
guess this is because I use the default Exchange own certificate) and if I
continue I get error 600 from the XML, as far as I understand this is a
normal thing.



As I told

Server component Client Access Role failed. Exchange Server I am getting this error installing exchange 2007 on x86 hardware. I cannot find my exchange 2003 server on the domain. . . Event Type Error Event Source: MSExchangeSetup Event Category: Microsoft Exchange Setup Event ID: 1002 Date: 11 / 25 / 2007 Time: 5:42:45 PM User: N / A Computer: EXCH07-X86 Description: Exchange Server component Admin Discussions Microsoft Exchange (1) Active Directory (1) RoleNetBIOSName (1) Exchange Server (1) MSExchangeADTopology (1) Outlook (1) RoleNoSelfSignedCertificates (1) InstallModeDataHandler (1) No. I have always had the 2003 server in the uninstall exchange 2003? what do you suggest? here is part of the log [11 / 25 / 2007 6:04:07 PM] [2] Searching objects "EXCH03 DEL:0e35c0d4-81a3-4112-98a8-da65216c8f09" of type "Server" under the root [11 / 25 / 2007 6:04:07 PM] [2] Previous operation run on domain controller 'dc0xxxxx.'. [11 / 25 2007 6:04:07 PM] [2] [ERROR] Exchange server "EXCH03 DEL:0e35c0d4-81a3-4112-98a8-da65216c8f09" was not found. Please make sure you have typed it correctly. [11 / 25 / 2007 6:04:07 PM] [2] Ending processing. [11 / 25 / 2007 6:04:07 PM] [2] Ending processing. [11 / 25 / 2007 6:04:07 PM] [1

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 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 of each of the Exchange web services. If I choose the "test autoconfiguration" option in Outlook 2007 I can see that these are all set correctly. My issue is that my internal these services to the internet using basic authentication. What I do not understand is why Outlook 2007 is ever trying to access the external versions of the various Exchange web service

Exchange 2007 in a domain using Kerberos Realm authentication Exchange Server I have Exchange 2007 SP1 running in a coexistent environment with Exchange 2003 SP2, both single-server setups. Eventually is what staff use to logon to Windows, OWA, etc with. OWA works fine. Using Outlook 2003 with a user logged on to Windows as REALM \ user everything works fine. Using Outlook 2007 with a user logged on to Windows as ADdomain \ user everything works fine. Using Outlook 2007 with a user logged on to Windows as REALM \ user things break. Specifically: - Outlook 2007 cannot access the autodiscover service. I think this happened when I added the SSL

Cannot access Global Address Book Exchange Server Vista, outlook 2007, exchange 2007 When trying to access global address book, I get message: The connection to Microsoft exchange is unavailable. Outlook must be online or connected to complete this action. Offline is NOT checked, I get says: online with Microsoft exchange. Any ideas what’s wrong???????? Exchange Miscellaneous Discussions Exchange Server 2007 (1) Exchange Server 2003 (1) Windows Vista (1) Outlook 2003 (1) Outlook 2007 (1) Outlook (1) Office (1) Vista (1) Hello, Thank you for your post. My name

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 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, in the HQ site) Issue is that when a user (MS Outlook 2007 SP1) tries to use Out of Office he / she gets the error message "blah