Duke exonerates Apple iPhone, Cisco-based network issue at fault

After blaming Apple’s iPhone for disrupting portions of their Wi-Fi network, Duke University’s Office of Information Technology has issued a statement totally exonerating Apple’s iPhone:

By now many of you have read news accounts around iPhones and Duke’s wireless network. Some of the reports incorrectly made it sound as if our entire wireless network had collapsed. Others made it sound as if the iPhone could not work correctly on our wireless network. Still others seem to imply that Duke’s network was deficient in some way because the problem had not been encountered more broadly. The reality is that a particular set of conditions made the Duke wireless network experience some minor and temporary disruptions in service. 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. Cisco has provided a fix that has been applied to Duke’s network and there have been no recurrences of the problem since. We are working diligently to fully characterize the issue and will have additional information as soon as possible. Earlier reports that this was a problem with the iPhone in particular have proved to be inaccurate.

In closing, I extend my gratitude to the very strong technical staff within OIT that was able to identify this situation, working shoulder-to-shoulder with technical staff from two of our long-time partners, Cisco and Apple. Meanwhile, our Duke community should feel confident that both the Duke wireless network is fully functional, and the iPhone is fully operable within our environment.

Duke’s Statement (same as above) is here.

On Monday, Kevin Miller, Duke’s Office of Information Technology’s Assistant Director of IT Communications Infrastructure squarely blamed Apple’s iPhone for Duke’s networking problems, telling Network World, “My concern is how many students will be coming back in August with iPhones? It’s a pretty big annoyance, right now, with 20-30 access points signaling they’re down, and then coming back up a few minutes later. But in late August, this would be devastating… It may have something to do with the iPhone losing connectivity and then trying to reconnect in a new location… I don’t believe it’s a Cisco problem in any way, shape, or form.”

Moral of the story: In any way, shape, or form, STFU until you know WTF you’re talking about.

So, does Duke University owe Apple recompense for hundreds of damaging articles that blamed Apple’s iPhone for Duke’s Cisco problem?

A smattering of samples:
• “A single iPhone is enough to bring down a Wi-Fi network, according to staff at Duke University in North Carolina.” – vnunet.com, July 19, 2007
• “A single iPhone was powerful enough to cause the problem, and there are 100 to 150 of them registered on the network, Bill Cannon, a Duke technology spokesman, said.” – The Associated Press, July 20, 2007 (syndicated to hundreds of media outlets)
• ” One of the big selling points of Apple’s iPhone is the ability to connect to the Internet via Wi-Fi, but I.T. pros at Duke University might say otherwise. The iPhones on campus are flooding the school’s wireless LAN with as many as 18,000 access requests per second, temporarily knocking out access points for 10 to 15 minutes at a time, according to Kevin Miller, Duke’s assistant director of communications infrastructure.” – Sci Tech Today, July 18, 2007

Seems like it’d be an easy case for Apple to win if they wish to pursue it.

Contact info:
• Dr. Richard H. Brodhead, Duke University President: 919 684-2424, president@duke.edu
• Tracy Futhey, VP for Information Technology and CIO: 919 684-5300, cio-office@duke.edu
• Bob Johnson, Director Communications Infrastructure Services (CIS): 919 668-1762, robert.l.johnson@duke.edu
• Kevin Miller, Assistant Director of IT Communications Infrastructure: 919 668- 6484, kevin.miller@duke.edu

