Our FR10 answers the visitor's laptop and ignores ours

TheoBell0671 · 4 Feb 2026, 02:21 UTC

Closed
TH
TheoBell0671
I thought the intermittent ping meant our FR10 connection was nearly there. The documented availability read still times out. A visitor's laptop worked, but we never wrote down its route or loaded SDK. What should I ask IT to compare before the controller gets blamed again?

2 replies

SO
SofiaBell0630
Replying to TheoBell0671

Ask for the actual destination, selected network interface and route on both machines, alongside the interpreter, loaded SDK and exact read-only call. Also confirm what worked on the visitor's machine; a successful ping is not the same check you are trying to reproduce.

2 points
TH
TheoBell0671
Replying to SofiaBell0630

Visitor had completed the actual read. IT found our saved route selected an old network adapter, while the script and supported SDK matched. They corrected the laptop configuration. Normal shift launch and reopen now return the intended controller identity and availability. Thanks, Sofia; controller settings stayed untouched.

19 points

Discussion closed

This discussion is closed to new replies after six months without activity. Last activity: .