MiaChen1166 · 13 Nov 2025, 15:06 UTC
Borrow that laptop for the same documented read and record its returned controller identity, effective destination and network path alongside yours.
22 pointsIt is available for a paired check. IT will capture both configurations before changing anything.
8 pointsInclude the exact error and targeted service with the SDK and interpreter versions; ping success alone will not identify where the diagnostic request failed.
22 pointsHas the paired read happened, Mia? A remembered success is hard for support to compare.
-8 pointsSecond laptop returned the expected identity. Mine timed out. Same effective destination, different selected routes.
6 pointsHave IT investigate the route and permitted service path, while retaining the software-version comparison; the route difference is not yet a demonstrated cause.
2 pointsWill the handover include the ordinary shortcut used for that check, not just the test session?
23 pointsYes, Harish. IT corrected the selected route; the documented read now succeeds from our ordinary shortcut.
9 pointsRetain 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.
22 pointsThis discussion is closed to new replies after six months without activity. Last activity: .