Download the Net-SNMP 5.1.2+ source and compile using MSVC++, MinGW or Cygwin as described in the Net-SNMP README.WIN32 file. This should create a working snmptrapd. See the question: How to I enable the Perl support for UCD-SNMP / Net-SNMP under Windows? Note: Net-SNMP 5.1.2 or higher is recommended if compiling under Windows as it contains the latest Windows specific compiling improvements.

If you have no plans on using the Net-SNMP Perl module (see the next question), then any recent version of Net-SNMP or UCD-SNMP should be sufficient with the exception of Net-SNMP 5.1. Net-SNMP 5.1.1 and higher can be used. If you plan on using UCD-SNMP 4.2.3 (provided by Compaq for RedHat 7.2), then you must at least use a newer version of snmptrapd. If you plan on enabling the Net-SNMP Perl module, Net-SNMP v5.1.1 or higher is recommended. This will allow you to use all the features of snmptt.

SNMPTT does not REQUIRE the Perl module, but it is recommended. By enabling the Perl module, you will get the following benefits: Conversion of INTEGER values to enumeration tags (for example: Status is now OK instead of Status is now 1) Ability for traps passed from snmptrapdor loaded from the snmptt.conf files to contain symbolic OIDs such as linkDown and IF-MIB::linkUp Variable syntax, description and enums when converting a MIB file using snmpttconvertmib Unless Net-SNMP 5.1.1 or 5.0.8 / 5.

Install ActiveState ActivePerl and then the ActivePerl .ppm module included in the Net-SNMP binary available from the Net-SNMP web site. If you compiled your own version of Net-SNMP, see the perl/README document for instructions on compiling the Perl modules. Download the Net-SNMP 5.1.2+ source and compile using Cygwin as described in the Net-SNMP README.WIN32 file.

Typically not. SNMP products provide device specific information, where protocol analyzers obtain all their information by examining the traffic on the LAN. For example, an SNMP collection utility could not provide session delta time stamps for a UNIX telnet session, nor can SNMP provide bandwidth utilization statistics directly.

By default, net-snmp is configured only to allow a really small amount of information to be accessed by the default community name of "public". The easiest way to change this is to find a line like: view systemview included .1.3.6.1.2.1.1

SNMP (Simple Network Management Protocol) is the protocol governing network management and the monitoring of network device and their functions. It is not limited to TCP/IP network.

This section is work in progress, but see the front page for info about CSBrowse. The control works fine from .NET apps, but the control is regarded as unmanaged code. If you're looking for a cross-platform solution, then some day, the GTK browser widget may be a better fit That is if the Mono crew consider doing their own thing instead of aping MS at every step, and produce a viable GTK# with a component for browsing.

The .NET Framework SDK is free and includes command-line compilers for C++, C#, and VB.NET and various other utilities to aid development. Microsoft Visual Studio Express editions are cut-down versions of Visual Studio, for hobbyist or novice developers.There are different versions for C#, VB, web development etc. Originally the plan was to charge $49, but MS has decided to offer them as free downloads instead, at least until November 2006.

Yes. COM components are accessed from the .NET runtime via a Runtime Callable Wrapper (RCW). This wrapper turns the COM interfaces exposed by the COM component into .NET-compatible interfaces. For oleautomation interfaces, the RCW can be generated automatically from a type library. For non-oleautomation interfaces, it may be necessary to develop a custom RCW which manually maps the types exposed by the COM interface to .NET-compatible types. Here's a simple example for those familiar with ATL.

Yes. .NET components are accessed from COM via a COM Callable Wrapper (CCW). This is similar to a RCW (see previous question), but works in the opposite direction. Again, if the wrapper cannot be automatically generated by the .NET development tools, or if the automatic behaviour is not desirable, a custom CCW can be developed. Also, for COM to 'see' the .NET component, the .NET component must be registered in the registry. Here's a simple example. Create a C# file called testcomserver.

I just can not belive Ghost has droped the ball on this and is still requiring people to use floppies. The directions are clear, straight-forward and accurate. This is the most well-put-together doumentation I've EVER found relating to Ghost. I've worked with (read: struggled with) the program on and off for years, and have never found any documentation anywhere near this caliber. This is the guide I was looking for since Symantec are so incopetent to write it for us.

SNMP uses 161/udp for general purpose (request/response) communications, and 162/udp for traps. Additionally, the SNMP multiplexing protocol (smux, defined in RFC1227 http://www.ietf.org/rfc/rfc1227.txt) uses 199/tcp. Another SNMP extension, the AgentX protocol (RFC2741, http://www.ietf.org/rfc/rfc2741.txt) uses 705/tcp.

I want to use your control in a non-VB environment (e.g. Sybase or Borland) AND create it dynamically. It works on my development machine, but elsewhere it throws a license error.

Depending on how one counts, there are between three and five active groups. The two most popular seem to be "sie, hir, hir, hirs, hirself", (especially "hir"), and "zie, zir, zir, zirs, zirself". The latter apparently came into being after a German-speaking netizen objected to "sie" and "Sie", which in many contexts means "she" in German. Third and fourth, differing only in the first and maybe last word, are "e or ey, em, eir, eirs, eirself or emself".