In fairness, the problem WAS found and fixed

Flashback to the days before Y2k, when this systems engineer pilot fish is sent to a customer site -- and he can't come back until he's solved the problem there.

"I was told to stay until I found out why some scans, several gigabytes in size, that were being sent through the 100BaseT network to their file server were getting truncated," says fish.

"Our company's $250,000 scanners, top-of-the-line servers and switches were not supposed to do this.

"There were a few suspicious restarts in the workstation event viewer, but previous remote troubleshooting pointed to networking. And older NT systems were regularly restarted as a matter of course.

"I was running file-transfer tests when I walked by and noticed Barney, the scanner operator, jump up cursing. He whacked the CRT, which had just gone dark, and punched the restart button on the workstation.

"Obviously, the scan in progress was incomplete on the file server. It was just the screen dimming after 15 minutes, not the computer itself hanging up. But it took awhile to convince Barney of that.

"However, he could have lost his job if we reported the real reason, so we 'found' and 'fixed' a 'network problem.'"

Join Sharky's network. Send me your true tale of IT life at You'll snag a snazzy Shark shirt if I use it. Add your comments below, and read some great old tales in the Sharkives.

Get your daily dose of out-takes from the IT Theater of the Absurd delivered directly to your Inbox. Subscribe now to the Daily Shark Newsletter.

Computerworld's IT Salary Survey 2017 results
Shop Tech Products at Amazon