Walk a network problem from cable to cloud, with AI as your tutor

You are teaching a help desk technician how to troubleshoot a network problem methodically. I will give you a scenario. Walk through the troubleshooting in five layers, in order, from cheapest-to-check to most expensive.

Use these five layers:
1. Physical (cable, port, light on switch, wifi signal).
2. Link (is the device on the network at all? does the OS show a connection?).
3. IP (does the device have an address? is it the right subnet? can it reach the gateway?).
4. DNS (can it resolve names? try by IP versus by hostname).
5. Application (is the service the user is trying to reach actually up? firewall blocking it?).

For each layer:
- Name one specific thing the technician should check, in plain language.
- Name the command or button-click they would use on Windows OR macOS (pick whichever is more common in a corporate environment).
- Name what result would tell them the problem is at this layer versus a deeper one.

After the layers, give a one-sentence guess at which layer this scenario most likely lives in, based on the symptoms.

Scenario:
[paste the scenario from step 1]

A device is showing a 169.254.x.x self-assigned IP address on its network adapter. Explain to a junior help desk technician:

1. What this address means in plain English (one sentence).
2. What the most likely cause is, on a wired corporate network.
3. What the most likely cause is, on a home wifi network.
4. Three things the technician can try, in the order they should try them.
5. When this is a problem the technician can fix, and when it should be escalated to the network admin.

Avoid jargon where possible. When you have to use a term (DHCP, ARP, gateway), explain it in five words or less the first time you use it.

You are writing a brief, internal close-out note for a help desk ticket. I will give you the facts. Write a tight three-paragraph note for the team.

Format:
- Paragraph 1: what the user reported, one sentence.
- Paragraph 2: what was actually wrong, one sentence. What fixed it, one sentence.
- Paragraph 3: anything to watch for if this happens again, one sentence. Or "no further action" if there is nothing.

Rules:
- Total under 90 words.
- No "we apologize" language. This is internal.
- Use the technical term once if it helps a future technician find this ticket via search (e.g., DHCP, APIPA, DNS).
- No emoji.

Facts:
- Reported: [paste the original scenario from step 1]
- Diagnosed: device had a 169.254.x.x self-assigned IP. Could not reach gateway or DNS.
- Resolved: released and renewed IP from the wired connection. Device pulled correct address from DHCP.
- Time: 18 minutes.