I love these stories, we should have an entire sub forum dedicated to them...always brings a smile to my face.
<LOL> Thanks, I look forward to your story.
This one isn't necessarily funny but I thought it somewhat amusing. Back in the late eighties / early nineties I worked for a large company. It was back when large companies were transitioning from extended bridged networks to routed subnets and many on the company network team hadn't quite come to fully appreciate the difference between bridges and routers.
We had an amazing installed base of 50,000 PCs back then and, even more amazing, 20,000 of them were Apple Macintoshes. Corporate was hard at work networking the 30,000 PCs. It was before the Internet so they were installing Novell File and Print to give a networked PC some meaning and purpose. The network protocol was Novell IPX.
Corporate chose to ignore the 20,000 Macs because Steve Jobs often took pleasure in ridiculing the
Corporate IT world (if anyone is old enough to remember some of the old Apple commercials) and corporate
justified doing so because of the bad rep the original release of AppleTalk had garnered.
A few of the Mac guys were at the corner pub (kind of an ad hoc Apple users' group). It was 1989 and Apple had just released an update to AppleTalk (AppleTalk Phase 2) which deployed extended addressing and split horizon broadcast. In our minds it was a new flag to wave and three beers later we had put together a rough draft for implementing AppleTalk (thus Macintosh) city wide.
A couple things happened as we polished and circulated our draft;
1 - The polished draft looked so real management assumed someone had actually approved it!
2 - The Corporate PC / Novell Network team started teasing us, "What's with all the paperwork and network naming / numbering standards? Novell just works, it's just plug and play!" More on this in a moment.
Anyway in a few short months we had
thousands of Macintoshes networked and talking with File Servers, Printers, Mainframes, VAXes, Unix Systems, etc.
But the Novell guys were still teasing us. Their stuff was simply "plug and play". (Huh? "Plug and play" yet they had managed to implement only a
few hundred nodes over the past couple
years?) So at our next apple laden alcohol users
meeting we read up on Novell. Turns out Novell IPX is much like DECnet, TCP/IP and AppleTalk; there
ARE network numbers (and name space) to define and manage. In fact each Novell File server also served as an IPX
router.
So why was it working? Because for the most part they were stand alone LANs. So what would happen when they started interconnecting all the LANs and CANs? Failure. Disaster.
So it was with the best of intentions we started raising the issue up the flag pole but no one saluted. Finally I released a brief statement of sorts, in the style of Muhammad Ali, rhymes and all, predicting the corporate crash of IPX on such and such a date some three months out. Nothing. I sent out a couple updates using new verse and new rhymes. Still nothing. I then forgot all about it until ...
Until ... a couple corporate suits and security showed up at my
Dilbert cube. IPX had crashed (about two days after the day I had
"predicted") and they wanted to know what the
hell I had done! I was trying to explain but I wasn't getting through. Or maybe I did. They left so I guess they concluded I wasn't bright enough to bring down an entire campus wide network. They weren't wrong.
The next day a real network guru stopped by. We talked for a few minutes and he started laughing. He went to the broken campus and had everything fixed within a hour. Novell sat on a wall, Novell had a great fall and Apple put it all back together again : -)