|
-
Dec 22nd, 2005, 04:04 AM
#5
Re: Problem with My.Computer.Network.Ping
Hello
From my experience if you are looping the pings one after the other then it will appear to take a long time, especially if some of the pings are non-responsive. The article I pointed you at gets round this by creating each ping as a seperate thread. The author suggests that the program works reliably with up to and including 200 seperate IP addresses.
I extended my program to include a timer for each IP that I am pinging, with this timer recording how long an IP address has been "UP" for or "DOWN" for, with an additional "WARNING" state, i.e. if there are three dropped packets it moves to the warning state and then after six say it would move to "DOWN". A little bit of overkill maybe, but we are trying to monitor connections to our VPN, so a record of exactly how long a connection has been up or down for is very useful.
If you need any more help, I will try as best as I can.
Gary
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|