In article ,
James Waldby wrote:
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".

Instead of ping try tracert. This will give you a hop-by-hop report
of connection. You can see where it fails:

tracert 206.188.219.158

Tracing route to 206.188.219.158 over a maximum of 30 hops

first hops omitted

5 2 ms 1 ms 2 ms sl-crs2-sj-0-4-0-3.sprintlink.net [144.232.0.249]
6 2 ms 2 ms 2 ms sl-st31-sj-0-15-0-0.sprintlink.net [144.232.8.151]
7 2 ms 2 ms 2 ms 144.232.9.142
8 13 ms 13 ms 13 ms te0-0-0-0.ccr22.sjc03.atlas.cogentco.com [154.54.7.22]
9 15 ms 15 ms 15 ms te0-5-0-3.ccr22.sjc01.atlas.cogentco.com [154.54.41.213]
10 15 ms 14 ms 14 ms te0-3-0-2.ccr22.lax01.atlas.cogentco.com [154.54.2.149]
11 49 ms 49 ms 49 ms te0-1-0-6.ccr22.iah01.atlas.cogentco.com [66.28.4.237]
12 71 ms 71 ms 71 ms te0-2-0-7.ccr22.atl01.atlas.cogentco.com [66.28.4.89]
13 72 ms 79 ms 72 ms te2-1.ccr01.atl05.atlas.cogentco.com [154.54.46.122]
14 73 ms 73 ms 73 ms 38.122.18.182
15 73 ms 73 ms 74 ms 209.17.112.38
16 73 ms 73 ms 73 ms mcapsweb1.monstercommerce.net [209.17.114.75]
17 74 ms 73 ms 74 ms 206.188.219.158

Trace complete.

If you are not on windows the command is most likely traceroute
and works slightly differently.

---john.