search cancel

Windows Agent Message sequence at Startup : "U02000146 Allowed address ..."

book

Article ID: 258274

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Hi Team,

Correctly configured and working Windows agents with TLS log the following lines, informing about non secured connections:

20230112/162325.665 - U02000146 Allowed address '127.0.0.1(WIN10AEA001)' for non-secured connections has been added.
20230112/162325.665 - U02000146 Allowed address '::1(WIN10AEA001)' for non-secured connections has been added.
20230112/162325.665 - U02000146 Allowed address '10.99.99.157(WIN10AEA001)' for non-secured connections has been added.
20230112/162325.665 - U02000146 Allowed address 'fe80::1408:26e4:e957:261d(WIN10AEA001)' for non-secured connections has been added.

These message sequence mention

  • the IPv4 loopback address,
  • the IPv6 loopback addresse,
  • the IPV4 address of the Host and
  • the IPv6 address the hots.

Even though these messages seems to be contradictory to the fact that Windows agents build a TLS connection to the AE system, these messages informs that the Agents accepts uncrypted connection TCP connection from his own IP addresses. 

 

Environment

Windows Agent  21.0

Cause

Incoming messages sourced by the JOB Messenger uses either one of these IP addresses to communicate with the Agent process.

Resolution

This is by design