Yeh, I was really clutching at straws. This turned out to be a problem with either our NLB, or a single CAS, which refused to process connections from some clients, but not all. Rebooting the server resolved it. Simple in the end, but horrible to troubleshoot with zero errors from monitoring or event logs.
Thanks, Richard -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Susan Bradley Sent: 16 September 2013 16:59 To: [email protected] Subject: Re: [Exchange] No connection to Exchange after WSUS September cycle. Those issues were a reoffering issue, not whereby Outlook can't connect to Exchange. That blog post wouldn't explain your symptoms. 1. What version of Exchange? 2. What exact updates did you apply? 3. Are the Exchange services on the server running? a. If you installed any Exchange security updates - there were some last month in August, the process of patching Exchange disables the services, patches them and then turns them back on. If there is a hiccup in the last part of the process, the services may not be turned back on. On 9/16/2013 4:42 AM, Sobey, Richard A wrote: > > Afternoon all, > > Has anyone seen a very recent spate of issues with your customers > unable to connect to Exchange? It seems to be happening to all clients > (Outlook 2003-2007-2010) and on multiple OSes. It was all working > hunky dory on Friday last week, which is leading me to the conclusion > that Microsoft's September release cycle of Windows Updates are > causing this problem. > > http://blogs.technet.com/b/office_sustained_engineering/archive/2013/0 > 9/12/september-2013-public-update-update-targeting-for-microsoft-updat > e-wsus-and-sccm.aspx > > It's too good a possibility for me to ignore, considering that other > computers still work for my customers, and OWA works on any affected > computer. > > Thoughts? > > Richard > -- So? Your thoughts? http://windowsitpro.com/industry/microsoft-attempts-ease-demise-technet-subscribers-building-replacement-mcts
