Link to home
Start Free TrialLog in
Avatar of sksaathoff
sksaathoffFlag for United States of America

asked on

Outlook cannot locate Exchange 2013 Server - "......Outlook must be online or connected..."

I have installed Exchange 2013 (MS Server 2008) in an Exchange 2007 (MS Server 2003) environment.  The Exchange 2007 box is decommissioned. However it remains as a file server.  I have both IPV6 and IPV4 running - and have disabled IPV6 in an attempt to fix this and failed.  Approximately 5 out of 50 machines made the switch to the new server.  The remaining boxes, a variety and mixture of Windows XP Pro, Vista Business, Windows 7 Pro, Outlook 2007, Outlook 2010 and Outlook 2013 give me the following message when attempting to configure Outlook:

1 - When opening Outlook:  "The connection to Microsoft Exchange is unavailable.  Outlook must be online or connected to complete this action"
2 - When trying to resolve the server name:  "The name cannot be resolved.  The connection to Microsoft Exchange is unavailable.  Outlook must be online or connected to complete this action"

I have tried the following fix with no effect:  http://support.microsoft.com/kb/2264398.  I have deleted/recreated Outlook profiles.  I have created profiles with new users.  I have upgraded from Outlook 2007 to Outlook 2010 - direct and by first completely uninstalling the old version.  I have uninstalled Outlook 2010 then installed Outlook 2013.  All with no effect.

Mobile devices connect with no issues.  Of the few PC's that do connect, all Outlook functions work fine.  All PC's were connected fine with Exchange 2007 before the upgrade.

I have just the one Exchange 2013 server, with all necessary roles installed.

I can see no pattern as to which machines connect and those that don't.  The Visa box with Outlook 2010 connects.  An XP box with 2007 connects, but others with that same combination don't.  An XP box with 2010 connects, but others with that combination don't.  Two Windows 7 boxes with Outlook 2010 connect, but several others with that same combination, placed in service at the same time, do not.  All relevant machines have all the most recent service packs and updates installed.

I can ping the mail server from all working and non-working PC's - with both IPV4 and IPV6 - by name, IP address, mail.localdomain.local and mail.publicdomain.org.
ASKER CERTIFIED SOLUTION
Avatar of Nick Rhode
Nick Rhode
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of sksaathoff

ASKER

Performed the steps in the article, plus a few other things.  No effect.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
On my primary dns server, under DNS-Servername-Forward Lookup Zones-localdomain.local-org-publicdomain, the autodiscover properties have the FQDN as autodiscover.publicdomain.org.localdomain.local.
Shouldn't it just be the local domain?
Is there somewhere else better to find this?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Gave myself credit because part of the solution was not addressed in the thread.