Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

SNMP problems on Windows 2000 and 2003 servers

I have found a trend recently where SNMP on several Windows 2000 and 2003 (mostly 2003) servers stops responding to my Solarwinds apps. I can find nothing is the server event logs to indicate any errors. A lot of time this will happen right after some sort of outage at on of our branches. Once the branch comes back up their file server is showing up as unknown status. I have to log into the server and either restart the SNMP service or make a change to its config (comm name or add authorized IP etc). This seems to primarily happen at my branches which are connected to corporate via VPN tunnels. Any ideas why this would happen?

Find more posts tagged with

Accepted answers

All comments

Dan.Wendeln

I wish I had a definitive answer for you, but all I know is that numerous customers have seen similiar behavior on Windows systems.

Cheers,

pguenther

We are still seeing this issue and with Orion growing daily I have way too many systems to go around restarting SNMP after every outage. Do others see this problem and how do you get around it?

pguenther

Does anyone else fight with the issue? I am faced with restarting SNMP on about 10 different servers again today after an brief outage.

brokenjeep

Your not alone..

I have 148 Windows boxes in my SW and every week without fail I need to go give one a kick. The only advice I can give you is to remove/reinstall patch the ones that are chronic.