I have the timeout and configured target. The supposedly working laptop's active adapter wasn't recorded.

Can you observe both ordinary launch routes in the same approved comparison, rather than compare today's failure with a remembered success?

Also distinguish a local call rejection from a request actually waiting for a reply. I wouldn't guess service or network trouble solely from a message somebody summarised as timeout.

The full error shows a reply wait. I've asked for both laptops together and kept the ping observation separate.

Give the comparison a named owner and keep the suspected cause out of the ticket title. Otherwise one plausible guess can become the explanation everyone repeats before the routes are even captured.

Compare actual controller identity and destination as well as address text. An address that answers isn't necessarily the intended endpoint for the documented service.

Has the comparison found a difference yet, or are you still arranging access to the other laptop?

Both captured now. Workshop laptop selects another adapter's route. Network owner is reviewing the intended configuration; no service result after correction yet.

That is a concrete route difference to address, not a reason to disable protection or try arbitrary ports. Use the documented service and approved network change, then repeat the read-only comparison.

Retain both configurations with the outcome. A corrected route is only useful to the next maintainer if the ordinary launch and network setup reproduce it after another restart.

Keep the final status pending until that read completes and its response is interpreted. Finding the route discrepancy has narrowed this investigation, not yet closed every timeout question.