Click here to Skip to main content
15,906,628 members
Articles / Programming Languages / Visual Basic
Article

C# Ping Component

Rate me:
Please Sign up or sign in to vote.
4.32/5 (28 votes)
30 Mar 20052 min read 381.5K   12.3K   83   53
An easy to use C# ping component.

Sample Image - CSharpPing.jpg

Introduction

While working on a project that needs to check the quality of the network connection, I've found that there is no easy way to ping another computer. I expected there would be something in the framework (somewhere in the System.NET namespace) to do this as it seems like a common thing to want to do, but I could find nothing so my search turned to the web. While I was able to find some c# ping examples, none of them were very well designed. I wanted a ping utility that would let me ping a remote machine any number of times and return the ping statistics in a sensible manner (that is, not something I'd have to parse) so I decided that I'd make my own.

Most of the ping code I saw on the net seemed to be derived from this MSDN article written by Lance Olson which was written way back when for the Beta 1 release of .Net (whether it cited him or not...). I based my ping utility on this code along with this article, written by Peter A. Bromberg, PhD, which updated the Olson's code to work with .NET version 1. Using this code as a starting point I've tried to make it a little more OO by creating a couple more classes and moving the code around, so that they do their own work. I think the code makes a lot more sense now and is much easier to understand and use. I used the Windows command line ping command as a baseline for the information I wanted to return, so I created a PingResponse object that encapsulates all and gets returned instead of an int or string. I'm not going to write up a detailed description of exactly how the code works as it is either self-explanatory or simply works because that's how you have to do it (most of the ICMP class). I've included a very simple client form to show how to use the ping utility asynchronously, which I imagine, how you'd want to use it most of the time.

Using the code

To use this component simply create a Ping object and call the PingHost or BeginPingHost function.

Synchronous Example:

C#
private void Ping(string hostname)
{
    //Create ping object
    Ping netMon = new Ping();

    //Ping host (this will block until complete)
    PingResponse response = netMon.PingHost(hostname, 4);

    //Process ping response
    if (response != null)
    {
        ProcessResponse(response);
    }
}

Asynchronous Example:

C#
//Create ping object
Ping netMon = new netMon();

private void Load()
{
    //Wire events (in constructor or InitializeComponent)
    netMon.PingError += new PingErrorEventHandler(netMon_PingError);
    netMon.PingStarted += new PingStartedEventHandler(netMon_PingStarted);
    netMon.PingResponse += new PingResponseEventHandler(netMon_PingResponse);
    netMon.PingCompleted += new PingCompletedEventHandler(netMon_PingCompleted);
}

private void Ping(string hostname)
{
    //Start ping
    IAsyncResult result = netMon.BeginPingHost(
                     new AsyncCallback(EndPing), hostname, 4);
}

private void EndPing(IAsyncResult result)
{
    netMon.EndPingHost(result);
}

private void netMon_PingStarted(object sender, PingStartedEventArgs e)
{
    //Process ping started
}

private void netMon_PingResponse(object sender, PingResponseEventArgs e)
{
    //Process ping response
}

private void netMon_PingCompleted(object sender, PingCompletedEventArgs e)
{
    //Process ping completed
}

private void netMon_PingError(object sender, PingErrorEventArgs e)
{
    //Process ping error
}

Known Issues / Further Enhancements

  • The first ping is sometimes longer than it should be. I suspect this is because of some extra time taken to create the initial socket connection and could be eliminated by simply dropping that first ping time.
  • Currently, you can only cancel when the PingResponse event is fired. It would be nice to be able to cancel at any time and have it processed immediately.
  • I should really keep track of the ping response type per response instead of for the whole set of responses. I simply haven't got around to change the PingReponse yet.

History

  • Version 1.0: Initial release.

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here


Written By
Web Developer
United States United States
This member has not yet provided a Biography. Assume it's interesting and varied, and probably something to do with programming.

Comments and Discussions

 
QuestionSocket Exception Pin
hezhicheng11-Apr-06 5:38
hezhicheng11-Apr-06 5:38 
AnswerRe: Socket Exception Pin
hezhicheng11-Apr-06 5:41
hezhicheng11-Apr-06 5:41 
GeneralRe: Socket Exception Pin
Wesley Brown11-Apr-06 7:00
Wesley Brown11-Apr-06 7:00 
NewsRe: Socket Exception Pin
hezhicheng12-Apr-06 2:58
hezhicheng12-Apr-06 2:58 
GeneralSynchronous timeout parameter not what it seems Pin
Roland_W6-Feb-06 2:41
Roland_W6-Feb-06 2:41 
GeneralCode update Pin
Johan Roos27-Jan-06 1:02
Johan Roos27-Jan-06 1:02 
GeneralRe: Code update Pin
Member 36263024-Sep-13 23:02
Member 36263024-Sep-13 23:02 
QuestionStatistical error? Pin
Ricardo Mendes20-Dec-05 6:19
Ricardo Mendes20-Dec-05 6:19 
I've put the Ping class to ping an unreachable host. All the PingResponse events give me a timeout result. But the PingCompleted event tells that not all the packets have been lost. What is wrong? Am I misinterpreting the results?
Thank you.
Questionerror? Pin
missjasper12-Dec-05 7:21
missjasper12-Dec-05 7:21 
AnswerRe: error? Pin
simonnews29-Dec-08 11:59
simonnews29-Dec-08 11:59 
GeneralSystem.Net.NetworkInformation.Ping Pin
Kristofer Liljeblad18-Nov-05 11:28
Kristofer Liljeblad18-Nov-05 11:28 
GeneralRe: System.Net.NetworkInformation.Ping Pin
DigiOz Multimedia17-Oct-07 7:38
DigiOz Multimedia17-Oct-07 7:38 
Generalunmanaged code Pin
ThPloeger27-Sep-05 1:52
ThPloeger27-Sep-05 1:52 
QuestionWhy 60 bytes? Pin
Einar Kvandahl29-Jul-05 11:43
Einar Kvandahl29-Jul-05 11:43 
GeneralAsync ping doesn't seem to return a PingResponse Pin
stevehiner1-Jul-05 12:08
stevehiner1-Jul-05 12:08 
GeneralRe: Async ping doesn't seem to return a PingResponse Pin
Wesley Brown12-Jul-05 8:17
Wesley Brown12-Jul-05 8:17 
GeneralThanks! Pin
Ben Buckland21-Jun-05 23:36
Ben Buckland21-Jun-05 23:36 
GeneralResponse from nowhere... Pin
ibleif19-Apr-05 7:26
ibleif19-Apr-05 7:26 
GeneralRe: Response from nowhere... Pin
Tust26-Apr-05 11:09
Tust26-Apr-05 11:09 
GeneralQuick and Dirty Ping Pin
_TAD_7-Apr-05 9:44
_TAD_7-Apr-05 9:44 
GeneralRe: Quick and Dirty Ping Pin
milesha11-Apr-05 22:50
milesha11-Apr-05 22:50 
GeneralRe: Quick and Dirty Ping Pin
Wesley Brown12-Jul-05 3:50
Wesley Brown12-Jul-05 3:50 
GeneralRe: Quick and Dirty Ping Pin
Andy@15-Sep-05 23:00
Andy@15-Sep-05 23:00 
GeneralFirst ping issue Pin
leppie30-Mar-05 19:31
leppie30-Mar-05 19:31 
GeneralRe: First ping issue Pin
Wesley Brown31-Mar-05 3:47
Wesley Brown31-Mar-05 3:47 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.