|
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
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
