Skip to content
Zanmcdaniel's profile

New Contributor

 • 

4 Messages

Friday, July 17th, 2015 6:00 PM

Can't Reach a Particular Site-Trouble in the Comcast network?

My wife shares website management duty with a charity hosted with an outsourced company. The site is up as per serviceuptime.com, but pings time out to it repeatedly. This problem has occurred for the past 12 hours at least.

 

Is there a known problem on the network? I can successfully ping across the path to the closest destination but can't reach the site. My notes are listed below. Any help would be greatly appreciated.

 

Serviceuptime.com shows the Fayettehumane.org site up.
Below are the results when it was reached from locations all over the globe.

Quick check results for fayettehumane.org (http)
Country     City     Response time     Check result
Italy     Florence     0.187     Ok
United States     New York, NY     0.071     Ok
United States     San Jose, CA     0.069     Ok
United States     Scranton, PA     0.192     Ok
United States     Miami, FL     0.066     Ok
United States     Saint Louis, MO     0.058     Ok
Germany     Gunzenhausen     0.483     Ok
France     Strasbourg     0.560     Ok




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

C:\Windows\system32>tracert fayettehumane.org

Tracing route to fayettehumane.org [64.235.229.56]
over a maximum of 30 hops:

  1     5 ms     7 ms     5 ms  10.1.10.1
  2    13 ms    10 ms    10 ms  96.120.5.137
  3    18 ms    27 ms    33 ms  xe-7-1-0-sur01.f1fayette.ga.atlanta.comcast.net
[68.85.233.85]
  4    27 ms    27 ms    20 ms  xe-6-0-13-0-ar01.b0atlanta.ga.atlanta.comcast.ne
t [68.85.111.165]
  5    28 ms    26 ms    29 ms  he-0-4-0-4-cr02.56marietta.ga.ibone.comcast.net
[68.86.95.121]
  6    25 ms    20 ms    28 ms  c-eth-0-2-0-pe05.56marietta.ga.ibone.comcast.net
 [68.86.86.82]
  7    29 ms    19 ms    12 ms  te0-0-0-19.ccr21.atl02.atlas.cogentco.com [154.5
4.10.233]
  8    29 ms    29 ms    29 ms  be2051.ccr42.atl01.atlas.cogentco.com [154.54.0.
161]
  9    42 ms    41 ms    36 ms  be2173.ccr22.iah01.atlas.cogentco.com [154.54.29
.118]
 10    79 ms   139 ms    89 ms  be2066.ccr22.lax01.atlas.cogentco.com [154.54.7.
54]
 11    73 ms    69 ms    73 ms  be2599.rcr21.b002695-3.lax01.atlas.cogentco.com
[154.54.41.38]
 12    66 ms    74 ms    79 ms  38.104.232.158
 13    78 ms    79 ms    79 ms  72.34.61.138
 14    71 ms    77 ms    70 ms  vz004.elinuxservers.com [72.34.33.31]
 15     *        *        *     Request timed out.
 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     *        *

This shows we are connected to the internet, out network is fine however, we cannot get past the site i-p address of 72.34.61.138
out connection drops between that destination and the host (linux servers hosting fayettehumane.org at 72.34.33.31

Maybe something is down between them........

I can successfully reach the site just before the place hosting fayettehumane.org as shown below:

C:\Windows\system32>ping 72.34.61.138

Pinging 72.34.61.138 with 32 bytes of data:
Reply from 72.34.61.138: bytes=32 time=78ms TTL=244
Reply from 72.34.61.138: bytes=32 time=81ms TTL=244
Reply from 72.34.61.138: bytes=32 time=70ms TTL=244
Reply from 72.34.61.138: bytes=32 time=75ms TTL=244

Ping statistics for 72.34.61.138:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 70ms, Maximum = 81ms, Average = 76ms

 

 

MY INFO:

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

C:\Windows\system32>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : promopusher
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : hsd1.ga.comcast.net

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : hsd1.ga.comcast.net
   Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Controlle
r
   Physical Address. . . . . . . . . : 00-14-22-E9-F9-CE
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2601:c7:8302:eb00::1bad(Preferred)
   Lease Obtained. . . . . . . . . . : Friday, July 17, 2015 7:33:15 PM
   Lease Expires . . . . . . . . . . : Friday, July 24, 2015 7:33:14 PM
   IPv6 Address. . . . . . . . . . . : 2601:c7:8302:eb00:e050:b50d:d811:33b5(Pre
ferred)
   Temporary IPv6 Address. . . . . . : 2601:c7:8302:eb00:609a:4906:e5ca:663a(Pre
ferred)
   Link-local IPv6 Address . . . . . : fe80::e050:b50d:d811:33b5%18(Preferred)
   IPv4 Address. . . . . . . . . . . : 10.1.10.184(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Friday, July 17, 2015 7:33:13 PM
   Lease Expires . . . . . . . . . . : Friday, July 24, 2015 7:33:17 PM
   Default Gateway . . . . . . . . . : fe80::bcd1:65ff:fe02:47f0%18
                                       10.1.10.1
   DHCP Server . . . . . . . . . . . : 10.1.10.1
   DHCPv6 IAID . . . . . . . . . . . : 117445666
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-67-72-10-00-14-22-E9-F9-CE

   DNS Servers . . . . . . . . . . . : 2001:558:feed::1
                                       2001:558:feed::2
                                       75.75.75.75
                                       75.75.76.76
   NetBIOS over Tcpip. . . . . . . . : Enabled

Accepted Solution

Gold Problem solver

 • 

610 Messages

9 years ago

Well, im seeing timeouts beginning at address 72.34.33.31, which has a DNS reference to "elinuxservers.com". All hops before that look fine, including your first Comcast hosts as well as what appears to be Cogent. I think your Comcast connection is fine. My guess would be a network issue between Cogent and "elinuxservers.com". I would contact both of those companies & ask whats up.

Accepted Solution

Problem solver

 • 

326 Messages

9 years ago

Your wife needs to setup with https://uptimerobot.com/  or some other free monitoring site that will page her if her website goes down, that way she won't be wasting your time and you won't be wasting anyone else's time when her hoster bites it.

 

It never ceases to amaze me the trust that people put in these hosters.  If you actually saw how they treat their sites and customers you would be shocked.  Your site may be very important to you but to a hoster the size of one of these hosters it's worth less than dirt.  They make their money by having a million "very important sites" just like yours stacked up and if one of them goes down it's no more of a bother to them than a flea bite to you is.

 

How much money do you pay Comcast for your connection every month?

 

How much money do you pay one of these hosters for a site every month?

 

Which is a bigger amount?

 

Now why on Earth would the company being paid 10 times LESS be MORE reliable?

Accepted Solution

Problem solver

 • 

305 Messages

9 years ago

You'll definitely want to reach out to your provider and get additional information. From what I can tell it's hitting their network, so your problem would likely be an internal one for them. 

New Contributor

 • 

4 Messages

9 years ago

Thanks! That did cross my mind-about the hosting company. Your help is greatly appreciated.

New Contributor

 • 

4 Messages

9 years ago

Thanks! Your help is greatly appreciated.