our FR5 status check works on the visiting laptop only

The script settings match. I haven't compared the route or which network adapter each laptop uses. IT can help with that.

Can IT capture the effective route to that address on each laptop while the test runs? A matching destination in the script does not show which interface carries the request, particularly if another connection is active.

Asked them. Visiting laptop has one active adapter, ours has wired and a managed wireless connection. No changes made to the controller.

Could the wireless connection be taking that address somewhere else? I'm asking, not volunteering a networking fix.

That is what the route comparison can establish. I would also record the read-only method, SDK version and error details so any software difference remains visible after the network finding.

IT found overlapping network ranges and a route through the wireless interface on our laptop. They're arranging an approved correction. SDK versions also differ, so that comparison isn't finished.

Did the read-only check work after the route correction, Alex, or is that still waiting to be applied?

Still waiting. The other laptop's settings and package details are saved now, so at least the working example won't disappear with its owner.

Correction applied by IT. Our read-only request now returns, but its response format differs from the visiting laptop. Maintainer is checking the wrapper against the documented SDK version.

So the connection improved and the software comparison still matters. Glad you kept both bits in the notes.