The commissioning laptop gets a ping reply from the FR5, then its documented identity request times out. A borrowed laptop worked once, with no useful setup notes. What would you capture before we blame the controller or change its settings?
Capture the actual destination, adapter and selected route for both laptops, with the request version and complete read result; the old successful attempt needs reproducing under known conditions before it becomes a reliable comparison.
The borrowed machine is available again. Both used the same bench connection, but one has a USB network adapter. We haven't recorded the route or actual destination used by the application.
Yes, Anna; I would have IT compare the service connection and local policy once those destinations and routes are known, with the SDK and configuration differences retained for software to review.
IT is collecting that comparison. I found two settings files on ours, so I've asked software which one the running process actually loads. No controller changes made.