Home Networking

[#1]

I began receiving this error today on all devices (2 laptops, a desktop, and a tablet).  The devices work correctly on other wireless networks.  I only started receiving this error today after uploading a blog post to my blog at http://readytruth.com.  can you help?

[#2]

What program is creating this error?

[#3]

I'm using IE 9.  I know the problem is not my computer as I can disconnect from my verizon router and connect through the hotspot on my phone and everything works fine.  I tried reseting my router to "factory settings" and I still cannot get to readytruth.com.  I had just published an article there and immediately afterward was not able to access the site.  It must have something to do with my router because it works from other wireless access points.  Any adeas you may have would be very much appreciated.  Thanks, Mark

[#4]

[#5]

Can you also perform a trace route to your site and post up the results you get? It doesn't matter which computer you use to perform it, as long as you copy/paste it here. Your previous post seems to have an attachment which did not upload so if it was a trace, I can't see it.

To run a Traceroute in Windows XP:

Go to Start > choose run > type "cmd" > Press OK > In cmd, enter in this command: tracert readytruth.com . Once the trace is performed, right click the Window and choose Select All. Then press Enter to copy the trace. Paste the trace into your reply.

On Vista/Win7:

Go to Start > search for "cmd" in the search box. Open cmd application and follow the same instructions as outlined above.

On MacOS/UNIX systems:

Open up a Terminal Window (On Macs, it is located under Utilities in Applications) and enter in the following command: traceroute readytruth.com . From this point, go to Edit if on a Mac, and choose Select All, then Copy and paste the results here.

[#6]

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Mark>tracert readytruth.com

Tracing route to readytruth.com [216.120.240.100]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  192.168.1.1
  2    25 ms    17 ms    13 ms  L100.DLLSTX-VFTTP-60.verizon-gni.net [96.226.238
.1]
  3    15 ms    20 ms    14 ms  G5-0-2.DLLSTX-LCR-06.verizon-gni.net [130.81.183
.90]
  4    13 ms    14 ms    14 ms  so-7-1-0-0.DFW01-BB-RTR2.verizon-gni.net [130.81
.199.44]
  5    21 ms    14 ms    14 ms  0.ae2.BR2.DFW13.ALTER.NET [152.63.2.230]
  6    18 ms    14 ms    16 ms  ae7.edge2.dallas3.level3.com [4.68.62.33]
  7    20 ms    24 ms    19 ms  vlan80.csw3.Dallas1.Level3.net [4.69.145.190]
  8    15 ms    20 ms    17 ms  ae-83-83.ebr3.Dallas1.Level3.net [4.69.151.158]

  9    45 ms    44 ms    42 ms  ae-7-7.ebr3.Atlanta2.Level3.net [4.69.134.22]
 10    50 ms    55 ms    53 ms  ae-2-2.ebr1.Washington1.Level3.net [4.69.132.86]

 11    89 ms    75 ms    72 ms  ae-81-81.csw3.Washington1.Level3.net [4.69.134.1
38]
 12    53 ms    58 ms    62 ms  ae-82-82.ebr2.Washington1.Level3.net [4.69.134.1
53]
 13    70 ms    74 ms    71 ms  ae-4-4.ebr2.Newark1.Level3.net [4.69.132.102]
 14    63 ms    61 ms    54 ms  ae-22-52.car2.Newark1.Level3.net [4.69.156.38]
 15    59 ms    59 ms    59 ms  HOSTROCKET.car2.Newark1.Level3.net [4.79.190.46]

 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

C:\Users\Mark>

[#7 · Accepted solution]

I would try contacting your Host to see if perhaps their server might have firewalled your connection for some odd reason. It's possible. It's also possible your IP address changed while making a new post, and resulted in your connection getting stuck with BOGON filter issues.

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\>tracert readytruth.com

Tracing route to readytruth.com [216.120.240.100]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.3.1
  2     9 ms     9 ms     9 ms  10.15.3.1
  3     9 ms     9 ms    10 ms  so-1-1-0-0.BUFF-CORE-RTR1.verizon-gni.net [130.81.13.73]
  4    20 ms    19 ms    19 ms  as4-0.NY325-BB-RTR1.verizon-gni.net [130.81.20.104]
  5    20 ms    20 ms    20 ms  0.so-0-0-0.XT1.NYC4.ALTER.NET [152.63.1.41]
  6    20 ms    19 ms    20 ms  0.ae3.BR3.NYC4.ALTER.NET [152.63.16.181]
  7    23 ms    20 ms    20 ms  te-7-3-0.edge2.NewYork2.level3.net [4.68.111.137]
  8    21 ms    20 ms    21 ms  vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
  9    20 ms    20 ms    19 ms  ae-4-4.ebr1.NewYork1.Level3.net [4.69.141.17]
 10    21 ms    21 ms    31 ms  ae-2-2.ebr1.Newark1.Level3.net [4.69.132.98]
 11    21 ms    21 ms    22 ms  ae-12-51.car2.Newark1.Level3.net [4.69.156.6]
 12    26 ms    25 ms    24 ms  HOSTROCKET.car2.Newark1.Level3.net [4.79.190.46]
 13    26 ms    26 ms    26 ms  alpha.hrwebservices.net [216.120.240.100]

Trace complete.

C:\Users\>

[#8]

You we're correct.  I sent this string of posts  to the host and they solved the problem within 5 minutes.  Thanks for the help

[#9]

Glad to hear that solved the issue