Inaccessable

[Ayman Altounji]

I have Insight loaded on 2 different NT workstations from which I periodically monitor 8 Netware 4.x servers. On one NT box, 2 of the 8 servers show as "inaccessable" all others can be accessed. On the other NT box all servers can be accessed, what could be the cause of this?

Simon

[Ayman Altounji]

It sounds like your problem could be the SNMP community string on your 'problem' NT system, if the Servers are displayed as unmanageable (coloured black).
You could try right clicking on one and selecting 'Device Setup' - make sure the community setting is correct there then refresh the device status.

Failing that make sure all the necessary SNMP and compaq services are running on your NT system, if need be check these against your good NT system.

good luck.

[Ayman Altounji]

Good input ACWSmith...

[Ayman Altounji]

From experience it seems like software such as service packs seems to have cause this. To solve the problem is to reinstall agents. I've just joined a new company with the same problem, trouble is there are at least 50 inaccessable servers. It seems like this is problem Compaq should investigate further

[Ayman Altounji]

I have seen many times that IPX devices will be inaccessable if the IPX frame type on the Windows work station is set to "Auto-Detect". I always specify the frame type and net number manually under IPX properties. Also, check the SNMP community strings. They are case sensitive.

[Ayman Altounji]

I experience the same problem on about 5 servers out of 52. They range from DL380's through to ML570's. I have not had this experience on a 2k box, it only seems to be winnt boxes that experience this.

To rectify the problem I have uninstalled and reinstalled SNMP, reconfigured the community strings, triple checked them. Deleted and recreated the server in the insight manager console and checked the community strings in there. All this was done in conjunction with multiple re-applications of the service packs on the NT box and multiple restarts of the SNMP service.

I still have not reached a resolution to this issue, I cannot find anything that stands out as being responsible for this issue, maybe this is an issue that Compaq may want to investigate further ? I will log a call about this and I will post any resolution I get to here for others.