A hardware tool that verifies whether a cable's wires are correctly connected and continuous.
A cable tester sends a signal through each wire in a copper cable and reports whether every pin-to-pin connection is present, in the correct order, and free of opens or shorts. It verifies continuity and wire map, confirming a cable is terminated to the right standard (T568A or T568B). The key exam distinction is scope: a cable tester confirms whether a fault exists and which pins are affected, while a time-domain reflectometer (TDR) measures the distance to the fault. On the N10-009, it is the correct first step when a newly punched-down patch cable fails to link up.
A two-piece tool that sends a tone on a wire so a probe can trace and locate that cable.
A toner probe is a two-piece kit: a tone generator and an inductive amplifier (the probe). The generator clips onto one end of a cable and injects an audible signal onto the wire. The technician then sweeps the probe along a bundle or wall until its tone grows loudest, pinpointing that exact cable without cutting anything. On the N10-009 exam, distinguish it from a cable tester, which verifies continuity, wiring faults, and pair mapping. A toner probe only locates which physical cable is which; the two tools are complementary, not interchangeable.
Software that captures and inspects packets to diagnose traffic and protocol problems.
A protocol analyzer (packet sniffer) captures raw frames off the wire and decodes every layer of the stack — Ethernet headers, IP addresses, TCP flags, application payloads — making it the strongest tool for diagnosing intermittent faults, misconfigured protocols, and unexpected traffic. Wireshark is the canonical open-source example in Network+ objectives. The key exam distinction is from a port scanner: a scanner probes which services are listening, while an analyzer passively captures live traffic. Because a switch forwards frames only to their destination port, capturing beyond your own host needs a mirror or SPAN port; otherwise you see only broadcast, multicast, and your own MAC’s frames.
The address 127.0.0.1 (or ::1) used to test a host's own TCP/IP stack.
The loopback address (127.0.0.1 for IPv4, ::1 for IPv6) is a reserved address that routes traffic internally within the host’s network stack, bypassing any physical network interface entirely. When a ping to 127.0.0.1 succeeds, it confirms that TCP/IP is installed and functioning correctly on the local machine — no cable, switch, or router is involved. A key exam distinction: a successful loopback ping rules out a software stack failure but says nothing about the NIC, cabling, or upstream connectivity. Confusing a loopback test with a test of the physical interface is a common mistake — pinging the host’s own assigned IP address (not 127.0.0.1) is the next step that actually exercises the NIC.
Automatic Private IP Addressing — a 169.254.x.x address a host assigns itself when no DHCP server responds.
Automatic Private IP Addressing (APIPA) assigns a host an address in the 169.254.0.0/16 range when DHCP discovery times out without a server response. The address is link-local only: no default gateway is configured, so traffic cannot be routed beyond the local subnet and internet access is impossible. On the exam, distinguish APIPA from an expired lease that may still hold a routable address temporarily — a 169.254 address is an unambiguous sign that DHCP never succeeded. Spotting it with ipconfig points to scope exhaustion, a downed DHCP server, or a misconfigured relay agent.