85 Comments

  1. Oh boy.
    I was hoping it was a ZUNE that brought Duke down, but it looks like the iPhone is free to roam again.

    IT Tools.

    MDN: “sales” as in “sales of CISCO just plummetted, as are Duke IT enrollments”

  2. Typical biased opinion by a Duke IT person blaming the iPhone just because it was something new rather than looking at the whole situation. Not a very good way to analyze for failures if you just asume as he did. And he did make an ass out of himself in the end when the problem was squarely a CISCO problem and had nothing to do with the iPhone.

  3. Apparently rushing to judgment – whether it be regarding the Duke Lacrosse team or the Apple iPhone – is becoming standard procedure at Duke.

    Geez, one or two iPhones are bringing down the entire Duke network. But it’s not happening anywhere else. Think maybe it could be something other than the iPhone? Maybe something specific to your network instead?

    Nah! That’s crazy talk.

  4. You, sir, are a big moron. Next time you feel a need to talk all big-headed about a technical issue please refrain and talk about your GI Joe action figures instead. Get a job at Mc Donalds ‘cuz I want your job and feel more capable of being a benefit to Duke University than you will ever be you sweaty stoked pig!

    If we lived in Turkey I’d stab you in the mouth.

  5. Okay, I’m glad they decided to eat shit and tell the truth. . . but what pisses me off more than the original shit story is what damage it caused.

    Example, I’m sitting in the break room at work checking messages on my iPhone, when someone walks in and say’s “I heard that iPhones are being banned at all College campuses cause they don’t work right” Of course they wont ever hear the news of the retraction. Geez

  6. Was it an “issue” or a problem?
    Anyway I find it very difficult how any straight thinking (or sober, sane) IT guy could blame the end users that was so clearly a networking fault. Should have been clear in about 30 seconds, guys.
    Yes, it was very stupid to go public with this IT problem, blaming the Apple iPhone…makes their OIT look dumb and shitty at the same time.
    But at least they were were big enough to own up to it and get the problem fixed.

  7. Yeah, you think that a rich kid school like Duke would have better IT equipment and better people working in their OIT than they do, but oh well…the cat’s out of the bag now.

    The whole world knows now!

  8. Yeah, because Cisco equipment is such crap.

    Come on, folks. Step back, take a deep, cleansing breath. It’s going to be OK. Apple will somehow weather this dastardly attack upon its reputation, just relax.

  9. I’ve been to Duke, even lived on campus. It did not impress me as a smartly run place.

    Their tech support for Macs was pathetic. They could not load OSX onto an iMac and kept the iMac for days, tearing it apart several times, blaming a different part every day. In the end they gave me the iMac back wihout accomplishing anything and said it was a bad battery. The battery was fine, it was a relatively new iMac! The tech guy was totally ignorant. After that I didn’t believe anything he or his IT group said.

    The whole place seemed backwards. Some of the staff were really unfriendly to anyone without a local, southern accent.

  10. It’s common knowledge that Cisco equipment is rather “loose”, enabling backdoors and such for the NSA/hackers to tap into.

    Cisco and AT&T both work very closely with the spooks, that’s why the Cisco “iPhone” was created to place leverage on Steve Jobs when he announced it. Steve bent over and took it, altered the iPhone to meet the spooks eavesdropping requirements.

    The spooks knew quite well in advance of everyone else Apple was going to announce such a device. It’s their job to know.

    By the way, consider the iPhone completely privacy insecure, as well as EFI based computers.

  11. Several years back I worked at a university in Toronto where the IT folks did the “blame the Mac” thing whenever something went wrong (usually security related). Each time it would end up being something other than the Macs, but that didn’t prevent the “blame the Mac” game from being played out again and again.

    You’d think that Duke, such a big contributor to iTunes University, would have taken the time to sort it all out.

  12. Paranoid Tin Foil Hat Dude;
    “By the way, consider the iPhone completely privacy insecure, as well as EFI based computers.”

    Must be why millions of BIOS based computers running ‘Doze have been hacked, but not a single Mac/EFI box?
    Anyone?
    Bueller?
    Fool.

  13. This ain’t over. Not by a long shot.

    I don’t see anything in Duke University’s statement that clears Apple’s iPhone for the mass disruption and havoc caused to the campus Wi-Fi network. Nothing. Apple clearly has a lot of questions to answer in addition to the apology they owe the university.

    Microsoft’s Zune doesn’t take networks down, and that’s a fact Apple lemmings. All that Wi-Fi sharing going on with the world’s greatest MP3 player in the past year and you never hear anything about networks being compromised. Only a couple of weeks out and the iPhone is causing serious problems in addition to the battery nightmare. Same old Apple—no regard for Microsoft’s established rock solid standards. Why didn’t they just license network technologies from Microsoft. We know they work. Apple always has to do it their way. Whatever.

    Kudos Kevin Miller! Don’t let Apple bully you.

    Your potential. Our passion.™

    MDN Magic Word: hope, as in I hope the Zune Phone comes soon!

  14. Must be why millions of BIOS based computers running ‘Doze have been hacked, but not a single Mac/EFI box?

    Your the fool, as you haven’t completely researched what this powerful OS independant firmware enviroment is capable of.

    EFI is there waiting for developers to place their DRM scheme laden code in there to be exploited.

    You’ve heard that 95% of exploits are based in code other than operating systems right?

    Combine this tendancy to write insecure software with a powerful firmware level that can do anything it wants independantly of the operating system and Apple is out of the secuirty loop.

    Contact the internet? check. Read hard drives? check.

    Tell the OS it can’t use the hardware or software unless it calls home? check.

    Ever research who runs the UEFI Group? ha! Your the fool.

  15. Now there is abslutely no reason to shell out that kind of money.

    EXACTLY

    IPhone = Not quite good enough yet, batter life dismall, Edge sucks.

    I’ll perhaps take revision 2. ” width=”19″ height=”19″ alt=”smile” style=”border:0;” />

  16. In a perfect world every one of these universities would have an Apple Certified Mac Tech on the IT staff, certifications kept current at all times.

    Since this this is this is not the case the best thing a student can do is to get a couple of subscriptions to good Mac publications and to have a good Mac book or two handy to help you sort things out when you have problems crop up. At least you will an idea what’s wrong even if you can’t fix it.

    Also if possible get AppleCare on the new purchase—this can be a lifesaver to a student on a tight budget. It’s worth the money.

    Lastly, if you have a problem take your Mac to an Apple Store or an Authorized Reseller for repair, not to those ham-handed monkeys like the ones that they have at Duke. They’ll just screw it up.

  17. STOP BITCHING AND MOANING AND EMAIL THIS AHOLES!!! I DID. STFU and do something! We are the counter power to the Mass FUD campaign that is rioting against such a innovative company. We are Apple’s people.

  18. Seems like it’d be an easy case for Apple to win if they wish to pursue it.

    BS.

    So how does Apple “prove” damages? While this instance certainly wasn’t GOOD for Apple’s PR, how do you put a value on it? And it what forms does Apple expect to recover damages?

    What a typical notion from today’s “Mommy make them stop, I wanna SUE!” society. Such a suit would only benefit the lawyers. ” width=”19″ height=”19″ alt=”raspberry” style=”border:0;” />

  19. Knew it was BS as soon as I read about this issue. I earned my nerd creds at a university in the late 80’s and thru the 90’s. Moved from there to Big Blue in late 90’s. Correlation is not causation. Method 101.

  20. You guys!! You got it all wrong. It was iPhones.

    It was Cisco iPhones causing the problem. ” width=”19″ height=”19″ alt=”wink” style=”border:0;” />

    now back to you regular program

  21. Seems like Duke’s got one more valid reason to stamp out the quick-mouthed-headless-morons that they call IT heads.

    I say Kevin Miller should either apologize or resign his post for dishing out irresponsible statements.

    MDN word: “hike”, as in Take a hike, Kevin.

  22. Now let us all calm down. A new phone has hit the block at very high velocity. Wi-fi system has a problem that has been highlighted either because of the iphone or it was a problem just waiting to occur.

    Fact 1:- Duke is the only place to report this particular problem, despite at least one million iphones out there in use.

    Fact 2:- Duke have raised their hands and fessed up to their error.

    Fact 3:- Open source operates on the basis that the product will be tested to destruction, any weaknesses or faults are quickly found, reported and fixed.

    Fact 4:- This is a good way to make sure that everything is stable & secure.

    Fact 5:- Cisco & Apple engineers have worked TOGETHER to resolve the problem.

    We should all be impressed by the way everything has been dealt with upto date.

    Please do not email abuse to these people, it doesn’t help anyone least of all Apple inc. & MDN

    We Applelytes should chill in situations like this because we know better!

  23. Pretty much ditto to what Crabapple said.

    I heard a story from a main distributor and integrator of wireless networking equipment (the high-end stuff like Colubris and Nomadix) a couple of years ago.

    They were called by one of their customers – an academic institution – to research why, at around lunchtime each weekday, their wireless networks would suddenly suffer something which appeared to be a broadcast storm. Even worse, some local businesses were complaining about the same thing.

    After several days of research, they finally located the cause of the problem: a pencil.

    It turned out that the handle on a microwave oven in one of the student common rooms had broken and the students, in all innocence, were using a standard pencil to somehow secure the door. The graphite in the pencil acted as a perfect antenna and was flooding the everything for about 1.5km with microwave radiation.

  24. If Duke tech dept is anything like Cornell U’s tech infrastructure people, (router installation people, network troubleshooting, wireless, etc.–not sales or personal help) they are incredibly prejudiced about Apple. I’ve had more than one smart ass anti-Apple remark from these pro-PC sheep drones. Though the Apple Division at the CIT Help Desk has always been very knowledgeable, supportive and courteous.

    So this Duke PC head’s comment didn’t surprise me at all.

    Thankfully we rarely need their help anyway.

  25. Duke is supposed to be an institution of higher learning, where one would hope to learn something about scientific inquiry, but it appears they may not be succeeding at this.

    Perhaps they learned how to think logically and scientifically from President Walker Bush (a fellow Methodist)–you know, the guy who, if he’d have been president when Pearl Harbor was attacked by the Japanese, would have invaded Korea or China instead.

    Goobers!

  26. I say good …this sort of thing will be leveraged at some level against anti-Apple bias. Dukes OIT will now publicly swallow some of their own venom …and their own reproach may already be felt by IT groups who regularly and privately congratulate each others willful anti-Apple hostility. The more this bias publicly trips over itself the more it will be challenged to explain the internal decisions it makes.

  27. They are not anti-Apple. They made a mistake.

    However we do seem to have a group of Luddites, with a hair-trigger ready to blame anything Apple. This extends well beyond Duke.

    As always: identify the problem, successfully correct it, and report. NEVER</b> conjecture in a press release.

    Gotta wonder what the response would’ve been if a MS phone was suspected of taking a network down….

  28. When I was at Duke (grad Dec 05) I found that the Peter Principle was alive and well at Duke’s IT department. The incompetents were quickly promoted to supervisory positions. The hard-working geniuses who actually knew what they were doing were too valuable to take offline.

    –Knotty

  29. @The other road warrior that hasn’t been imping me for a while. Thanks.

    @the other Zune Tang imps. Thanks, it’s all great entertainment.

    @Zune Tang,

    “This ain’t over. Not by a long shot.” I am sure it will still continue. After all isn’t that a cultural yank icon; to continue repeating something so that it becomes true? I rented “Erick the Viking this weekend to watch. I will certainly enjoy the sinking island scene.

    “I don’t see anything” You know if you stop reading right there, you are absolutely right, you sure don’t. You don’t see any Zunes out either. How many months did you say it would take for the Zune to be #1?

    “Microsoft’s Zune doesn’t take networks down”, not to mention that they don’t build networks either. Remember it is MicroSOFT, they are software, they don’t have enough to get it up into hardware. Wannabes, although I do think they make a mouse and a computer that is just a toy.

    “hope, as in I hope the Zune Phone comes soon!” Wel, you know at Microsoft, everyone has left the drawing boards to get onto the photocopiers. You are a legend of your own mind.

    @those that operate their posts a higher mental capacity than “redundant yank moron” you might remember I posted here:

    http://macdailynews.com/index.php/weblog/comments/14311/

    and talked about the great Duck Uni from the Doonesbury point of view.

    “relax everyone will be on top of it tomorrow.”

    Here comes the iPhone flood, washing out the hope of the iZune FUD.

  30. Seems a good time for this, or least selection portions:

    If you can keep your head when all about you

    Are losing theirs and blaming it on you,

    If you can trust yourself when all men doubt you

    But make allowance for their doubting too,

    Or being lied about, don’t deal in lies,

    Or being hated, don’t give way to hating,

    If you can bear to hear the truth you’ve spoken

    Twisted by knaves to make a trap for fools

    If you can do all these, Grasshopper
    Then you Get It™ about Apple, and Steve
    And might be ready to Think Different™

    Thank you Rudyard
    BC

  31. This is typical of IT types, they think knowing Microsoft crap and the crap created by computer companies to support it makes them specialist. IT should be interested in all computer technology not just the shit that will keep them employed.

    IT folks believe that being able to remedy the thousands of problems associated with a poorly designed, held together with duct tape OS like windoze is sign of intelligence. The training these hacks get is mostly windoze based. I had an argument with a professor who taught network theory, the course was mainly on Active Directory. A good network should be OS independent. Cisco seems to have designed their shit to windoze specs.

    I say flood that IT asshole with email, I say make the f****cking idiot sorry he opened his mouth against Apple.

    The revolution will be televised…. on iPhone,

  32. I find it ironic and disingenuous that this statement from Duke IT blames the press for innacurate reporting on the story given them by their OWN Assistant Director, THEN APPLAUDS their IT staff, without accepting any responsibility for the premature release to the media of their erroneous initial impressions…they come across as foolish.

  33. say make the f****cking idiot sorry he opened his mouth against Apple.

    It could also make Duke permanently ban all Apple products on campus.

    Coming across like a pack of foam-mouthed hyenas only furthers the notion that Apple users are indeed a “Cult”, part of some asshole lunatic fringe. Why should Duke even bother with Apple if any misstep brings on the kook squads?

    If someone feels a need to write, approach Duke at a professional, reasoned, and EDUCATED level. Point out what they got right, what they did wrong, and what they can do better. Above all thank them for supporting Apple, and accept their retraction of initial iPhone blame.

  34. “We Applelytes should chill in situations like this because we know better!”

    Yes, we should get together for group blowjobs.

    And lots of Anal Sex.

    And we could also tell each other how much we like our Apple products while we’re doing each other up the ass.

    Who’s in?

  35. “It may have something to do with the iPhone losing connectivity and then trying to reconnect in a new location… I don’t believe it’s a Cisco problem in any way, shape, or form.”

    The blame is not to be put on Duke University per se but to the irresponsible IT heads that blamed iPhones at the onset even WITHOUT knowing the real cause.

    IT people should know better than talk w/o “debugging”.

    anal sex? hmmm.

  36. Apple should file a HUGE (and I mean ridiculous, here) LAWSUIT against Duke. One that gets LOTS and LOTS of media coverage. One that would completely bankrupt Duke and they would never actually win.

    They should base it on the potential loss of the entirety of the iPhone business based on the most outrageous published sales projections for the next ten years. Be sure to include R&D and even get AT&T in on the deal. (You could even get Cisco in on it since they provide countless links in the wireless chains and were presumably harmed by the very public nature of Duke’s IT “issue.”)

    The point is the same as Apple’s 1984 commercial.

  37. Great comments about the people. I love Duck, it’s a university they are always getting into situations.
    Ban Apple products at Deuk? Boy, anyone who does that is getting mighty close to the *gasp* Zune Cult strategy. Pretty soon, you will see cult members walking on the street, dressed like St. Shultz from Hogan’s Heroes prancing on the street with a Zune instead of a gun of course, going “I zee nothing, I hear nothing, I know nothing”.

  38. Most of your comments are ignorant. While I find the Duke/Cisco zealotry disgusting at times, they are a pretty good I.T. shop (I am an engineer local to the area). Speaking from experience, these types of problems are not the things that are resolved or understood quickly. Networks of today are so complicated, it often takes the support of the end user device, the networking vendor, and the local networking engineers to figure out what is happening. What really happened is Kevin learned the power of the blog, and probably needs to be a little less vocal in the future and spend more time dealing with the technical issues, and less time making press releases and talking to reporters. At my organization, we have a policy against any staff talking to the press, and what Kevin did would have been grounds for a kick to the curb. This hasnt hurt the iPhone, and you MAC zealots out there that are calling and emailing him must be about 10 years old.

  39. You are wrong, bad press is bad press and that can hurt a product. A professed professional IT gives a press conference to blame a brand new, hyper popular product and he wrong. He goes so far as to unequivocally say that Cisco’s access point was not, could not be the problem. His arrogant disdain for Apple shows clear. Make no bones about it this was an attempt to make the new product look bad. He (kevin miller) was looking for his fifteen minutes of fame at the expense of Apple and he was wrong. He is getting his do. Call me a mac zealot, but the fact remains this was about knocking the iPhone down a peg. Let him bask in the glow of his arrogant folly.

  40. Apple should file a HUGE (and I mean ridiculous, here) LAWSUIT against Duke. One that gets LOTS and LOTS of media coverage. One that would completely bankrupt Duke and they would never actually win.

    So… you’re suggesting Apple should assemble a legion of the costliest lawyers available, and file a $100 trillion (yes, trillion) dollar suit against Duke. And be sure to get the press heavily involved, OJ-like. If one’s gonna be ridiculous ya might as well do it right…

    The result? The lawyers would win big (imagine the legal bills) and Apple would lose big (someone’s gotta pay those fees). Hardly seems light a worthwhile fight.

  41. Duke owes Apple big time for this.

    It doesn’t matter how much they apologize, or say publicly that they were wrong, the damage has been done, and [a href=”http://www.xmfan.com/viewtopic.php?t=82734″>asshats will spread the FUD.</a>

    MW: Price. Wow. How does it know?

  42. kevin miller (mind the capitalization) made a BIG ass out of himself. He probably as an MBA from Duke.

    He should take a lot of heat for running his mouth about things he does not know. Let’s take it to him. We know one or more of the lowly IT tech he overheard troubleshooting and discussing the issue will pay dearly for his incompetency.

  43. in the Duke U. executive dining hall….

    “Good evening, Mr. Miller. Happy to have you dining with us today. Ah, I see you’ve choosen crow as your main course. May I suggest a slice of humble pie to go with that? Of course, sir.
    And, Mr. Miller, for your crow… would you like pickapepper sauce on the side?”

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.