Web Browsers

[fdlite]

Been trying to access my web page and unable to thru Comcast.  From other locations (that are not using Comcast) I am able to access my web page.  When I do a ping or trace route to my web site I get timeouts at once I get into the Comcast 'network' modem.  Used to work up until last week or so and I don't understand why it isn't now.  Did something change at Comcast, is there now something I need to setup in IE?

I just like to update my web site again.

Thanks,

Dane

[fdlite]

Sorry, forgot to attach a ping and trace route.

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

C:\>ping fdlite.net76.net

Pinging fdlite.net76.net [31.170.162.163] with 32 bytes of data:

Request timed out. Request timed out.

Request timed out. Request timed out.

Ping statistics for 31.170.162.163:     Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\>tracert fdlite.net76.net

Tracing route to fdlite.net76.net [31.170.162.163] over a maximum of 30 hops:

1     1 ms    <1 ms    <1 ms  REDDOLPHIN [192.168.1.1]  

2    36 ms    29 ms    30 ms  c-71-204-92-1.hsd1.ga.comcast.net [71.204.92.1]

3     *        *        *     Request timed out.  

4     *        *        *     Request timed out.  

5     *        *        *     Request timed out.  

6     *        *        *     Request timed out.  

7     *        *        *     Request timed out.  

8     *        *        *     Request timed out.  

9     *        *        *     Request timed out.  

10     *        *        *     Request timed out.  

11     *        *        *     Request timed out.  

12     *        *        *     Request timed out.  

13     *        *        *     Request timed out.  

14     *        *        *     Request timed out.  

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     *        *        *     Request timed out.

Trace complete.

C:\>

[BruceW]

A trace like that suggests that Comcast is blocking the host's IP (I see similar results in Pennsylvania). For help, call Customer Security Assurance at 1-888-565-4329, 6am-2am Eastern time, http://security.comcast.net/get-help/contact-comcast-security.aspx.

[fdlite]

Thank you Bruce for the information, I will try contacting them tomorrow (since it is after 2 PM EST).  I could understand blocking if the site was a porn site, which it isn't, but it is a free web hosting site that I am using, so that might be an issue.  But my question is why now?

Thanks,

Dane

[BruceW]

---

fdlite wrote: ... I will try contacting them tomorrow (since it is after 2 PM EST). ...

---

That time interval is one we don't see every day. It means that CSA opened at 6AM today, and will remain open until 2AM tomorrow. IOW, they're open right now.

---

... I could understand blocking if the site was a porn site, which it isn't,

---

Don't think Comcast would block porn, but that IP does host a number of other sites, and if one of them is distributing viruses, for example, Comcast might block the IP, which blocks all the sites on it.

Give CSA a call. And please let us know how it goes, OK?

[Again]

FWIW, I'm not on the Comcast server and I can't access fdlite.net76.net at all.

Here's the tracert from where I am at the moment.  Maybe it will help.

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

C:\>ping fdlite.net76.net

Pinging fdlite.net76.net [31.170.162.163] with 32 bytes of data:
Reply from 31.170.162.163: bytes=32 time=76ms TTL=51
Reply from 31.170.162.163: bytes=32 time=74ms TTL=51
Reply from 31.170.162.163: bytes=32 time=84ms TTL=51
Reply from 31.170.162.163: bytes=32 time=97ms TTL=51

Ping statistics for 31.170.162.163:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 74ms, Maximum = 97ms, Average = 82ms

C:\>tracert fdlite.net76.net

Tracing route to fdlite.net76.net [31.170.162.163]
over a maximum of 30 hops:

  1    28 ms    45 ms    29 ms  cpe-70-123-112-1.tx.res.rr.com [70.123.112.1]
  2    11 ms    13 ms    13 ms  tge7-2.dllatx1c-er02.texas.rr.com [70.125.219.29
]
  3    22 ms    34 ms    23 ms  tge3-6.dllatx10-tr02.texas.rr.com [24.175.38.216
]
  4    19 ms    23 ms     *     24.175.49.8
  5    20 ms    48 ms    32 ms  ae-4-0.cr0.hou30.tbone.rr.com [66.109.6.54]
  6    16 ms    18 ms    23 ms  ae-0-0.pr0.dfw10.tbone.rr.com [66.109.6.181]
  7    22 ms    20 ms    23 ms  prr01dllstx-tge-0-2-0-6.dlls.tx.charter.com [96.
34.149.21]
  8    27 ms     *       35 ms  bbr02ftwotx-tge-0-3-0-6.ftwo.tx.charter.com [96.
34.3.106]
  9    47 ms    47 ms    46 ms  bbr01slidla-tge-0-1-0-4.slid.la.charter.com [96.
34.0.155]
 10    66 ms    65 ms    66 ms  bbr02slidla-tge-0-0-0-0.slid.la.charter.com [96.
34.0.33]
 11    54 ms    71 ms    47 ms  bbr01atlnga-tge-0-0-0-8.atln.ga.charter.com [96.
34.0.35]
 12    73 ms    81 ms    52 ms  crr01sghlga-tge-0-2-0-3.sghl.ga.charter.com [96.
34.2.75]
 13    82 ms    71 ms    52 ms  acr02atlnga-tge-0-0-0-0.atln.ga.charter.com [96.
34.72.179]
 14   127 ms    44 ms    51 ms  75-131-187-34.static.gwnt.ga.charter.com [75.131
.187.34]
 15   111 ms    78 ms    77 ms  te-4-0-0.crr01-avl.avl.immedion.com [67.23.161.1
44]
 16    92 ms    79 ms    79 ms  67.23.161.251
 17     *      136 ms   969 ms  ashv1.main-hosting.com [208.69.231.10]
 18    83 ms    97 ms    75 ms  31-170-162-163.main-hosting.com [31.170.162.163]


Trace complete.

C:\>

[fdlite]

Not sure why you weren't able to access outside of Comcast, as from a friend's house (who isn't using Comcast), had no problem getting to my site, from work no problem.

Anyway, after a while on the phone with Comcast this morning and being turned over to their security area, they agree that there was an issue on their side.  Good news, is it is now fixed and I can once again access my site and make some changes/updates.

From me to Comcast, thanks!

Dane

[Again]

Glad you got it fixed!  Happy updating!