Custom PC Lab Success, Site Failure: Client Anger Over Unplugged Network Cable
This article from The Register's 'On Call' column recounts a tech support anecdote involving a technician named Gerald. Early in his career, Gerald configured a Windows 98 PC intended for use as a data collector. After passing laboratory tests, the system was deployed to a client site by another team member but failed to function correctly. Gerald's supervisor, believing the system was defective, harshly criticized Gerald and ordered him to travel 100 kilometers to the client's location for immediate repairs. Upon arrival, Gerald faced an furious client who claimed the malfunction was causing financial losses. Gerald diagnosed that while the PC booted and recognized the network card, it could not connect to external networks. After initial troubleshooting, he began disconnecting peripherals to transport the unit back for further testing. During this process, he discovered the network cable had never been plugged into the PC; it was neatly coiled and taped to a nearby support column. The incident highlights a common IT support frustration where user error or simple oversight leads to significant conflict, embarrassment for both the angry client and the technician's management, despite the hardware functioning perfectly.
Wire timeline
Custom PC Lab Success, Site Failure: Client Anger Over Unplugged Network Cable
This article from The Register's 'On Call' column recounts a tech support anecdote involving a technician named Gerald. Early in his career, Gerald configured a Windows 98 PC intended for use as a data collector. After passing laboratory tests, the system was deployed to a client site by another team member but failed to function correctly. Gerald's supervisor, believing the system was defective, harshly criticized Gerald and ordered him to travel 100 kilometers to the client's location for immediate repairs. Upon arrival, Gerald faced an furious client who claimed the malfunction was causing financial losses. Gerald diagnosed that while the PC booted and recognized the network card, it could not connect to external networks. After initial troubleshooting, he began disconnecting peripherals to transport the unit back for further testing. During this process, he discovered the network cable had never been plugged into the PC; it was neatly coiled and taped to a nearby support column. The incident highlights a common IT support frustration where user error or simple oversight leads to significant conflict, embarrassment for both the angry client and the technician's management, despite the hardware functioning perfectly.
www.theregister.com - Articles