Printer not discovered

It’s the ’80s, and this marketing consultant pilot fish will get despatched out to see what’s occurring with a shopper who’s complaining that recordsdata are printing days and even weeks after they had been submitted. However not fully — solely a web page or two at a time.

Fish has loads of issues to verify earlier than giving critical consideration to the concept there’s a time portal hidden someplace.

It’s a NetWare community on co-ax. The server seems OK, and fish sees nothing queued.

Printer seems OK, too.

However when fish tries to disconnect the BNC connector, it falls off in his hand.

Subsequent, he opens the wall jack — and the co-ax falls out of the connector. Issues want a more in-depth look, and what fish sees is that, as a substitute of good, even crimps, there are markings that appear to be they had been made by — pliers?

So fish asks for a rundown on the wiring. It’s all new, he’s informed, executed by an electrician who was there to do another electrical wiring and was requested to place within the co-ax community.

Which he was glad to do, however he did not have co-ax instruments; he simply reduce and crimped together with his electrician’s pliers as he put in dozens of co-ax wall jacks and made some co-ax connector cables. The overwhelming majority of these connections simply disintegrate when touched.

Fish makes use of a time-domain reflectometer to bounce a sign down the cables and see if there are any discontinuities and whatnot. And he will get some actually unusual readings.

That results in the invention that the electrician had gone exterior the constructing with a few runs, then over the roof to completely different elements of the constructing — “simply to keep away from all that pesky cable pulling, you realize,” says fish. However the place the cable wasn’t lengthy sufficient, the electrician simply put in barrel connectors to splice to a brand new run of cable. Exterior. On the roof. With inside (i.e., not waterproof)
connectors.

Water had been leaking into these connectors, after all, then draining to the bottom level of the cable. And since some wall jacks had been leaking contained in the partitions, there was mildew, too.

So is that this frail community the time portal? It’s a giant a part of it. However fish missed one thing in his first evaluation of the scenario: The primary server isn’t printing; jobs are being despatched to a forgotten NetWare print server lengthy forgotten in a closet. It might get jobs, then attempt to push them out over this waterlogged, badly crimped community — and fail. However it will maintain every job and retry — repeatedly and once more …

Fish’s agency will get the job of re-terminating every part, changing soaked cables as needed (and never going over the roof). Another person needed to care for the mildew.

Queue up your true tales of IT life. Ship them to Sharky at sharky@computerworld.com. You may also subscribe to the Every day Shark E-newsletter.