It comes as no surprise that Duke’s network issues were ultimately found to lie with Cisco and not with the Apple iPhone. After all, if this was a general issue with the iPhone, every open wifi connection in San Francisco (and other me-too gadget locales) would have been crashing just like Duke’s.
Other than applying a patch from Cisco, the root-cause remains a bit murky:
“Cisco has provided a fix that has been applied to Duke’s network and the problem has not occurred since,” the statement read. Cisco did not describe what the source of the problem was. Late on June 20, Duke released a statement elaborating on the problem and how it was resolved. “The reality is that a particular set of conditions made the Duke wireless network experience some minor and temporary disruptions in service,” said Tracy Futhey, the university’s chief information officer, in a statement. “Those conditions involve our deployment of a very large Cisco-based wireless network that supports multiple network protocols. Cisco worked closely with Duke and Apple to identify the source of this problem, which was caused by a Cisco-based network issue,” the statement said.
Sounds like one of those political non-apologies where ‘mistakes have been made’ but no admission of guilt or responsibility is offered.