Trouble Shooting
Trouble Shooting
Trouble Shooting
========================================================================
Table of Contents
-----------------
==========================================================================
1. MIB Browser does not receive SNMP notifications because of a firewall
--------------------------------------------------------------------------
Problem Description
-------------------
If there is a firewall on the PC running MIB Browser (e.g., the built-in
Windows Firewall or a third-party software firewall), or if there is a
firewall between that PC and the network nodes that send SNMP notifications
to MIB Browser, the firewall might be blocking traffic on the default
trap ports (IP/UDP 162 and IPv6/UDP 162). Consequently, MIB Browser does
not receive SNMP notifications sent from remote devices.
Symptoms
--------
MIB Browser does not receive any SNMP notifications sent to it from remote
SNMP agents, although the status of the default trap port (IP/UDP 162)
in the MIB Browser Preferences dialog box, Trap Ringer/Ports view is listed
as "Ready" and MIB Browser can receive Traps sent locally to the loopback
interface (127.0.0.1).
Solution
--------
Open the appropriate port(s) on the firewall (IP/UDP 162 and IPv6/UDP 162)
to allow passing SNMP Trap and Inform packets through. For instructions
on configuring the firewall, kindly refer to documentation that came
with it.
============================================================================
2. MIB Browser does not receive SNMP notifications because some other
process is occupying the trap port(s)
----------------------------------------------------------------------------
Problem Description
-------------------
If some third-party application other than Microsoft "SNMP Trap Service"
opens the default trap port (IP/UDP 162) before MIB Browser (actually its
trap receiving service - "MG-SOFT SNMP Trap Service"), then MIB Browser will
not be able to receive any SNMP Trap and Inform messages on default trap port.
Symptoms
--------
On startup MIB Browser displays the following message in the Query results
window panel: "Failed to register trap reception on default port 162".
Consequently, MIB Browser does not receive any SNMP notifications on
the default port, although MG-SOFT SNMP Trap Service is running.
Solution
--------
First, please check the status of the default trap port (IP/UDP 162) in
MIB Browser. To do this, open the MIB Browser Preferences dialog box from
the View menu and switch to the Trap Ringer/Ports view. If the status of
the IP/UDP port 162 is listed as "Down", then probably some other trap
receiving application/process running on the same computer is occupying
this port and and because of that MIB Browser (actually, MG-SOFT SNMP Trap
Service - MgWTrap3.exe) cannot bind to that port to receive SNMP Trap/Inform
messages.
This command prints out all occupied UDP ports. If it prints two lines
like this:
Check again the status of IP/UDP port 162 in MIB Browser Preferences
dialog (CTRL+R), Trap Ringer/Ports view (its status should be "Ready").
Finally, check if MIB Browser can now receive Traps by sending a test
Trap to it using the bundled sendtrap.exe utility. To do that, open
the CMD window (Start->Run:CMD), change directory to
"C:\Program Files\MG-SOFT\MIB Browser\Bin"
and execute the following command:
sendtrap 127.0.0.1
The Trap Ringer Console window should display a new Trap message.
========================================================================
3. MIB Browser's splash screen displayed longer than usually
------------------------------------------------------------
Problem Description
-------------------
Sometimes, MIB Browser cannot properly initialize a notifications
receiving module at startup. In this case the program startup takes
longer than usually. This behavior is mostly related to the
Microsoft's SNMP Trap service.
Symptoms
--------
The MIB Browser's splash screen, which is normally shown only for
a few seconds at the program startup, remains displayed for a few
minutes showing a notice 'Registering Notifications...'.
Solution
--------
Check if you have the Microsoft's SNMP Trap service running or not.
If not, set the service to 'Automatic' startup at boot time (or
disable it, if you do not need it), but do NOT configure it for
'Manual' startup.
========================================================================
4. General guidelines for reporting the problem
-----------------------------------------------
Before reporting the problem, make sure that you are using the latest
version of the software as available from MG-SOFT's download page at
http://www.mg-soft.com/download.html. Report the problem only in case
you can reproduce it by using the latest version of the software and
you cannot find a suitable problem solution description in this document.
========================================================================