Cedar Falls public works cannot tell whether Blast dies on the laptop, inside the Windows 10 desktop, or at the city firewall. What should the operator do before blaming the firewall?
Select an answer to reveal the explanation.
Short Explanation
A Blast path has two clocks: the laptop client and the desktop agent. Line those timestamps up before accusing the city firewall of eating the session, or you will argue about two different minutes.
Full Explanation
When it is unclear whether a Blast drop is client-side, agent-side, or mid-path, gather Horizon Client and Horizon Agent logs and compare timestamps so events can be correlated. That associate step comes before changing civic firewall policy. Intelligent Hub logs do not time Blast on a Horizon session. App Volumes Manager attach times and a citywide firewall disable are not gather-logs actions for this path.