Discussion Locked

SNMP Auth Failure on Netopia Router

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

OK, second try: This is a pretty specific question: Netopia R9100 router, latest firmware (4.8.3); WinNT 4.0/SP4 PDC, DHCP, WINS; Win98SE client, standard software -- MSO2K, Palm Pilot, etc.

Here's the story. About two weeks ago, one machine started to give me an error that reads: "SNMP Authentication Failure (IP address 192.168.0.13)" when the user boots and logs on in the morning. Netopia Tech Support suggests it?s indicative of a failing network card. Funny thing is, three other machinesgenerated the same error, but only on one day. One machine generated five error messages in less than 5 minutes. Nothing from these machines since then. Correction: A fourth machine generated the error today when I rebooted the router -- not the computer.

What on earth could cause these errors, and how can I troubleshoot? I'm a bit rusty on NetMon, but that's where I'm inclined to start. TIA.

6 replies

by mckaytech

The usual cause of SNMP authentication failures is that the community string ("public" by default) is not being presented properly, either because of packet corruption or because it has been changed to some other value.

I guess my first question would be "What is at 192.168.0.13?".

My first observation would be that the common piece seems to be the router. It is quite common for equipment vendors to blame every piece of equipment but their own. However, the error today was associated with a reboot of the router rather than anything on the workstation end and when four machines generate the same error, it's very unlikely that the root problem is those machines. My guess is that the Netopia interface is flaking out (or the cable or the switch/hub port to which it is connected).

I agree with your plan to start with NetMon but I would also consider just doing the basic "swap" troubleshooting where you change out the patch cable, then the switch port, etc. and see if you can isolate the problem further. The best case would be if you could shame the vendor into swapping out the router to see if that solves the problem.
I'm guessing it would...

paul

by jonathanv_00

Well, it just occurred to me that the way this system works, you may not be able to respond with a comment that's not answer, or not be able to do a second answer. So, here are the points, and thanks for your help. Still haven't tracked down the issue, but you helped me think of a couple of things to try. Take care.

JonathanV

by jonathanv_00

Thanks. I was out of the office today, so I will do some switching of cables, etc. soon. (192.168.0.13 is the user's workstation that has generated this error the most.) If that doesn't work, I'll reset the thing and reload the latest firmware. After that, I call them. . . I'm going to leave this question open for more discussion, but I like your answer. Thanks.

by jonathanv_00

Still hoping for another comment or two; not as much interaction here as on Experts Exchange, it seems. I switched the patch cables, the cabling company tested the line, and I switched a port on the hub. I will try a different port the router latertoday when I get my hands on a crossover cable. I'll let you know what goes on.

by jonathanv_00

Paul -- since I'm not getting other responses, I hope you check this or have it set to get an email when there's a response. Haven't had a chance to use different ports on the router yet, but if that doesn't turn up anything, any ideas what I wouldlook for in Network Monitor? Failing that, I'll re-do the firmware, and send some points your way. Thanks.

Jonathan

This discussion is closed to new replies.