Troubleshooting Without Weakening Security

On a busy Saturday the card till stops connecting. A queue is building. The quickest-looking fix is to switch off the firewall "just to see". Troubleshooting is a core IT skill, and doing it in a calm, recorded way also protects the shop, because some faults turn out to be security problems.

The rule

Change one thing, test, write it down, and never switch off protection.

A method that works on any device and any operating system:

1. Define the problem in one sentence: what should happen, what happens instead, since when.
2. Gather clues: error messages, what changed recently, whether other devices are affected.
3. Start from the bottom: power, cables, Wi-Fi connection, then the network, then the application.
4. Change one thing at a time and test after each change, so you know what fixed it.
5. Write it down: symptom, cause, fix. Next time it takes two minutes.

Changing several things at once hides the real cause. Disabling a firewall or antivirus to "fix" something may hide the problem while opening a bigger one, and people forget to turn it back on.

Watch for clues that the fault is not ordinary: settings nobody remembers changing, a new unknown program, an account locked from too many password attempts, or a machine suddenly very slow and busy. Those are reasons to stop and report, not to keep fiddling.

The shortcut

Work bottom-up and one at a time: physical, then connection, then network, then software. After every step, ask "Did anything change?" and note it.

Notice that the laptops working was a strong clue: it ruled out the internet connection in one step.

Drills

Answer fast — trust the rule.

Remember

• Change one thing, test, write it down, and never switch off protection.
• Go bottom-up: physical, connection, network, software.
• Trap: disabling the firewall or antivirus to "fix" things, and ignoring signs of an intruder.