There are things in the flow of your script that appear to be remnants of several attempts to approach your task in slightly different ways. For example, $host is used early on before it is given a value. Toward the bottom, $stop_time is used without being given a value.

You need some feedback from your script to help you sort things out. If you have telnet access to the server, run the script from the command line. The results may be instructive.

If you do not have telnet access, you need to get the server to cough up messages to your web browser. Try:

use CGI qw(:standard);    # you already have this
use CGI::Carp;
use CGI::Carp qw(fatalsToBrowser);
local $SIG{__WARN__} = \&Carp::cluck;
[download]

Later, when things are better, you will likely want to remove these lines or comment them out.

Also, use strict and include -w in your hash-bang line. They do wonders for helping you see where you may have slipped up.

Having said all this, I have gone to the docs as you clearly have done, and done some (frustrated) playing around. Turns out that the protocol really does make a difference. 'udp' dies ungracefully in different ways on two different OS's. 'tcp' reports nobody home. 'icmp' reports the servers are responding. Here's a script I ran from the command prompt on a Linux machine.

use Net::Ping;
my @protocols = qw(icmp tcp);
my @host_array = ("www.google.com",
                  "irc.webchat.org",
                  "64.177.244.76");
foreach my $proto (@protocols) {
   my $p = Net::Ping->new($proto);
   foreach my $host (@host_array) {
      print "With $proto, $host does ";
      print "NOT " unless $p->ping($host);
      print "respond\n";
   }
   $p->close();
}
[download]

Result:

With icmp, www.google.com does respond
With icmp, irc.webchat.org does respond
With icmp, 64.177.244.76 does respond
With tcp, www.google.com does NOT respond
With tcp, irc.webchat.org does NOT respond
With tcp, 64.177.244.76 does NOT respond
[download]

Now here's the gotcha. I did this from the command prompt because you need root privilege to use the icmp protocol on a Linux machine. No good if you want to run this from a web page. And the tcp protocol option crashes on my Win98 machine.

Yuck! No easy answers but I hope this helps you sort things out.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.