> At this juncture we don't know if the problem is rooted
> in NT or in Netview.
You should always assume that NetView is perfect and seek
to afix blame elsewhere (NT, the position of the moon,
sunspots, etc.) :-)
Seriously though, isSNMPSupported is set to TRUE by netmon
during configuration check. There are 2 reasons why netmon
may set this to false for a node that has SNMP configured.
1. You don't have the proper community name configured
2. The remote machine did not respond within the time
window.
I would use the MIB browser to verify that you are using
the correct community name. If that works, you should
adjust the SNMP timeout and do a demand-poll. If that
works - the rest of the machines should get updated
properly during the next configuration check (assuming
you updated the SNMP timeout for them as well).
Jeffrey
|