Why does only the borrowed laptop read the controller identity?

AnnaBell0677 · 30 Jan 2025, 11:13 UTC

Closed
AN
AnnaBell0677
Our FR5 commissioning laptop reaches the controller intermittently by ping but times out on the documented identity read. The integrator's laptop worked on the same cable. He has left with the laptop and most of the useful information. I want a comparison someone can repeat before this becomes another controller settings experiment.

5 replies

HA
HassanArcher0356
Replying to AnnaBell0677

Compare interface addresses, selected route and the documented service connection; ping alone does not establish service availability.

10 points
AN
AnnaBell0677
Replying to HassanArcher0356

Our laptop has wired Ethernet and a VPN route for the same address range. The integrator has sent his interface settings. No overlapping route on his machine.

11 points
HA
HassanArcher0356
Replying to AnnaBell0677

Have IT verify which route the identity request uses and correct the overlap under their network policy; no controller change indicated yet.

19 points
AN
AnnaBell0677
Replying to HassanArcher0356

IT confirmed the request went to the VPN interface and corrected the laptop configuration. Identity retrieval now works repeatedly. They documented a commissioning profile for us. Considerably cheaper than the afternoon already spent blaming the script.

17 points
HA
HassanArcher0356
Replying to AnnaBell0677

Have the profile checked after managed network updates too; today's working route is evidence, not a lifetime arrangement.

7 points

Discussion closed

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