Sounds to me as if your autodiscover is configured incorrectly, either internally, externally, or both.
From: [email protected] [mailto:[email protected]] On Behalf Of Kuehn, Shannon Sent: Tuesday, December 10, 2013 11:59 AM To: '[email protected]' Subject: [NTSysADM] Peculiar Office 365 Issue Hi everyone, I have a weird, weird Office 365 issue and am hopeful the brain power on this list could potentially help! To set the stage: - We have an internal namespace (internaldomain.com) where everyone connects for internal resources (email server, file share, applications, etc.). - We also have an external namespace (gemrc.com) which is how the world views us and sends external email internally. - We just deployed Exchange 2013 in a hybrid configuration. I am in the middle of moving all archives to O365. - According to my Exchange consultant, everything appears to be configured correctly. We have an ADFS server, an ADFS proxy and a DirSync server. I verified no errors on any of those servers and the sync is happening as I can see all domain users within O365's portal. ADFS is running on the ADFS server + proxy. DirSync is seemingly running smoothly as well. - I installed Microsoft Single Sign on Assistant on every machine. - I applied the latest round of security updates to Office 2010 (including Service Pack 2 and all security updates for Service Pack 2). - I have deleted domain credentials within Credential Manager. - I have recreated mailbox profiles a plenty. The kicker? Here's what is happening: - Upon launching Outlook locally, a password prompt appears. According to everything online and my Exchange consultant, users should put in first initial + last name @gemrc.com and then their current network password. What that does is it connects users to their archive. It misses the actual internal namespace and the local account does not find itself current. Makes me think something is awry with Kerberos or something. - I then go into the Send/Receive tab and force the Exchange prompt to pop up, which I then use to connect these users to our internal namespace. The local Outlook client then is current. - This works for about 8-12 hours and then the local Outlook client goes into a Limited Connectivity state and drops the connection to both Office 365 and our internal namespace. I currently have a technical ticket open with Microsoft (waiting on a call back and if I don't get one, I'll start the calling path shortly), but thought to query the group in the event any of you have seen this. Just perplexing and I don't have enough time to run out to every mailbox and connect them daily. Thoughts? Help? Solutions? Ideas? I'm fresh out...thanks in advance! _______________________________________________________________________ Shannon Kuehn GEM Realty Capital, Inc. 900 North Michigan Avenue | Suite 1450 | Chicago, IL 60611 Direct: (312) 915-3512 | Mobile: (312) 953-4577 | Fax: (312) 915-2901 Email: [email protected]<mailto:[email protected]> | Website: http://www.gemrc.com<http://www.gemrc.com/> ________________________________________ E-MAIL CONFIDENTIALITY NOTICE: The contents of this e-mail message and any attachments are intended solely for the addressee(s) and may contain confidential and/or legally privileged information. If you are not the intended recipient of this message or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and any attachments. If you are not the intended recipient, you are notified that any use, dissemination, distribution, copying, or storage of this message or any attachment is strictly prohibited. GEM Realty Capital, Inc. and its affiliates and subsidiaries are not responsible for any recommendation, solicitation, offer or agreement or any information about any transaction, customer account or account activity contained in this communication.
