The workshop laptop times out on a read-only FR10 availability query. Ping sometimes answers. I noticed it changes when the dock is connected, but the other laptop's network notes are incomplete. I want to compare what each machine actually uses before changing the script.
Have your network maintainer inspect the chosen route and source address for the controller endpoint in both cases. Don't start swapping SDK calls to compensate for traffic leaving through the wrong interface.
Our replacement laptop inherited a network profile from a different bench. Everybody blamed the application because that was the thing displaying the error. Please get the corrected arrangement into the laptop handover if that's what yours turns out to be.
Dock profile had an old route for an overlapping bench network. Maintainer removed that obsolete profile and restored the approved controller route. The same read-only query now returns the expected controller identity docked and undocked.
Clara, the laptop handover now names the approved adapter setup and the obsolete profile. Thank you. We repeated the check after reconnecting the dock and restarting the laptop; no script change needed.