Our training laptop pings the address written on the FR10 cabinet, but the read-only connection test times out. The tutor's laptop works. I found a second address in an old worksheet and now nobody can tell me which note is current. How do I establish what we're actually contacting?
Have the person responsible for the cell confirm its configured address, then compare that with the exact target each test uses. A handwritten address and a successful ping can agree while referring to the wrong device.
The tutor confirmed the controller address from the approved cell notes. Our script uses the other one from the worksheet. I changed the configuration to match the notes, but it still times out.
Check whether the running script loaded that changed configuration; it may be reading a different file than the one you edited. Log the effective target locally with the request result, so the next comparison is based on what ran.
That would explain different behaviour from apparently identical files. Compare launch path and active environment as well as the visible script, because those can select configuration and library copies behind the scenes.
Found a duplicate configuration beside the shortcut's working folder. The effective target was still the old address. Now corrected, and the test returns an explicit connection error instead of hanging until our outer timeout.
Good, the target is now established. Compare the library versions and full error with the tutor's successful run; keep the controller configuration fixed while you investigate the remaining client difference.
It's an incompatibility report from our local wrapper. The tutor uses the wrapper revision approved with this training image; ours came from an older copied folder. IT is restoring the documented laptop environment.
Read-only check now succeeds on our laptop too. We tested from the normal shortcut and recorded the effective target and loaded versions. The old worksheet has been marked obsolete by the tutor.
Put those recorded values with the training image instructions. You had two separate client problems, and future troubleshooting will go faster if the old address and old wrapper aren't remembered as one mysterious network failure.