简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
MiaChen1166 · 2025年11月13日 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分It is available for a paired check. IT will capture both configurations before changing anything.
8分Include the exact error and targeted service with the SDK and interpreter versions; ping success alone will not identify where the diagnostic request failed.
22分Has the paired read happened, Mia? A remembered success is hard for support to compare.
-8分Second laptop returned the expected identity. Mine timed out. Same effective destination, different selected routes.
6分Have IT investigate the route and permitted service path, while retaining the software-version comparison; the route difference is not yet a demonstrated cause.
2分Will the handover include the ordinary shortcut used for that check, not just the test session?
23分Yes, Harish. IT corrected the selected route; the documented read now succeeds from our ordinary shortcut.
9分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.
22分此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .