Network Pinger

4.5/5 4

Last updated: Mar 14, 2012 Certified 100% CLEAN Freeware

SOFTPEDIA® DOWNLOAD NOW 5,286 downloads so far

Simple-to-handle application that can be used in order to ping several IP addresses, scan ports, bring up Whois information and save all data to a file on the HDD. #IP pinger #Ping tool #Trace route #Pinger #Ping #Tracert

Softpedia Review

specifications

Free Download

Review by: Madalina Boboc

3.0/5

Network Pinger is a software utility that provides users with a simple means of pinging a given IP address, scan ports, bring up Whois information about a website and view traceroute stats.

This app is portable and therefore, it is possible to bypass the setup process, and you should know that the Windows registry is not going to be changes in any way.

Moreover, you can take Network Pinger anywhere with you, by simply moving the program files to a USB thumb drive or other similar device.

This application enables you to perform multiple operations pertaining to the network. For example, it is possible to ping a user-input IP address or range, as well as view a graphical representation of the average response time in milliseconds, stats regarding the number of received, sent or lost data packets, and approximate round trip in milliseconds.

In addition to that, it is possible to trace route to an IP address and return information about the process, as well as scan particular ports in order to check if they are opened or not, as well as view information about the working ones.

With just a few clicks you can run a Whois query pertaining to a specific website, and find out details such as domain name, registrar, referral URL, name server, status and creation and expiration date. You can find out the IP address a domain name points at, as well as list WMI classes and start some queries.

Last but not least, you should know that regardless of the action you perform, it is possible to open the results in a pretty simple built-in text editor, and save them to a RTF or TXT document.

To sum up, Network Pinger is a handy tool for power and novice users that are interested in pinging an IP address or finding out more information about it, without hindering the computer’s performance or popping any errors. Nevertheless, you should know that the interface is not particularly appealing and might seem a bit cluttered, and the response time leaves a lot to be desired.

What's new in Network Pinger 1.0.1.0:

Check-for-new-versions function added - As I was changing things, specially due to the bug I describe below with the Name Resolution and others, I thought something like: "and now? all the people that may have that bug and I don't have a way to tell them". So, I've decided to add an update checking system to the software, as it's important that people know when new versions are released. I've added a button that users can click and also an option on the Help Menu, so that when users click it, it'll instantly search on Network Pinger's website for new versions, and if it finds something new, it will warn the user of new versions and if no new versions were found it will tell the user which is the last version and its release date. Also, it comes with a new auto-check for updates functionality. By default (if the "config.dat" file is deleted), when it creates a new one, comes with the auto-check function with the monthly check chosen, to check once per month for new versions. You can chose also the weekly auto-check option, of disable auto-checks at all on the help menu, and in that case no automatic checking for new versions would ever been done unless the user clicks on the check-for-new-versions button. So you can disable or configure or even use it anytime. It's specially for this new function that I jumped the version to 1.0.1.0 as this time it wasn't just some minor bugs that were corrected;
Corrected an important bug in Name Resolution - I was using Network Pinger to do Reverse DNS to some IPs, and noticed that sometimes it failed. Sometimes I thought it was my computer lacking memory or something (you can't imagine how I use it), but it happened a lot. I've tested and I've found out a simple mistake. There were some important tables with data that were only populated on the Whois functionality, and not the DNS one. So if you ran the DNS tools after using the Whois tool, it would work perfectly, but if you used the DNS or Reverse DNS tool before the Whois one, as the data wasn't initialized, the Name Resolution would fail and even the domain names not recognized sometimes... It's curious how I used it so long without noticing this big bug! It is corrected now;

Read the full changelog