Laptops at a hospital campus follow a PAC file that sends application traffic to a proxy, and a capture shows that proxy resetting the sessions. What should be corrected?
Select an answer to reveal the explanation.
Short Explanation
A PAC file is a traffic cop on the laptop, and this one is waving cars into a booth that keeps shutting the gate. You correct the endpoint proxy selection, because the capture shows that proxy resetting the session. A WAN swap or a data-center probe move does not change where the laptop was told to send the flow.
Full Explanation
The laptops apply a PAC file that selects a proxy, and the capture shows that proxy resetting the application sessions. The steering decision lives on the endpoint, so the correction is the proxy selection the PAC file is applying, not a circuit the reset is not coming from. Replacing the WAN circuit between the campus and the application provider would matter if the path beyond the proxy were dropping traffic that the proxy had forwarded cleanly, which is not what the capture shows. A BGP advertisement for the proxy's prefix watches how that prefix is routed, and a reset from the proxy the laptop was told to use is not a missing advertisement. Moving an Enterprise Agent inside the data center changes where a probe sits and leaves the PAC file on the laptops pointing at the same resetting proxy. Exam caveat: a proxy reset can sit on top of a healthy WAN, so path work starts only after the endpoint is no longer being steered into the reset. Operational check: on a failing laptop, identify which proxy the PAC file selects and confirm the session reset is coming from that proxy rather than from a later hop.