Some GUI elements like buttons, window borders, or text are not displayed or not displayed at the correct location.

Current Java versions has much faster GUI refreshing mechanisms than older ones. Generally, this is a good thing, but unfortunately some graphic card drivers have bugs that cause a highly optimized rendering system to fail properly refreshing the display. If you encounter such problems, please try to get and install an updated version of your graphic card drivers.

MIB files cannot be compiled although other SNMP tools accept them.

In almost all such cases, the MIB module that fails to compile has a serious syntax error, thus, an error that clearly violates a SMI rule. If you are not able to fix the MIB module with the built-in MIB editor, you may switch the MIB compiler into lenient mode and recompile the module.

Caution: Using lenient MIB compilation may cause problems later because incorrect or inconsistent data may have been read. If you encounter problems with MIB Explorer, please make sure that all your MIBs have passed normal compilation.

The chart view of a monitor does not update correctly when data collection is performed by expressions only.

Workaround: Add a (dummy) row that collects an arbitrary numerical value (e.g. sysUpTime) and uncheck the Display box in the configuration of the new row to avoid displaying the dummy value. The chart update will be then correct.

The axis labels of 3D charts are not correctly rendered when saved as PDF, PS, or PCL files.

This is a known issue and there is currently no workaround other than using the JPEG or PNG data types instead.

Timeout in SNMP Table view or a tooBig error status is returned when refreshing a table, but single columns of the table can be retrieved without problems.

The packet size of the response might be too big.

Try reducing the "Max VBs per PDU" value or increasing the "Maximum inbound message size" value of the transport mapping used in Preferences. If the target is not a SNMPv1 target, then reducing the "Get Bulk repetitions" value will also help to reduce the size of the response PDU send back by the target.

Determining a target's MIB set detects MIB modules that are not implemented by the agent.

The agent does not implement lexicographic ordering correctly.

Enable logging with a log table size of at least 100 entries and set the logging priority for SNMP to DEBUG. Verify the responses got from the target for correct lexicographic ordering.

Alternatively, you can also use the Packet Analyzer to inspect the responses sent by the agent.

Sometimes timeout on a specific target.

Timeout or retries value to small.

First, try to increase the timeout value in Target Preferences. If this does not help, try to increase the "Number of retries" value.

MIB Explorer seems to hang after having connected to a remote monitor or after having deployed a monitor.

The remote MIB Explorer server is most likely behind a firewall or the client and remote are connected using Network Address Translation (NAT). The server therefore cannot open a connection to the client to inform the client about monitor data updates. To solve the problem, please check the "Do not use callback connection" option when connecting to a remote server or when deploying to a remote server. If the client already "hangs" please wait (up to 6 minutes) for the TCP connection to time out. The MIB Explorer will respond again.

Timeout on any type of request for a specific target.

Wrong community or USM user specified for the target.

Change the community or the user settings in Target Preferences.

Internal 1405 (encryption) or 1406 (decryption) error when sending or receiving SNMPv3 request with strong encryption (AES192 or AES256).

Your current Java Runtime Environment does not have a security policy installed that allows strong encryption. If the corresponding prerequisites are met, you can download strong encryption from http://java.oracle.com.