Duke Wireless Problem Caused by Cisco, not iPhone
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?""
All of our 100mbit servers and the Cisco switches they connect to have to be nailed to 100/Full, because the Cisco hardware refuses to negotiate properly with HP Proliants and Sun hardware. Yet a $40 D-Link can manage just fine.
Not to mention how buggy IOS releases have become in recent years.
I wonder how many folks will start checking out Juniper.
I wish I had a nickel for every jerk who has instantly pointed the finger at Apple for any IT issue in which Macintoshes were involved.
Or described the NuBus "proprietary" and the AT bus and Micro Channel as "standard."
Or claimed that the ASCII standard defines CR+LF as the proper character combination for a line break.
Or asked me to "go to the 'START' button" on my Mac and, when I said I didn't have one because I was on a Mac, told me that Macs weren't supported even though their website says that they are.
"How to Do Nothing," kids activities, back in print!
I hate that phrase: "any way, shape, or form." What's wrong with "in any way?" Do issues have a shape or form?
Gamingmuseum.com: Give your 3D accelerator a rest.