I'm in the process of setting up an Exchange 2010 environment that runs along side an established Exchange 2007 environment. When setting up a new Outlook profile, AutoDiscover establishes the network connection and finds the server settings successfully, but fails to log on to the server displaying the error message "The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action." After clicking OK, I'm prompted with Microsoft Exchange server and Mailbox dialog screen (see attached screenshots). This happens for mailboxes that reside in Exchange 2007 and Exchange 2010. My setup for Exchange 2010 is as follows: 2 CAS, 2 HT, and 2 Mailbox server DAG. I have a Brocade hardware load balancer balancing the traffic between the two CAS servers. I have Client Access Array configured that points to the virtual IP address of the hardware load balancer for the two CAS servers. I also have the following registry keys configured on both CAS servers with static ports: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeRPC\ParametersSystem HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeAB\RpcTcpPort OWA works fine for the mailboxes I'm trying to configure through Outlook. Any ideas?

You must point Autodiscover to the Exchange 2010 server, and properly configure proxy and redirection to support the Exchange 2007 services until you've moved mailboxes off of them. http://technet.microsoft.com/en-us/library/bb310763.aspxEd Crowley MVP "There are seldom good technological solutions to behavioral problems."

Thanks for your reply and link Ed. The A record in DNS for Autodiscover is currently pointing to the Exchange 2010 CAS server NLB IP address. Redirection is working properly as I'm able to login to Exchange 2010 OWA and pull up an Exchange 2007 mailbox and also an Exchange 2010 mailbox without issue.

hi, Could you try to manually create the outlook profile not using autodiscover, see if you can open outlook. Directly enter the internal autodiscover url into the browser on your cas server, see if you can get the 600 error result. Do the operation on both cas servers. Enter the external autodiscover url into the browser on your client, see if you can get the 600 error. Can you pint the VIP? If you can, you also can try to change the external autodiscover url to point to your one cas, see if you can open outlook after you do that. hope can help you thanks, CastinLu TechNet Community Support

When I try to manually create the profile, I receive the same error. I receive the following when going to the Autodiscover URL: <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> <Response> <Error Time="11:58:46.4732644" Id="1369355851"> <ErrorCode>600</ErrorCode> <Message>Invalid Request</Message> <DebugData/> </Error> </Response> </Autodiscover> I can successfully ping the VIP on the hardware load balancer. When I manually create the Outlook profile and type in one of the Exchange 2010 CAS servers, it automatically inserts the client array FQDN but then finishes creating the Outlook profile. When the Outlook opens I receive the following error: "Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data file (.ost)."

then I don't think its server site problem , could you please check in another system . It seems client site outlook problem.connect me :- http://in.linkedin.com/in/satya11 http://facebook.com/satya.1000 Don't forget to mark helpful or answer

hi, >>>I receive the following when going to the Autodiscover URL: <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> <Response> <Error Time="11:58:46.4732644" Id="1369355851"> <ErrorCode>600</ErrorCode> <Message>Invalid Request</Message> <DebugData/> </Error> </Response> </Autodiscover> The result you get also is the result that you enter the URL from clinet? If you don't test it, please do it. Above result shows that your autodiscover is ok on server. But may be there are some problem on other aspects. Have you try to change the exchange autodiscover URL point to your one cas servers directly? I recommend that you should try it if you can and you will. If you can please give me some detail information: Your cas servers' FQDN and ip Your cas array's FQDN and ip Your external autodiscover URL and ip hope can help you thanks, CastinLu TechNet Community Support

please check all the below entry you have done correctly 1- CName entry for the autodiscover in the dns zone of domain 2-Create an SRV record in the dns zone of domain 3-pointing to Host name of Your CAS server to contact Autodiscover service 4-publish dns records in public dns You may follow this article for more details -http://technet.microsoft.com/en-us/library/bb201695.aspxconnect me :- http://in.linkedin.com/in/satya11 http://facebook.com/satya.1000 Don't forget to mark helpful or answer