Re: Verify network connection from i

[Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>]

I wrote an article about this a long time ago that included a utility 
for programatically checking a connection. Unfortunately, it's probably 
not online anywhere anymore.  I may be able to dig it up if you can't 
find an easy solution.

IMHO, if you're checking something like this you should always check the 
specific thing you're looking for.  i.e. if you want to check HTTP, you 
should make a TCP connection on the same port (Default: 80) that the 
actual connection will require.

Checking a different way (like PING) is not good because each thing can 
be blocked individually.  In your case, as you've noted, they've blocked 
PING, so it can't be used to test for (whatever it is that you wanted to 
test).  It'd also be possible to block the other way...  allow PING and 
block (whatever).  Everything can be allowed/blocked individually.. so 
test the specific thing you want to know about, not a different protocol.

-SK


On 8/21/2018 11:00 AM, David Gibbs wrote:
> Folks:
>
> This may sound like a dumb question, but what tool or technique do you 
> use to verify a network connection to another system (internal or 
> external)?
>
> Yes, PING & TRACEROUTE are the obvious answers ... but, in my case, 
> ping & traceroute are (for whatever reason) blocked (both from the i 
> and my workstation).
>
> I've tried using wget in qshell (and qp2term), but I get a connection 
> refused error.
>
> Using wget I am able to retrieve the default index page from an IIS 
> instance I'm running on my workstation (which is in the same physical 
> network as the i).
>
> Any ideas?
>
> Thanks!
>
> david