A scanner never gets an address. A radioactive trace filtered to that scanner shows a DHCP nak from the server. A building syslog from the same minute does not mention the scanner. Where was the failure caught?
Select an answer to reveal the explanation.
Short Explanation
The trace you filtered to the scanner already shows the server saying no. That is where the failure was caught. A building log that never mentions the scanner did not catch it, and a beacon does not carry DHCP.
Full Explanation
A radioactive trace filtered to one client follows that client's join, including DHCP. This trace shows a nak from the server, which is the failure, and the building syslog from the same minute never mentions the scanner. The syslog did not store the nak and hide it. It does not have this event. A beacon does not carry DHCP. A guest portal log is a login record, not a DHCP nak. A radioactive trace filtered to the scanner shows a DHCP nak. That trace is the view that caught the failure. A building syslog does not. Check one live client after the change and leave the rest of the floor alone until that client matches the result you expected. Confirm the symptom on the next attempt before changing anything else. Exam caveat: a nak means the server answered and refused. No answer at all would be a different trace, with the discover and no offer. Read which of those the trace actually has. Operational check: keep the filter on the scanner, fix the scope or the reservation that produced the nak, and confirm the next trace shows an offer and an ack.