Unsolved

This post is more than 5 years old

1 Rookie

 • 

66 Posts

7946

September 12th, 2004 14:00

Windows NT authentication error: community name incorrect.

I receive several of these errors each day from some of my DELL servers on the IT Assistant / Alerts screen. I have checked and rechecked all my SNMP settings on these remote servers, and they ARE correct. Any idea why these keep coming? I'd sure like to get rid of them.

Windows NT authentication error: community name incorrect.

Any help or suggestions will be greatly appreciated.

Message Edited by tgoetzman on 09-12-2004 10:44 AM

2 Intern

 • 

127 Posts

September 13th, 2004 12:00

Please be sure that the community name in the snmp service is read/write and is also listed on the traps tab of the service.  Then go to IT Assistant and check Options-> Set Discovery Range and be sure that the snmp get and set communities match the string on the remote server.  You will also need to check the strings on the Options-> Discovery Cycle ->Protocol Settings tab to be sure they match.  If all of the strings match, you can disable authentication traps on the remote server's snmp service by unchecking the Send Authentication Trap checkbox at the top of the Security tab window.

1 Rookie

 • 

66 Posts

September 13th, 2004 12:00

Thank you. If I disable authentication, it won't affect any of the alerts or traps, will it?

2 Intern

 • 

127 Posts

September 13th, 2004 12:00

Alerts and traps will not be affected, except the authentication alerts.  This is a check and balance to be sure that the snmp community names match between the remote server's snmp service and the management station (in this case - IT Assistant).

1 Rookie

 • 

31 Posts

October 6th, 2004 15:00

I had the same issue and I believe that those errors were from an alternate system that was monitoring our system. If you have secured your SNMP community names (something other than the default of public), and another monitoring system is using public (or another name) to monitor the system, you will get these errors.

I did end up shutting the notifications off at the client side, merely because I didn't care who else was trying to monitor my system.  They couldn't - so I didn't really worry.  Perhaps when I have more time, that's something I'll look at for security reasons, but with the limited bandwith I have, this was the easiest solution.

 

Good luck,

 - Jen Meklenburg

0 events found

No Events found!

Top