The first thing to find out when troubleshooting is what is the behaviour? In other words, when and in what way does the so-called problem occur? This is too-often overlooked, and can lead to "correcting" an optimal configuration. | Perhaps the problem hasn't even happened yet. An unlikely event, you could say. But since problems too often can be sources of innovation and improvement, don't dismiss this lightly. What is great about the problem, if there is anything great about it? | When you are satisfied that the solution can't be worse than the trouble, reboot. If that doesn't work, power cycle the malfunctioning equipment (meaning turn it off and on). If it still isn't working, turn off all equipment for a cool-down period. Then pray.
|
