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

Timeout error when adding a node

I have managed to add some of my windows servers to solar winds but one server seems to be giving me a timeout error when i try to add it, i understand it is most likely something to do with my setup, too help me troubleshoot this does anyone know what exactly solar winds does to add a node i know that is uses wmi but would there be anything else(e.g. ports? protocols?) that it uses?

Thanks.

Find more posts tagged with

solarwinds

Accepted answers

tomasv

By default WMI uses dynamic port behavior. So may be the range of used ports (now 5503 and 5502) can anytime change.

There are specific rules on Microsoft's firewall to enable remote WMI - Connecting to WMI Remotely Starting with Windows Vista (Windows)

All comments

martinstenner

Depends what polling method you're using. If SNMP you'll need to make sure you're using the correct SNMP community strings (as configured on the server) when adding the node.

If WMI a domain account with sufficient privileges. Preferably a service account.

Make sure WMI and SNMP are allowed through the firewall on the server you're trying to add.

If you can't ping the server, it's probably a good idea to get ICMP working before you look elsewhere.

mharvey

If you are using WMI, then it's running WQL queries to see what the device supports where SNMP uses OIDs. What I'd first recommend is making sure, if you are using WMI, that connectivity is allowed between the systems. This link should be able to help with that:

http://knowledgebase.solarwinds.com/kb/getattachment.php?data=MTY3MnxBUE1XTUlUcm91Ymxlc2hvb3RpbmcucGRm

This is a link to the WMI troubleshooting guide from Solarwinds.

Regards,

Matthew Harvey

Loop1 Systems

tomasv

The set of factors which could break WMI polling is quite complex.

There is document which describes steps how troubleshoot WMI problems - http://www.solarwinds.com/documentation/apm/docs/APMWMITroubleshooting.pdf

wbrown

I've had a similar issue when adding network devices. In those cases the issue was due to the polling services on the assigned poller had failed.

The services on the poller appeared to be running but restarting the services, or rebooting the poller in some instances, was required in order to add the node with the specified poller.

If you have multiple pollers then try adding the node to a different poller.

jm89

When adding a node it seems solar winds sends a request on port 135 to the node you are trying to add, and then sends another request using some random port (in my case this random port was either 5503 or 5502). The request for port 135 went through successfully to the node i was trying to add, whilst the request for both 5503 and 5502 never made it to the node. Opening up these ports has now allowed me to add the node.

Thanks for all the helpful suggestions.

tomasv

By default WMI uses dynamic port behavior. So may be the range of used ports (now 5503 and 5502) can anytime change.

There are specific rules on Microsoft's firewall to enable remote WMI - Connecting to WMI Remotely Starting with Windows Vista (Windows)