@TobyBrown0927 The recorded endpoint agrees with our script. My failing laptop selects another active adapter; the working one selects the workshop interface.

@DineshAllen0299 Give that route difference to your network owner for a targeted correction. Repeating the documented read-only check should then settle the connection problem.

Too strong. Correct routing doesn't prove the controller service is available. You might just get a different failure

@CalebBennett0754 Fair. i should've said it tests the routing lead. Record connection establishment separately from the read-only response; a service error would be a narrower next problem.

Would a successful ping help at all, then? I've got a folder of ping screenshots feeling increasingly decorative.

@DineshAllen0299 Limited reachability evidence. Ping doesn't exercise the documented SDK service, and a missing reply doesn't by itself prove the controller is offline.

On my laptop, office and workshop connections picked different routes to the same endpoint. The script hadn't changed; the active adapters had.

I'll retain the relevant adapter state alongside our selected-route information, making sure it describes the same laptop session in which the check fails.

Would a check with only the workshop connection establish the required fix, or does the normal multiple-connection setup still need review?

@AdaBaker0477 Use the network owner's documented diagnostic setup. A check with one connection doesn't establish the right configuration for normal use with both.

The evidence so far identifies different laptop routing, while the script agrees with the installation record. It doesn't establish that the controller address should change

Agreed. I've sent the route comparison to our network owner. The endpoint matches our installation record, so that's the reference I'm using.

@TobyBrown0927 What does a service error tell you that a timeout doesn't? At least something answered?

@AdaBaker0477 A documented service response can distinguish successful connection establishment from a later application failure. Its meaning still comes from the matching documentation, and an error isn't a successful read-only result.

@TobyBrown0927 My setup allowed ping but filtered the required service. The network logs explained that difference; the ping screenshots never could.

I'll keep filtering as a question if our route review doesn't settle it. Your example is useful, but I don't have that evidence for our cell.

Give support the documented service reference and the failure stage. Asking for everything to be opened wouldn't explain which connection you actually need

The initial troubleshooting question has a concrete answer: our laptops select different routes to the recorded endpoint. Resolution still depends on the network owner's correction and a successful read-only check under normal conditions.

That keeps the route finding and the final connection result in proportion. The repeat check is a clear condition for closing the fault.