Borrowed laptop completed the FR5 read-only check. Workshop laptop times out, though ping sometimes replies. We wrote down almost nothing from the successful setup (excellent preparation for borrowing it again).
What should IT and our maintainer compare before anyone changes controller settings?
Start with what the successful laptop actually used: controller endpoint, selected network interface and route, documented service, and software environment. Get the same details from the failed run.
I have sat through a comparison where 'same connection' meant two laptops plugged into the same bench, while one was using another active interface. The labels on the cables did not answer that. Have IT establish the approved path; the maintainer can then compare the read from identified software rather than trying random network changes.
Was the successful check made from the user's ordinary shortcut? That is the setup I would want recorded, not only an interactive window the visiting technician prepared.
Interactive window on the borrowed laptop, Will. Visitor has agreed to send its working environment details. IT is capturing our selected route and confirming the endpoint.
Keep the failed run intact until those details are recorded. Changing three things to get a response can leave you with a working laptop and no useful explanation for the next failure.
Our maintainer, with IT owning the network section. Endpoint is now confirmed; our laptop was selecting a different interface from the one intended for the controller route.
Have IT correct that permitted route, then repeat the documented read from the identified environment. Do not call it finished just because the ping becomes steadier.
Yes, endpoint matches. IT has corrected the route. The documented read works in the maintainer's environment now; normal shortcut still needs checking against that setup.
That last check matters. The shortcut can select a different interpreter or library even on the same laptop, so keep its imported copy with the result.
Useful to find both differences. The route explains one part of the investigation; the launcher comparison still deserves its own entry instead of everything being called network trouble.
Supported environment confirmed and launcher corrected. Normal user read now returns the expected controller identity. Network and launcher differences are recorded separately. Thanks Hazel for the actual-interface question.
Does the rebuild note point to that verified configuration, including who reviews it after changes? The working shortcut should not be the only surviving copy of the answer.