Slashdot Mirror

← Back to Stories (view on slashdot.org)

Duke Wireless Problem Caused by Cisco, not iPhone

Posted by CmdrTaco on from the egg-on-someone's-face dept.

jpallas writes "Following up to a previous Slashdot story, it now turns out that the widely reported problems with Duke University's wireless network were not caused by Apple's iPhone. The problem was actually with their Cisco network. Duke's Chief Information Officer praises the work of their technical staff. Does that include the assistant director for communications infrastructure who was quoted as saying, "I don't believe it's a Cisco problem in any way, shape, or form?""

12 of 195 comments (clear)

  1. I'll feel bad... by CCFreak2K · · Score: 5, Funny

    ...for the poor guy who said it wasn't a Cisco problem when he starts getting those Apple fanboy death threats.

    --
    "Beware of he who would deny you access to information, for in his heart he dreams himself your master."
  2. Not the iPhone but the iPhone by tepples · · Score: 2, Funny

    So it wasn't Apple's iPhone but Cisco's Linksys iPhone that was causing problems, am I right?

  3. Re:The Information Age by janrinok · · Score: 2, Funny

    However, no one actually makes sure it is correct.

    Isn't that the entire basis for wikipedia?

    --
    Have a look at soylentnews.org for a different view
  4. Everyone is a winner by BillGatesLoveChild · · Score: 5, Funny

    Cool. Cisco screws up, iPhone gets blamed, but nobody minds, because iPhones are so cool.

    Boss: "Did you get those reports done?"
    Underling: "Sorry Boss, I Couldn't. iPhone Congestion."
    Boss: "iPhone? ... (smiles) iPhones are cool aren't they!"
    Underling: "They sure are boss!"

    Boss wanders off feeling good.
    Underling returns to screwing around with his iPhone.

  5. Re:Most Don't understanding networking by TheEmptySet · · Score: 2, Funny
    "weird entworking problems"


    Damn those Ents and their slow decision making. First they nearly refused to act to stop the downfall of middle Earth and now, even worse, they are causing problems with Steve's divine creation. Personally I think we should ban them from having I phones if they are going to do this.

  6. Re:you're by uglyduckling · · Score: 4, Funny

    Shouldn't that be "fuck's sake" or "fucks' sake" - certainly not "fucks sake"..?

  7. Re:Cisco gear just isn't that good. by jkbull · · Score: 5, Funny

    ...(NEVER make one of these crash to ROMMON on boot. The fix is to RMA the NPE)...
    I understand the ROMMON, RMA, and NPE acronyms, but what's NEVER stand for?
  8. Re:So what was it by sammy+baby · · Score: 5, Funny
    I prefer Charles Wang's assessment of the folks at Gartner.

    "I want to choose my words carefully here, so I'm not misunderstood," he said. "They're a bunch of fucking idiots."


    Sorry I can't provide an authoritative cite... but even if it's apocryphal, it's so perfect that I can't care.

  9. Poor Sake by Oyume · · Score: 4, Funny

    Why is everyone picking on Sake? I mean, sure it's served slightly warm and in tiny cups, but it's not all that bad to drink, is it?

  10. Re:Meh. by gelfling · · Score: 2, Funny

    and electricity too and the damn horseless buggy. you kids get off my lawn

  11. Re:Jumping to conclusions by PM4RK5 · · Score: 2, Funny

    There's a reason they have a world-renowned business school. I'm pretty sure Jumping To Conclusions is a senior-level course.

    *ducks*

  12. Re:idiots by eli+pabst · · Score: 4, Funny

    He continued working on getting to the root of the problem and solved it yesterday.
    See, that's what he gets for not reading Slashdot. If he would've just sat there eagerly refreshing his browser, he would've seen several people post the solution to their problem last week and could've taken the weekend off. Hope this is a lesson.