CEO's Blog

If you encounter an Internet Explorer script errors when launching or using IPCheck’s WinGUI, please check in the Administrator Control Panel (under Windows’ START menu, in IPCheck’s program group) whether the DNS entry / IP address provided under the “System” tab matches the information provided in the WinGUI login information.

Make certain to use exactly the same data provided: i.e. if using an IP address in the Administrator Control Panel, make sure that the server login parameter provided in the WinGUI is also the IP address. In case the Admin Control Panel contains a DNS entry, provide the same for the WinGUI.

Note: please also make sure to provide the port number unless using the default value of port 80.

When working with WMI (Windows Management Instrumentation) and experiencing problems with the error code “80041010″ and the message “Invalid Class”, usually the problem is caused by some required WMI classes that are not properly registered in the Windows system. The solution is to (re-)register all the WMI classes.

Read our latest knowledgebase article What to do when getting the ‘Code Error 80041010 - Invalid Class’ error while creating or using WMI sensors for more details.

The latest version 5.4.1.863/864 of IPCheck Server Monitor includes four minor bugfixes (support for 64bit WMI sensors, among others) as well as an optimized dump of monitoring data to the disk (makes sure that even for installations with many sensors the sensor intervals are not delayed by data dumping). Find out more about the other changes in the IPCheck version history.

In order to avoid installation and configuration issues, it is generally better to install PRTG and IPCheck directly on the host server, seeing as certain system pop-ups are not properly carried forward when connecting to the server via a RDP session.

Read more in our Knowledge Base Article.

As of the new Apple operating system Leopard, Macintosh users are able to monitor their resources and their hardware based on SNMP. John Welch has posted an article explaining the implementation and functionality of this newly included SNMP system at The Unofficial Apple Weblog. You can find the article under http://www.tuaw.com/2007/12/05/john-welchs-guide-to-snmp-on-leopard. SNMP is one of the ways to monitor your systems with both our flagship software products, PRTG and IPCheck.

Recently we came across the following three pretty notable pages provided by Cisco, allowing users to find Cisco MIBs and to discern OID segment almost at a glance.

(more…)

Version 5.4.1.855 of IPCheck Server Monitor includes some changes and enhancements for SQL and System sensors and a bugfix for WMI sensors.

See the history for details and download this latest version.

WMI (”Windows Management Instrumentation”) is Windows built-in monitoring and management technology (introduced with Windows 2000). It’s a great way to monitor Windows systems in your network.

IPCheck Server Monitor already works with WMI. As accessing WMI counters over a network is not exactly trivial, our new Paessler WMI Tester is a tool that can be used to test the accessibility of WMI counters in a quick and easy manner.

Since introducing WMI sensors to IPCheck with version 5.4.1.834/835 we have received multiple queries on how to monitor processes using WMI Query sensors. Doing so is actually quite simple.

Read more in the Knowledge Base article about “Monitoring the thread count of active processes via WMI Query sensors”

The other day we found a Vista machine in our network that we could not remotely monitor from the LAN using WMI. But WMI monitoring was working fine on all our other Vista machines…

Finally we discovered that on the specific machine the NOD32 anti virus software was causing the same problems for WMI as we had already seen for SNMP (see my post from July 5th about dysfunctional SNMP on Vista).

As soon as we applied the procedure described in the article from July everything was fine for WMI.