It might not be your NetView that is causing this. It could be another
application using SNMP, which hasn't been configured with the correct
community name. This would cause your server to send a
authenticationFailure Trap to it's trap destination (your NetView).
Examples of such application could be other SNMP managers of print
managers (e.g. HP JetAdmin).
- Michael.
______________________________ Reply Separator _________________________________
Subject: Re: Incorrect Community Name
Author: Non-HP-Raymond.Stoner (Raymond.Stoner@SPCORP.COM) at HP-Belgium,mimegw3
Date: 02-06-99 14:17
We have the same problem at times with some of our NT servers (Compaqs) .
The servers are both in NetView SNMP config properly and SNMP appears to be
configured properly on the Server. Pretty strange. Performed some SNMP
tracing on the event but results did not show much. So what we have done is
un-checked the send authentication trap box in the SNMP config on some of
the offending NT servers.
-----Original Message-----
From: OGrant [mailto:OGrant@pec.com]
Sent: Tuesday, May 18, 1999 12:48 PM
To: NV-L@UCSBVM.UCSB.EDU
Subject: Re: Incorrect Community Name
Check configuration of SNMP services on the offending device(s) - a bad
community name is suggested below.
> -----Original Message-----
> From: Phat D Doan [SMTP:pddoan@REGENCE.COM]
> Sent: Tuesday, May 18, 1999 12:39 PM
> To: NV-L@UCSBVM.ucsb.edu
> Subject: Incorrect Community Name
>
> I kept getting the below events to my Netview v.5.1 (on AIX 4.2.1) from
> the
> WindowNT systems:
>
> Incorrect Community Name (authenticationFailure Trap)
> enterprise:ENTERPRISES (1.3.6.1.4.1.311.1.1.3.1.2) args(0):
>
>
> How do I correct the problem? Thanks for your help.
>
>
> Phat Doan
|