FR5 diagnostic timeout without the working laptop's settings

It is available for a paired check. IT will capture both configurations before changing anything.

Include the exact error and targeted service with the SDK and interpreter versions; ping success alone will not identify where the diagnostic request failed.

Has the paired read happened, Mia? A remembered success is hard for support to compare.

Second laptop returned the expected identity. Mine timed out. Same effective destination, different selected routes.

Have IT investigate the route and permitted service path, while retaining the software-version comparison; the route difference is not yet a demonstrated cause.

Will the handover include the ordinary shortcut used for that check, not just the test session?

Yes, Harish. IT corrected the selected route; the documented read now succeeds from our ordinary shortcut.

Retain that before-and-after comparison and the verified endpoint in the handover, so a later timeout is investigated against a known working setup rather than this original incomplete account.