Possible Cause: The IPGROPER module is not running.
Action: Check if IPGROPER is running in the NetExplorer IP host discovery. If IPGROPER module is not running, set the module to run. For information, see "Choosing Which Discovery Modules to Load" in "Understanding Network Discovery and Atlas Management" in the Novell ZENworks 6.5 Server Management Administration Guide.
Possible Cause: The SNMP community string of the server is not configured for discovery.
Action: To validate your SNMP configuration:
In ConsoleOne, launch the MIB Browser.
Specify the IP address of the server.
Specify the SNMP READ/GET community string.
Select the MIB-II system group (iso.org.dod.internet.mgmt.mib-2.system).
Click Tree Walk.
The results are displayed if you have configured correctly.
If the results are not displayed, you need to configure to discover IP routers. For more information, see "Starting Discovery" in "Understanding Network Discovery and Atlas Management" in the Novell ZENworks 6.5 Server Management Administration Guide.
Possible Cause: The scope set for discovery does not contain the address of the server.
Action: You need specify the address of the server in the scope. For more information, see "Changing the Discovery Scope" in "Understanding Network Discovery and Atlas Management" in the Novell ZENworks 6.5 Server Management Administration Guide.
Possible Cause: There is a problem with the address information of the server returned by SNMP.
Action: To validate your SNMP configuration:
In ConsoleOne, launch the MIB Browser.
Specify the IP address of the server.
Specify the SNMP READ/GET community string.
Select the MIB-II ipAddrTable in the IP group (iso.org.dod.internet.mgmt.mib-2.ip.ipAddrTable.ipAddrentry.ipAdEntAddr).
Click Tree Walk.
Check if the IP address appears in the list. Specify the correct IP address of the server. You need to wait until the next cycle of discovery for this address to be discovered.
Possible Cause: The network in which the server is present is not discovered because the router connecting the network to the site server is not discovered.
Action: If the machines that are in the same network as the server are not discovered, then check if the router which is connected to the network is discovered. For more information, see My router is discovered as an IP workstation.
If the network is very large, NetExplorer takesa longer to discover the information about the server.
Possible Cause: Discovery has not run for a sufficient time.
Action: If the SNMP information is correct, you can use file-based discovery to immediately obtain information about the machine discovered, without waiting for discovery to reach the network in the normal cycles. For more information, see "File-Based Discovery" in "Understanding Network Discovery and Atlas Management" in the Novell ZENworks 6.5 Server Management Administration Guide.