Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Log & Event Manager (LEM) > LEM - Knowledgebase Articles > Authentication Traffic but No Agent rule explained

Authentication Traffic but No Agent rule explained

Table of contents
Created by Craig O’ Neill, last modified by MindTouch on Jun 23, 2016

Views: 1,156 Votes: 1 Revisions: 3

Updated June 13, 2016

Overview

This article explain the Authentication Traffic but No Agent rule.

Environment

  • All LEMversions
  • Windows Agents

Detail

This rule is triggered by Events sent from DHCP servers on Domain Controllers as Workstations or servers being authenticated, but there is no LEM agent installed on the server/workstation.

Basically it is LEM's way of letting you know that there is a problem with agent communication on a machine.
The rule should only be enabled after all your servers and workstations have agents installed.

Unless you have LEM Agents on ALL of your Windows machines, you should disable the rule.

 

 

Last modified

Tags

Classifications

Public