Our laptop sometimes pings the FR5 address in the bench note, but the read-only diagnostic shortcut times out. Second laptop worked during a visit. Nobody wrote down its setup, naturally. I've found another address in the shortcut and want to establish which endpoint we're actually asking.
Ask the network owner to confirm the controller endpoint, then compare that with both the note and the running application's configuration. Two written addresses are already a useful discrepancy.
Network owner confirmed the controller address. Bench note matches it; shortcut loads a settings file with the other address. I had assumed the visible note was what the script used.
Before editing that file, check whether it's the settings file intended for this bench or an old training copy. You don't want to repair one shortcut while another still launches the wrong job configuration.
Please name the settings file in the handover. 'Use the diagnostic script' is apparently an invitation to collect every script with diagnostic in its name.
Not changed yet, Owen. Maintainer is comparing the launcher with the working laptop's retained files. Chloe's right: our shortcut came from a different bench folder.
David, we ended up giving our teaching shortcuts the cell name as well as the exercise name. Still not a technical control, but it stopped people choosing by whichever icon looked familiar.
Aaron: versions and check match. Maintainer restored this bench's launcher and settings. Query now reaches the confirmed endpoint but still reports a service timeout, so the wrong address was not the whole problem.
Can the working laptop be checked under the same connection conditions, rather than relying on its successful visit? That would narrow the remaining difference.
Both checked together. IT found the diagnostic service blocked by this laptop's assigned policy. They corrected the approved rule for that service; the documented query now returns the expected status on both machines.
Yes, fresh login and ordinary shortcut. Confirmed endpoint, launcher and approved policy are in the handover. Two separate mistakes fixed. Thanks for not letting the first address discovery become our entire diagnosis.