Unable to modify tags in one remote tag provider, Others working fine

Hello,

We have a hub and spoke architecture, one frontend gateway paired with several backend gateways which handle all the tags and coms to various plant areas.

I have recently configured a new backend gateway which is replacing an existing gateway.
With the new gateway I am unable to modify/add any tags to the tag provider from the central frontend. All other backend gateways are functioning normally.

When connected directly to the backend gateway (with the same AD credentials) it functions normally.

I’ve compared the existing gateway and the new gateway and the configurations are identical.

Any pointer as to what might be causing this?

Cheers

S

It might be security settings on your frontend gateway, specifically the Security Zones. Security zone identifiers can filter on IP addresses, host names, gateway names, and some other things. Your old backend gateway might have qualified for a required zone based on its host name or IP address, but your new one might not. You can also use the Security.SecurityZones and the Security.SecurityZones.Zone loggers on the central gateway to troubleshoot the security zones.

1 Like