We run Exchange 2010 SP 2 RU3. We have intermittent issues with clients connecting to either CAS server. I have isolated a particular CAS server in each this has happened by updating a hosts file on my machine. The error message that the Outlook client will see is “loading profile”. On each occasion I run this command for diagnostic purposes:
test-OutlookConnectivity -Protocol:Http -TrustAnySSLCert:$true -MonitoringContext:$true
Which generates the following Output:
ClientAccessServer ServiceEndpoint Scenario Result Latency
(MS)
------------------ --------------- -------- ------ -------
CASX.domain.... autodiscover.domain.domain.local Autodiscover: Web service request. Success 234.01
CASX. domain.... myemail. domain.co.uk RpcProxy::VerifyRpcProxy. Success 31.20
CASX. domain.... myemail.domain.co.uk RFRI::GetReferral. Success 2527.35
CASX. domain.... myemail. domain.co.uk NSPI::GetProfileDetails. Success 2527.35
CASX. domain.... myemail. domain.co.uk Mailbox::Connect. Failure -1.00
CASX. domain.... myemail. domain.co.uk Mailbox::Logon. Skipped -1.00
At the same time I check the RCP Client Access logs:
2013-01-16T12:10:52.286Z,22,0,/o=RootDomain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=User.Name,,OUTLOOK.EXE,14.0.4760.1000,Classic,X.Y.Z.A,::1,ncacn_ip_tcp,,Connect,0,00:00:00.1092063,"SID=S-1-5-21-527237240-1708537768-682003330-48401, Flags=None",
This information is repeated. I have removed IPs, user names and domain names if the output looks odd.
I have compared this to when it works and this is the next step I would expect to see that is missing:
2013-01-16T12:55:41.987Z,1182,25,/o= RootDomain /ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=User.Name,,OUTLOOK.EXE,14.0.4760.1000,Classic,,,ncacn_ip_tcp,,OwnerLogon,0,00:00:00.0156000,"Logon: Owner, /o=RootDomain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=User.Name in database DatabaseName - DatabaseX last mounted on MBX.domain.rootdomain.local at 10/01/2013 09:20:01, currently Mounted; LogonId: 1",
Our AD is set up as follows:
childA.root.local – Exchange resides here.
ChildB.root.local
Root.local
We have had a number of issues with DNS and the inability of ChildA to connect to the root domain DCs. We have added forwarders for the root domain to childA as this was flagged as an issue when best practice analysis was run on the DCs. I have also seen errors on the CAS servers related to an inability to connect to a GC server. We have also had wider DNS issues too. Currently the 2003 DCs are being replaced by 2008 DCs. So I imagine changing the underlying AD environment, the foundation for Exchange is not helping. I have tried to isolate this to a particular DC but have been unable.
A reboot resolves the issue. The previously outlined test works and users can connect again. Tests such as wlbs params etc show no issues.
Are there any known issues with SP2 RU3 that coudl cause this. My feeling is it's a DNS/AD/DC issue but want to certain based on my experience with SP1 RU4.