No, look, really, BOTHER ME!

Junior IT pilot fish gets simple duties like taking care of network and node issues that occur at this manufacturing plant.

"One afternoon, I was informed that one node could not connect to the network-attached storage unit and retrieve files," says fish. "So I got to the NAS with my netbook, checked the Cat 5 cable and saw that it too was not getting a connection on the network."

Since all the other computers are running without problems, fish concludes the trouble is with the cable. He replaces the cable's connectors, and reattaches the cable to a different port on the switch.

Problem solved -- right?

Next morning, when fish arrives at work, he has a new trouble ticket: Another computer from the same segment has the same issue as the day before.

Fish offers the use of his own workstation to the stranded user so his shift can get to work. User replies, "I don't have time to walk to the front office and make the printouts. Fix the @#$%! thing!"

After a little more troubleshooting, fish has changed his diagnosis: The switch is going bad and needs replacing. While fish is doing that, the user -- much calmer now -- returns and tells him, "I'd been having a problem with connecting to the NAS for the past three days."

Says fish, "I asked, why didn't you call me then? He replied, 'You were already working on that other computer and its network problem, I didn't want to bother you with mine.'"

Sharky's always ready to hear your true tale of IT life. Send it to me at sharky@computerworld.com. You'll score a sharp Shark shirt if I use it. Add your comments below, and read some great old tales in the Sharkives.

Now you can post your own stories of IT ridiculousness at Shark Bait. Join today and vent your IT frustrations to people who've been there, done that.

Copyright © 2010 IDG Communications, Inc.

  
Shop Tech Products at Amazon