HanaBennett0709 · 8 Jan 2025, 09:21 UTC
Check which adapter carries the connection while docked. A ping reply tells you something answered; it doesn't identify the route your application used or prove the expected service is available.
23 pointsDock Ethernet and bench adapter both have addresses on the same subnet. Hadn't noticed that.
8 pointsThat is worth investigating. Compare the selected route in both setups and the address the script actually targets. Don't start changing the robot address to compensate for a laptop routing problem.
5 pointsWhat did the route comparison show? Also check whether the application binds to a particular local adapter (some wrappers do). Two addresses in one subnet are a clue, not a diagnosis.
-7 pointsAgreed. I jumped from a plausible cause to a fix too quickly. The route output and application target are the useful evidence here.
15 pointsIT found our wrapper bound to the dock adapter. Corrected that setting; docked and undocked status reads now work. Robot untouched.
16 pointsThis discussion is closed to new replies after six months without activity. Last activity: .