On Wed, 17 Oct 2012 20:16:37 -0500, Karl Townsend wrote:

start program "command". Then enter "ping centerfiresystems.com".

Paul
I get "request timed out"

As iggy mentioned, name resolution might not be working for the
site, but it seems more likely a firewall program on your computer
is getting in the way. Anyhow, to see if it's a name resolution
problem, also enter the command "ping 206.188.219.158". It will
look different on your MS-Windows system, but what I see on my
linux system when pinging centerfiresystems.com or its numeric IP
or google.com or its numeric IP is shown below. On your
windows system leave out the -c3 option. If you can ping google
or 173.194.33.41 but neither of centerfiresystems.com or
206.188.219.158 then suspect a firewall has blocked that IP and
look at your firewall configuration and rules. If you can't ping
any of them, then suspect a firewall or similar has blocked the
ping program; but getting "request timed out" makes that unlikely.

Also, regarding the site itself, using firefox 16.0.1 on ubuntu
12.04 linux 3.2.0-32, addresses http://centerfiresystems.com/ or
https://centerfiresystems.com/ or centerfiresystems.com or
206.188.219.158 all end up at the same centerfiresystems http: page.

If ping cannot access a site, its unlikely your browser can either,
although ping uses ICMP protocol rather than HTTP protocol and some
sites may block ICMP while allowing HTTP. If you get ping to work
but not your browser, then in your browsers, clear all the cookies
and try to access centerfiresystems. In preferences make a note
about current preferences and then on the Security tab temporarily
turn off Block reported attack sites, try to access centerfiresystems,
then turn it back on. Similarly, temporarily turn off Block reported
web forgeries, try to access centerfiresystems, then turn it back on.

Ping results ---

$ ping -c3 centerfiresystems.com
PING centerfiresystems.com (206.188.219.158) 56(84) bytes of data.
64 bytes from 206.188.219.158: icmp_req=1 ttl=109 time=82.5 ms
64 bytes from 206.188.219.158: icmp_req=2 ttl=109 time=83.2 ms
64 bytes from 206.188.219.158: icmp_req=3 ttl=109 time=83.2 ms

$ ping -c3 206.188.219.158
PING 206.188.219.158 (206.188.219.158) 56(84) bytes of data.
64 bytes from 206.188.219.158: icmp_req=1 ttl=109 time=81.1 ms
64 bytes from 206.188.219.158: icmp_req=2 ttl=109 time=82.1 ms
64 bytes from 206.188.219.158: icmp_req=3 ttl=109 time=81.5 ms

$ ping -c3 google.com
PING google.com (173.194.33.41) 56(84) bytes of data.
64 bytes from sea09s02-in-f9.1e100.net (173.194.33.41): icmp_req=1 ttl=54 time=31.0 ms
64 bytes from sea09s02-in-f9.1e100.net (173.194.33.41): icmp_req=2 ttl=54 time=38.0 ms
64 bytes from sea09s02-in-f9.1e100.net (173.194.33.41): icmp_req=3 ttl=54 time=35.7 ms

(From here, google.com randomly resolves to one of 173.194.33.32 ...
173.194.33.41 at the moment)

$ ping -c3 173.194.33.41
PING 173.194.33.41 (173.194.33.41) 56(84) bytes of data.
64 bytes from 173.194.33.41: icmp_req=1 ttl=54 time=30.7 ms
64 bytes from 173.194.33.41: icmp_req=2 ttl=54 time=30.6 ms
64 bytes from 173.194.33.41: icmp_req=3 ttl=54 time=31.8 ms

--
jiw