I got it down to a second or two per pc using a command line program called
"fping". I use the Process class to launch it invisibly and redirect its
output back to my app. It has switches that allow me to set the number of
ping requests (which I set to 1), and one that allows me to turn off all
messages except for the single ping result. I can also tell it how long to
wait for a reply (0-5 seconds) so I can tailor it to my network speed.
Unless I run across something better, this is what I'll use.
"m.posseth" <po*****@planet.nl> wrote in message
news:42***********************@nova.planet.nl...
well i had a remoting project with exact the same problem , i solved this
by sending UDP broadcasts on the network to discover when a server starts
\ stops
however this requires that on all computers a application is running that
sends these messages
regards
Michel Posseth
"Terry Olsen" <to******@hotmail.com> schreef in bericht
news:%2****************@TK2MSFTNGP15.phx.gbl...I have a list of pc names that I need to go out and pull information
from. If they are all online, great! But when a PC is turned off (not
online), the program hangs for a good 40 seconds before moving on. Is
there a way for me to quickly see if a host is online or not? I'm
hoping for something less than 5 seconds per host.
*** Sent via Developersdex http://www.developersdex.com ***
