Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Log & Event Manager (LEM) > 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: 999 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