Can't reach fios.asurion.com from Verizon FiOS, but other people on Verizon FiOS can

[Mark F]

I'm not sure if this is the proper group.

I'm "Mark F", a Verizon FiOS user in ZIP 10502 (NY). I
originally posted in alt.online-service.verizon, but it
now seems more like a network issue.

The problem is that I can't get to fios.asurion.com but many
other people can. I think that the problem is at ATT, but I'm
not sure.

Note that I get to 12.123.129.81 and can't get further, while
"Dave" gets to the same node and continue past and get reach
the desired node.

Some else thought that the problem was that 74.*.*.* wasn't known
everywhere or that my IP itself (in 106.*.*.*) was
not known.

Thank you for any help you can give me.
> From: "Mark F" <mark53916@gmail.com>
>
>
>
> >> Tracing route to fios.asurion.com [12.191.160.39]
> >> over a maximum of 30 hops:
>
> >> 1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
> >> 2 6 ms 34 ms 34 ms 74.101.54.1
> >> 3 8 ms 6 ms 7 ms 11-0-1-1253.NYCMNY-LCR-12.verizon-gni.net
> >> [130.81.139.36]
> >> 4 18 ms 7 ms 6 ms so-6-2-0-0.NY5030-BB-RTR1.verizon-gni.net
> >> [130.81.29.14]
> >> 5 9 ms 9 ms 10 ms 0.so-3-1-0.XT1.NYC8.ALTER.NET [152.63.10.33]
> >> 6 9 ms 9 ms 10 ms 0.so-6-0-0.XL3.NYC4.ALTER.NET [152.63.16.221]
> >> 7 9 ms 10 ms 9 ms 0.xe-3-2-0.BR2.NYC4.ALTER.NET [152.63.3.126]
> >> 8 10 ms 12 ms 9 ms 192.205.36.57
> >> 9 38 ms 36 ms 39 ms cr1.n54ny.ip.att.net [12.122.86.6]
> >> 10 34 ms 34 ms 34 ms cr1.phlpa.ip.att.net [12.122.5.242]
> >> 11 37 ms 37 ms 37 ms cr2.phlpa.ip.att.net [12.122.3.226]
> >> 12 40 ms 39 ms 39 ms cr2.cl2oh.ip.att.net [12.122.2.209]
> >> 13 38 ms 39 ms 39 ms cr1.cl2oh.ip.att.net [12.122.2.125]
> >> 14 38 ms 39 ms 39 ms cr2.nsvtn.ip.att.net [12.122.28.73]
> >> 15 40 ms 39 ms 39 ms gar1.nsvtn.ip.att.net [12.123.129.81]
> >> 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.
>
> | Who someone who can get to fios.asurion.com try it and post their
> | results please?
Dave speaking below:
>
> C:\1>tracert fios.asurion.com
>
> Tracing route to fios.asurion.com [12.191.160.39]
> over a maximum of 30 hops:
>
> 1 <1 ms <1 ms <1 ms 192.168.1.1
> 2 5 ms 3 ms 4 ms L100.NWRKNJ-VFTTP-125.verizon-gni.net [98.109.220.1]
> 3 5 ms 5 ms 7 ms 5-0-8-1725.NWRKNJ-LCR-07.verizon-gni.net [130.81.137.100]
> 4 7 ms 6 ms 8 ms so-5-0-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.29.8]
> 5 12 ms 12 ms 12 ms so-12-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.17.6]
> 6 111 ms 22 ms 10 ms 192.205.36.57
> 7 42 ms 41 ms 41 ms cr1.n54ny.ip.att.net [12.122.86.6]
> 8 41 ms 41 ms 41 ms cr1.phlpa.ip.att.net [12.122.5.242]
> 9 41 ms 41 ms 42 ms cr2.phlpa.ip.att.net [12.122.3.226]
> 10 43 ms 40 ms 41 ms cr2.cl2oh.ip.att.net [12.122.2.209]
> 11 42 ms 41 ms 40 ms cr1.cl2oh.ip.att.net [12.122.2.125]
> 12 42 ms 40 ms 41 ms cr2.nsvtn.ip.att.net [12.122.28.73]
> 13 41 ms 41 ms 42 ms gar1.nsvtn.ip.att.net [12.123.129.81]
> 14 39 ms 240 ms 120 ms 12.87.103.106
> 15 43 ms 41 ms 41 ms fios.asurion.com [12.191.160.39]
> 16 43 ms 42 ms 43 ms fios.asurion.com [12.191.160.39]
> 17 42 ms 42 ms 41 ms fios.asurion.com [12.191.160.39]
> 18 44 ms 41 ms 42 ms fios.asurion.com [12.191.160.39]
>
>
> --
> Dave
> http://www.claymania.com/removal-trojan-adware.html
> Multi-AV - http://www.pctipp.ch/downloads/dl/35905.asp
>

[Bob K]

On 4/13/2010 10:11 AM, Mark F wrote:
> I'm not sure if this is the proper group.
>
> I'm "Mark F", a Verizon FiOS user in ZIP 10502 (NY). I
> originally posted in alt.online-service.verizon, but it
> now seems more like a network issue.
>
> The problem is that I can't get to fios.asurion.com but many
> other people can. I think that the problem is at ATT, but I'm
> not sure.
>
> Note that I get to 12.123.129.81 and can't get further, while
> "Dave" gets to the same node and continue past and get reach
> the desired node.
>
> Some else thought that the problem was that 74.*.*.* wasn't known
> everywhere or that my IP itself (in 106.*.*.*) was
> not known.
>
> Thank you for any help you can give me.
>> From: "Mark F"<mark53916@gmail.com>
>>
>>
>>
>>>> Tracing route to fios.asurion.com [12.191.160.39]
>>>> over a maximum of 30 hops:
>>
>>>> 1<1 ms<1 ms<1 ms Wireless_Broadband_Router.home [192.168.1.1]
>>>> 2 6 ms 34 ms 34 ms 74.101.54.1
>>>> 3 8 ms 6 ms 7 ms 11-0-1-1253.NYCMNY-LCR-12.verizon-gni.net
>>>> [130.81.139.36]
>>>> 4 18 ms 7 ms 6 ms so-6-2-0-0.NY5030-BB-RTR1.verizon-gni.net
>>>> [130.81.29.14]
>>>> 5 9 ms 9 ms 10 ms 0.so-3-1-0.XT1.NYC8.ALTER.NET [152.63.10.33]
>>>> 6 9 ms 9 ms 10 ms 0.so-6-0-0.XL3.NYC4.ALTER.NET [152.63.16.221]
>>>> 7 9 ms 10 ms 9 ms 0.xe-3-2-0.BR2.NYC4.ALTER.NET [152.63.3.126]
>>>> 8 10 ms 12 ms 9 ms 192.205.36.57
>>>> 9 38 ms 36 ms 39 ms cr1.n54ny.ip.att.net [12.122.86.6]
>>>> 10 34 ms 34 ms 34 ms cr1.phlpa.ip.att.net [12.122.5.242]
>>>> 11 37 ms 37 ms 37 ms cr2.phlpa.ip.att.net [12.122.3.226]
>>>> 12 40 ms 39 ms 39 ms cr2.cl2oh.ip.att.net [12.122.2.209]
>>>> 13 38 ms 39 ms 39 ms cr1.cl2oh.ip.att.net [12.122.2.125]
>>>> 14 38 ms 39 ms 39 ms cr2.nsvtn.ip.att.net [12.122.28.73]
>>>> 15 40 ms 39 ms 39 ms gar1.nsvtn.ip.att.net [12.123.129.81]
>>>> 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.
>>
>> | Who someone who can get to fios.asurion.com try it and post their
>> | results please?
> Dave speaking below:
>>
>> C:\1>tracert fios.asurion.com
>>
>> Tracing route to fios.asurion.com [12.191.160.39]
>> over a maximum of 30 hops:
>>
>> 1<1 ms<1 ms<1 ms 192.168.1.1
>> 2 5 ms 3 ms 4 ms L100.NWRKNJ-VFTTP-125.verizon-gni.net [98.109.220.1]
>> 3 5 ms 5 ms 7 ms 5-0-8-1725.NWRKNJ-LCR-07.verizon-gni.net [130.81.137.100]
>> 4 7 ms 6 ms 8 ms so-5-0-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.29.8]
>> 5 12 ms 12 ms 12 ms so-12-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.17.6]
>> 6 111 ms 22 ms 10 ms 192.205.36.57
>> 7 42 ms 41 ms 41 ms cr1.n54ny.ip.att.net [12.122.86.6]
>> 8 41 ms 41 ms 41 ms cr1.phlpa.ip.att.net [12.122.5.242]
>> 9 41 ms 41 ms 42 ms cr2.phlpa.ip.att.net [12.122.3.226]
>> 10 43 ms 40 ms 41 ms cr2.cl2oh.ip.att.net [12.122.2.209]
>> 11 42 ms 41 ms 40 ms cr1.cl2oh.ip.att.net [12.122.2.125]
>> 12 42 ms 40 ms 41 ms cr2.nsvtn.ip.att.net [12.122.28.73]
>> 13 41 ms 41 ms 42 ms gar1.nsvtn.ip.att.net [12.123.129.81]
>> 14 39 ms 240 ms 120 ms 12.87.103.106
>> 15 43 ms 41 ms 41 ms fios.asurion.com [12.191.160.39]
>> 16 43 ms 42 ms 43 ms fios.asurion.com [12.191.160.39]
>> 17 42 ms 42 ms 41 ms fios.asurion.com [12.191.160.39]
>> 18 44 ms 41 ms 42 ms fios.asurion.com [12.191.160.39]
>>
>>
>> --
>> Dave
>> http://www.claymania.com/removal-trojan-adware.html
>> Multi-AV - http://www.pctipp.ch/downloads/dl/35905.asp
>>

I just did a tracert, and it went OK. This is what I got:

Tracing route to fios.asurion.com [12.191.160.39]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.100.1
2 48 ms 49 ms 126 ms
70-100-128-1.dsl1-fairport.roc.ny.frontiernet.net [70.100.128.1]
3 48 ms 48 ms 47 ms vlan40.br2.roch.ny.frontiernet.net
[74.44.233.19]
4 114 ms 47 ms 47 ms ge-3-1--0.ar04.roch.ny.frontiernet.net
[65.73.205.5]
5 49 ms 48 ms 48 ms
ge--2-0-0---0.cor01.roch.ny.frontiernet.net [74.40.3.205]
6 63 ms 61 ms 61 ms
xe-0-0-0--0.cor02.asbn.va.frontiernet.net [74.40.5.18]
7 60 ms 60 ms 61 ms
xe-11-0-0--0.cbr01.asbn.va.frontiernet.net [74.40.2.178]
8 63 ms 63 ms 62 ms 12.118.132.33
9 86 ms 86 ms 86 ms cr1.wswdc.ip.att.net [12.122.135.70]
10 91 ms 86 ms 85 ms cr2.phlpa.ip.att.net [12.122.4.53]
11 86 ms 86 ms 86 ms cr2.cl2oh.ip.att.net [12.122.2.209]
12 87 ms 86 ms 85 ms cr1.cl2oh.ip.att.net [12.122.2.125]
13 193 ms 86 ms 86 ms cr2.nsvtn.ip.att.net [12.122.28.73]
14 95 ms 98 ms 96 ms gar1.nsvtn.ip.att.net [12.123.129.81]
15 85 ms 90 ms 88 ms 12.87.103.106
16 85 ms 87 ms 87 ms fios.asurion.com [12.191.160.39]
17 86 ms 87 ms 86 ms fios.asurion.com [12.191.160.39]
18 87 ms 170 ms 86 ms fios.asurion.com [12.191.160.39]
19 87 ms 86 ms 88 ms fios.asurion.com [12.191.160.39]
Trace complete.

This seems to agree with what Dave got.

Have you tried a ping to fios.asurion.com? (I was able to.) That might
give you something to go on. Somewhere, I had heard that there are
different ways that tracert can be run. Some sites don't respond to
ping commands, and there were some work-arounds for that.

I don't know if the DNS servers get involved with every step in a
tracert. The site your tracert times out at (step 14 in Dave's) doesn't
have a URL associated with it. Have you tried using different DNS
servers to see if that might be a problem?

Obviously, whatever your DNS server is, it does resolve the
fios.asurion.com OK.

I don't see where your ip (in 106.*.*.*) should be a problem, unless the
site at 12.87.103.106 has that blacklisted for some reason.

....Bob

[Bob K]

On 4/13/2010 11:00 AM, Bob K wrote:
<snipped>
> I don't know if the DNS servers get involved with every step in a
> tracert. The site your tracert times out at (step 14 in Dave's) doesn't
> have a URL associated with it. Have you tried using different DNS
> servers to see if that might be a problem?
>
> Obviously, whatever your DNS server is, it does resolve the
> fios.asurion.com OK.
>

> ...Bob
>
>
To add to my own comments...

Here are the DNS servers I use:
8.8.8.8
and
4.2.2.4

Both are, the last I checked, public DNS servers, and using them gets
around some of the games an ISP may play with some of DNS lookups.

....Bob

[Mark F]

(New comment at end)
On Tue, 13 Apr 2010 11:00:28 -0400, Bob K <SPAMpot@Frontiernet.net>
wrote:

> On 4/13/2010 10:11 AM, Mark F wrote:
> > I'm not sure if this is the proper group.
> >
> > I'm "Mark F", a Verizon FiOS user in ZIP 10502 (NY). I
> > originally posted in alt.online-service.verizon, but it
> > now seems more like a network issue.
> >
> > The problem is that I can't get to fios.asurion.com but many
> > other people can. I think that the problem is at ATT, but I'm
> > not sure.
> >
> > Note that I get to 12.123.129.81 and can't get further, while
> > "Dave" gets to the same node and continue past and get reach
> > the desired node.
> >
> > Some else thought that the problem was that 74.*.*.* wasn't known
> > everywhere or that my IP itself (in 106.*.*.*) was
> > not known.
> >
> > Thank you for any help you can give me.
> >> From: "Mark F"<mark53916@gmail.com>
> >>
> >>
> >>
> >>>> Tracing route to fios.asurion.com [12.191.160.39]
> >>>> over a maximum of 30 hops:
> >>
> >>>> 1<1 ms<1 ms<1 ms Wireless_Broadband_Router.home [192.168.1.1]
> >>>> 2 6 ms 34 ms 34 ms 74.101.54.1
> >>>> 3 8 ms 6 ms 7 ms 11-0-1-1253.NYCMNY-LCR-12.verizon-gni.net
> >>>> [130.81.139.36]
> >>>> 4 18 ms 7 ms 6 ms so-6-2-0-0.NY5030-BB-RTR1.verizon-gni.net
> >>>> [130.81.29.14]
> >>>> 5 9 ms 9 ms 10 ms 0.so-3-1-0.XT1.NYC8.ALTER.NET [152.63.10.33]
> >>>> 6 9 ms 9 ms 10 ms 0.so-6-0-0.XL3.NYC4.ALTER.NET [152.63.16.221]
> >>>> 7 9 ms 10 ms 9 ms 0.xe-3-2-0.BR2.NYC4.ALTER.NET [152.63.3.126]
> >>>> 8 10 ms 12 ms 9 ms 192.205.36.57
> >>>> 9 38 ms 36 ms 39 ms cr1.n54ny.ip.att.net [12.122.86.6]
> >>>> 10 34 ms 34 ms 34 ms cr1.phlpa.ip.att.net [12.122.5.242]
> >>>> 11 37 ms 37 ms 37 ms cr2.phlpa.ip.att.net [12.122.3.226]
> >>>> 12 40 ms 39 ms 39 ms cr2.cl2oh.ip.att.net [12.122.2.209]
> >>>> 13 38 ms 39 ms 39 ms cr1.cl2oh.ip.att.net [12.122.2.125]
> >>>> 14 38 ms 39 ms 39 ms cr2.nsvtn.ip.att.net [12.122.28.73]
> >>>> 15 40 ms 39 ms 39 ms gar1.nsvtn.ip.att.net [12.123.129.81]
> >>>> 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.
> >>
> >> | Who someone who can get to fios.asurion.com try it and post their
> >> | results please?
> > Dave speaking below:
> >>
> >> C:\1>tracert fios.asurion.com
> >>
> >> Tracing route to fios.asurion.com [12.191.160.39]
> >> over a maximum of 30 hops:
> >>
> >> 1<1 ms<1 ms<1 ms 192.168.1.1
> >> 2 5 ms 3 ms 4 ms L100.NWRKNJ-VFTTP-125.verizon-gni.net [98.109.220.1]
> >> 3 5 ms 5 ms 7 ms 5-0-8-1725.NWRKNJ-LCR-07.verizon-gni.net [130.81.137.100]
> >> 4 7 ms 6 ms 8 ms so-5-0-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.29.8]
> >> 5 12 ms 12 ms 12 ms so-12-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.17.6]
> >> 6 111 ms 22 ms 10 ms 192.205.36.57
> >> 7 42 ms 41 ms 41 ms cr1.n54ny.ip.att.net [12.122.86.6]
> >> 8 41 ms 41 ms 41 ms cr1.phlpa.ip.att.net [12.122.5.242]
> >> 9 41 ms 41 ms 42 ms cr2.phlpa.ip.att.net [12.122.3.226]
> >> 10 43 ms 40 ms 41 ms cr2.cl2oh.ip.att.net [12.122.2.209]
> >> 11 42 ms 41 ms 40 ms cr1.cl2oh.ip.att.net [12.122.2.125]
> >> 12 42 ms 40 ms 41 ms cr2.nsvtn.ip.att.net [12.122.28.73]
> >> 13 41 ms 41 ms 42 ms gar1.nsvtn.ip.att.net [12.123.129.81]
> >> 14 39 ms 240 ms 120 ms 12.87.103.106
> >> 15 43 ms 41 ms 41 ms fios.asurion.com [12.191.160.39]
> >> 16 43 ms 42 ms 43 ms fios.asurion.com [12.191.160.39]
> >> 17 42 ms 42 ms 41 ms fios.asurion.com [12.191.160.39]
> >> 18 44 ms 41 ms 42 ms fios.asurion.com [12.191.160.39]
> >>
> >>
> >> --
> >> Dave
> >> http://www.claymania.com/removal-trojan-adware.html
> >> Multi-AV - http://www.pctipp.ch/downloads/dl/35905.asp
> >>
>
> I just did a tracert, and it went OK. This is what I got:
>
> Tracing route to fios.asurion.com [12.191.160.39]
> over a maximum of 30 hops:
> 1 <1 ms <1 ms <1 ms 192.168.100.1
> 2 48 ms 49 ms 126 ms
> 70-100-128-1.dsl1-fairport.roc.ny.frontiernet.net [70.100.128.1]
> 3 48 ms 48 ms 47 ms vlan40.br2.roch.ny.frontiernet.net
> [74.44.233.19]
> 4 114 ms 47 ms 47 ms ge-3-1--0.ar04.roch.ny.frontiernet.net
> [65.73.205.5]
> 5 49 ms 48 ms 48 ms
> ge--2-0-0---0.cor01.roch.ny.frontiernet.net [74.40.3.205]
> 6 63 ms 61 ms 61 ms
> xe-0-0-0--0.cor02.asbn.va.frontiernet.net [74.40.5.18]
> 7 60 ms 60 ms 61 ms
> xe-11-0-0--0.cbr01.asbn.va.frontiernet.net [74.40.2.178]
> 8 63 ms 63 ms 62 ms 12.118.132.33
> 9 86 ms 86 ms 86 ms cr1.wswdc.ip.att.net [12.122.135.70]
> 10 91 ms 86 ms 85 ms cr2.phlpa.ip.att.net [12.122.4.53]
> 11 86 ms 86 ms 86 ms cr2.cl2oh.ip.att.net [12.122.2.209]
> 12 87 ms 86 ms 85 ms cr1.cl2oh.ip.att.net [12.122.2.125]
> 13 193 ms 86 ms 86 ms cr2.nsvtn.ip.att.net [12.122.28.73]
> 14 95 ms 98 ms 96 ms gar1.nsvtn.ip.att.net [12.123.129.81]
> 15 85 ms 90 ms 88 ms 12.87.103.106
> 16 85 ms 87 ms 87 ms fios.asurion.com [12.191.160.39]
> 17 86 ms 87 ms 86 ms fios.asurion.com [12.191.160.39]
> 18 87 ms 170 ms 86 ms fios.asurion.com [12.191.160.39]
> 19 87 ms 86 ms 88 ms fios.asurion.com [12.191.160.39]
> Trace complete.
>
> This seems to agree with what Dave got.
>
> Have you tried a ping to fios.asurion.com? (I was able to.) That might
> give you something to go on. Somewhere, I had heard that there are
> different ways that tracert can be run. Some sites don't respond to
> ping commands, and there were some work-arounds for that.
>
> I don't know if the DNS servers get involved with every step in a
> tracert. The site your tracert times out at (step 14 in Dave's) doesn't
> have a URL associated with it. Have you tried using different DNS
> servers to see if that might be a problem?
>
> Obviously, whatever your DNS server is, it does resolve the
> fios.asurion.com OK.
>
> I don't see where your ip (in 106.*.*.*) should be a problem, unless the
> site at 12.87.103.106 has that blacklisted for some reason.
>
> ...Bob
Verizon has fixed the symptom of me not being able to reach a
particular IP address, but I'm not sure that they fixed the actual
problem.

Verizon called me to say they thought the fixed the problem by
"rebuilding" my account.

Since I thought that "rebuilding" my account would not fix the
underlying problem which might be due to a procedural error that
might effect more than one user or more than one IP address and that
new symptums would happen to other users, I asked the person
who called to do a tracert.

They refused to do a tracert from their system, even when I said that
they didn't have to tell me the results if they thought that would be
a security issue.

When I told them that I was concerned that there were many problems
that I could not know about because software beyond my control
automatically went to a lower quality alternate site when it detected
an unreachable node the Verizon person didn't understand how that
would be a problem and said that they only would attempt to fix
problems with reaching specific URL's.

If someone with a Verizon FiOS account is willing, they might
call and say they were having a problem reaching fios.asurion.com and
ask if anyone else has reported the problem. Then please report back
and tell us if they say someone else reported the problem (truth) or
no one else has reported the problem (lie.)

Thanks.

By the way, none of the 5 or more Verizon people that I spoke to
understood that the return paths used by tracert but not displayed
might not match the forward paths that are displayed, and that a
broken backward path for normal browser access (as contrasted with
a broken backward path for tracert alone) could lead to the
original symptom. (The possible PROBLEM, as contrasted with the
symptom of not being able to read a URL or IP address, is that
Verizon doesn't propagate changes correctly or another ISP is not
properly integrating knowledge of Verizon's changes.)


Here is the new tracert result:
> Microsoft Windows XP [Version 5.1.2600]
> (C) Copyright 1985-2001 Microsoft Corp.
>
> C:\Documents and Settings\mfineman>tracert fios.asurion.com
>
> Tracing route to fios.asurion.com [12.191.160.39]
> over a maximum of 30 hops:
>
> 1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
> 2 8 ms 6 ms 7 ms 74.101.54.1
> 3 8 ms 9 ms 10 ms 11-0-1-1153.NYCMNY-LCR-11.verizon-gni.net [130.8
> 1.137.30]
> 4 11 ms 10 ms 9 ms so-2-1-0-0.NY325-BB-RTR1.verizon-gni.net [130.81
> .29.12]
> 5 9 ms 9 ms 9 ms 0.xe-1-2-0.BR2.NYC4.ALTER.NET [152.63.18.37]
> 6 10 ms 9 ms 10 ms 192.205.34.49
> 7 37 ms 36 ms 37 ms cr1.n54ny.ip.att.net [12.122.86.6]
> 8 37 ms 37 ms 36 ms cr1.phlpa.ip.att.net [12.122.5.242]
> 9 39 ms 37 ms 37 ms cr2.phlpa.ip.att.net [12.122.3.226]
> 10 37 ms 36 ms 37 ms cr2.cl2oh.ip.att.net [12.122.2.209]
> 11 37 ms 36 ms 37 ms cr1.cl2oh.ip.att.net [12.122.2.125]
> 12 38 ms 36 ms 37 ms cr2.nsvtn.ip.att.net [12.122.28.73]
> 13 35 ms 35 ms 34 ms gar1.nsvtn.ip.att.net [12.123.129.81]
> 14 43 ms 39 ms 39 ms 12.87.103.106
> 15 42 ms 39 ms 39 ms fios.asurion.com [12.191.160.39]
> 16 39 ms 39 ms 42 ms fios.asurion.com [12.191.160.39]
> 17 57 ms 39 ms 39 ms fios.asurion.com [12.191.160.39]
> 18 37 ms 37 ms 37 ms fios.asurion.com [12.191.160.39]
>
> Trace complete.

[Bob K]

On 4/23/2010 10:16 AM, Mark F wrote:
> (New comment at end)
> On Tue, 13 Apr 2010 11:00:28 -0400, Bob K<SPAMpot@Frontiernet.net>
> wrote:
>
>> On 4/13/2010 10:11 AM, Mark F wrote:
>>> I'm not sure if this is the proper group.
>>>
>>> I'm "Mark F", a Verizon FiOS user in ZIP 10502 (NY). I
>>> originally posted in alt.online-service.verizon, but it
>>> now seems more like a network issue.
>>>
>>> The problem is that I can't get to fios.asurion.com but many
>>> other people can. I think that the problem is at ATT, but I'm
>>> not sure.
>>>
>>> Note that I get to 12.123.129.81 and can't get further, while
>>> "Dave" gets to the same node and continue past and get reach
>>> the desired node.
>>>
>>> Some else thought that the problem was that 74.*.*.* wasn't known
>>> everywhere or that my IP itself (in 106.*.*.*) was
>>> not known.
>>>
>>> Thank you for any help you can give me.
>>>> From: "Mark F"<mark53916@gmail.com>
>>>>
>>>>
>>>>
>>>>>> Tracing route to fios.asurion.com [12.191.160.39]
>>>>>> over a maximum of 30 hops:
>>>>
>>>>>> 1<1 ms<1 ms<1 ms Wireless_Broadband_Router.home [192.168.1.1]
>>>>>> 2 6 ms 34 ms 34 ms 74.101.54.1
>>>>>> 3 8 ms 6 ms 7 ms 11-0-1-1253.NYCMNY-LCR-12.verizon-gni.net
>>>>>> [130.81.139.36]
>>>>>> 4 18 ms 7 ms 6 ms so-6-2-0-0.NY5030-BB-RTR1.verizon-gni.net
>>>>>> [130.81.29.14]
>>>>>> 5 9 ms 9 ms 10 ms 0.so-3-1-0.XT1.NYC8.ALTER.NET [152.63.10.33]
>>>>>> 6 9 ms 9 ms 10 ms 0.so-6-0-0.XL3.NYC4.ALTER.NET [152.63.16.221]
>>>>>> 7 9 ms 10 ms 9 ms 0.xe-3-2-0.BR2.NYC4.ALTER.NET [152.63.3.126]
>>>>>> 8 10 ms 12 ms 9 ms 192.205.36.57
>>>>>> 9 38 ms 36 ms 39 ms cr1.n54ny.ip.att.net [12.122.86.6]
>>>>>> 10 34 ms 34 ms 34 ms cr1.phlpa.ip.att.net [12.122.5.242]
>>>>>> 11 37 ms 37 ms 37 ms cr2.phlpa.ip.att.net [12.122.3.226]
>>>>>> 12 40 ms 39 ms 39 ms cr2.cl2oh.ip.att.net [12.122.2.209]
>>>>>> 13 38 ms 39 ms 39 ms cr1.cl2oh.ip.att.net [12.122.2.125]
>>>>>> 14 38 ms 39 ms 39 ms cr2.nsvtn.ip.att.net [12.122.28.73]
>>>>>> 15 40 ms 39 ms 39 ms gar1.nsvtn.ip.att.net [12.123.129.81]
>>>>>> 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.
>>>>
>>>> | Who someone who can get to fios.asurion.com try it and post their
>>>> | results please?
>>> Dave speaking below:
>>>>
>>>> C:\1>tracert fios.asurion.com
>>>>
>>>> Tracing route to fios.asurion.com [12.191.160.39]
>>>> over a maximum of 30 hops:
>>>>
>>>> 1<1 ms<1 ms<1 ms 192.168.1.1
>>>> 2 5 ms 3 ms 4 ms L100.NWRKNJ-VFTTP-125.verizon-gni.net [98.109.220.1]
>>>> 3 5 ms 5 ms 7 ms 5-0-8-1725.NWRKNJ-LCR-07.verizon-gni.net [130.81.137.100]
>>>> 4 7 ms 6 ms 8 ms so-5-0-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.29.8]
>>>> 5 12 ms 12 ms 12 ms so-12-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.17.6]
>>>> 6 111 ms 22 ms 10 ms 192.205.36.57
>>>> 7 42 ms 41 ms 41 ms cr1.n54ny.ip.att.net [12.122.86.6]
>>>> 8 41 ms 41 ms 41 ms cr1.phlpa.ip.att.net [12.122.5.242]
>>>> 9 41 ms 41 ms 42 ms cr2.phlpa.ip.att.net [12.122.3.226]
>>>> 10 43 ms 40 ms 41 ms cr2.cl2oh.ip.att.net [12.122.2.209]
>>>> 11 42 ms 41 ms 40 ms cr1.cl2oh.ip.att.net [12.122.2.125]
>>>> 12 42 ms 40 ms 41 ms cr2.nsvtn.ip.att.net [12.122.28.73]
>>>> 13 41 ms 41 ms 42 ms gar1.nsvtn.ip.att.net [12.123.129.81]
>>>> 14 39 ms 240 ms 120 ms 12.87.103.106
>>>> 15 43 ms 41 ms 41 ms fios.asurion.com [12.191.160.39]
>>>> 16 43 ms 42 ms 43 ms fios.asurion.com [12.191.160.39]
>>>> 17 42 ms 42 ms 41 ms fios.asurion.com [12.191.160.39]
>>>> 18 44 ms 41 ms 42 ms fios.asurion.com [12.191.160.39]
>>>>
>>>>
>>>> --
>>>> Dave
>>>> http://www.claymania.com/removal-trojan-adware.html
>>>> Multi-AV - http://www.pctipp.ch/downloads/dl/35905.asp
>>>>
>>
>> I just did a tracert, and it went OK. This is what I got:
>>
>> Tracing route to fios.asurion.com [12.191.160.39]
>> over a maximum of 30 hops:
>> 1<1 ms<1 ms<1 ms 192.168.100.1
>> 2 48 ms 49 ms 126 ms
>> 70-100-128-1.dsl1-fairport.roc.ny.frontiernet.net [70.100.128.1]
>> 3 48 ms 48 ms 47 ms vlan40.br2.roch.ny.frontiernet.net
>> [74.44.233.19]
>> 4 114 ms 47 ms 47 ms ge-3-1--0.ar04.roch.ny.frontiernet.net
>> [65.73.205.5]
>> 5 49 ms 48 ms 48 ms
>> ge--2-0-0---0.cor01.roch.ny.frontiernet.net [74.40.3.205]
>> 6 63 ms 61 ms 61 ms
>> xe-0-0-0--0.cor02.asbn.va.frontiernet.net [74.40.5.18]
>> 7 60 ms 60 ms 61 ms
>> xe-11-0-0--0.cbr01.asbn.va.frontiernet.net [74.40.2.178]
>> 8 63 ms 63 ms 62 ms 12.118.132.33
>> 9 86 ms 86 ms 86 ms cr1.wswdc.ip.att.net [12.122.135.70]
>> 10 91 ms 86 ms 85 ms cr2.phlpa.ip.att.net [12.122.4.53]
>> 11 86 ms 86 ms 86 ms cr2.cl2oh.ip.att.net [12.122.2.209]
>> 12 87 ms 86 ms 85 ms cr1.cl2oh.ip.att.net [12.122.2.125]
>> 13 193 ms 86 ms 86 ms cr2.nsvtn.ip.att.net [12.122.28.73]
>> 14 95 ms 98 ms 96 ms gar1.nsvtn.ip.att.net [12.123.129.81]
>> 15 85 ms 90 ms 88 ms 12.87.103.106
>> 16 85 ms 87 ms 87 ms fios.asurion.com [12.191.160.39]
>> 17 86 ms 87 ms 86 ms fios.asurion.com [12.191.160.39]
>> 18 87 ms 170 ms 86 ms fios.asurion.com [12.191.160.39]
>> 19 87 ms 86 ms 88 ms fios.asurion.com [12.191.160.39]
>> Trace complete.
>>
>> This seems to agree with what Dave got.
>>
>> Have you tried a ping to fios.asurion.com? (I was able to.) That might
>> give you something to go on. Somewhere, I had heard that there are
>> different ways that tracert can be run. Some sites don't respond to
>> ping commands, and there were some work-arounds for that.
>>
>> I don't know if the DNS servers get involved with every step in a
>> tracert. The site your tracert times out at (step 14 in Dave's) doesn't
>> have a URL associated with it. Have you tried using different DNS
>> servers to see if that might be a problem?
>>
>> Obviously, whatever your DNS server is, it does resolve the
>> fios.asurion.com OK.
>>
>> I don't see where your ip (in 106.*.*.*) should be a problem, unless the
>> site at 12.87.103.106 has that blacklisted for some reason.
>>
>> ...Bob
> Verizon has fixed the symptom of me not being able to reach a
> particular IP address, but I'm not sure that they fixed the actual
> problem.
>
> Verizon called me to say they thought the fixed the problem by
> "rebuilding" my account.
>
> Since I thought that "rebuilding" my account would not fix the
> underlying problem which might be due to a procedural error that
> might effect more than one user or more than one IP address and that
> new symptums would happen to other users, I asked the person
> who called to do a tracert.
>
> They refused to do a tracert from their system, even when I said that
> they didn't have to tell me the results if they thought that would be
> a security issue.
>
> When I told them that I was concerned that there were many problems
> that I could not know about because software beyond my control
> automatically went to a lower quality alternate site when it detected
> an unreachable node the Verizon person didn't understand how that
> would be a problem and said that they only would attempt to fix
> problems with reaching specific URL's.
>
> If someone with a Verizon FiOS account is willing, they might
> call and say they were having a problem reaching fios.asurion.com and
> ask if anyone else has reported the problem. Then please report back
> and tell us if they say someone else reported the problem (truth) or
> no one else has reported the problem (lie.)
>
> Thanks.
>
> By the way, none of the 5 or more Verizon people that I spoke to
> understood that the return paths used by tracert but not displayed
> might not match the forward paths that are displayed, and that a
> broken backward path for normal browser access (as contrasted with
> a broken backward path for tracert alone) could lead to the
> original symptom. (The possible PROBLEM, as contrasted with the
> symptom of not being able to read a URL or IP address, is that
> Verizon doesn't propagate changes correctly or another ISP is not
> properly integrating knowledge of Verizon's changes.)
>
>
> Here is the new tracert result:
>> Microsoft Windows XP [Version 5.1.2600]
>> (C) Copyright 1985-2001 Microsoft Corp.
>>
>> C:\Documents and Settings\mfineman>tracert fios.asurion.com
>>
>> Tracing route to fios.asurion.com [12.191.160.39]
>> over a maximum of 30 hops:
>>
>> 1<1 ms<1 ms<1 ms Wireless_Broadband_Router.home [192.168.1.1]
>> 2 8 ms 6 ms 7 ms 74.101.54.1
>> 3 8 ms 9 ms 10 ms 11-0-1-1153.NYCMNY-LCR-11.verizon-gni.net [130.8
>> 1.137.30]
>> 4 11 ms 10 ms 9 ms so-2-1-0-0.NY325-BB-RTR1.verizon-gni.net [130.81
>> .29.12]
>> 5 9 ms 9 ms 9 ms 0.xe-1-2-0.BR2.NYC4.ALTER.NET [152.63.18.37]
>> 6 10 ms 9 ms 10 ms 192.205.34.49
>> 7 37 ms 36 ms 37 ms cr1.n54ny.ip.att.net [12.122.86.6]
>> 8 37 ms 37 ms 36 ms cr1.phlpa.ip.att.net [12.122.5.242]
>> 9 39 ms 37 ms 37 ms cr2.phlpa.ip.att.net [12.122.3.226]
>> 10 37 ms 36 ms 37 ms cr2.cl2oh.ip.att.net [12.122.2.209]
>> 11 37 ms 36 ms 37 ms cr1.cl2oh.ip.att.net [12.122.2.125]
>> 12 38 ms 36 ms 37 ms cr2.nsvtn.ip.att.net [12.122.28.73]
>> 13 35 ms 35 ms 34 ms gar1.nsvtn.ip.att.net [12.123.129.81]
>> 14 43 ms 39 ms 39 ms 12.87.103.106
>> 15 42 ms 39 ms 39 ms fios.asurion.com [12.191.160.39]
>> 16 39 ms 39 ms 42 ms fios.asurion.com [12.191.160.39]
>> 17 57 ms 39 ms 39 ms fios.asurion.com [12.191.160.39]
>> 18 37 ms 37 ms 37 ms fios.asurion.com [12.191.160.39]
>>
>> Trace complete.
>

Well, to add to the confusion, I just did another tracert, and got
different results from what I did earlier (still included above). This
time:

Tracing route to fios.asurion.com [12.191.160.39]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.100.1
2 47 ms 47 ms 47 ms
70-100-128-1.dsl1-fairport.roc.ny.frontiernet.net [70.100.128.1]
3 48 ms 48 ms 47 ms vlan40.br2.roch.ny.frontiernet.net
[74.44.233.19]
4 47 ms 47 ms 47 ms ge-3-1--0.ar04.roch.ny.frontiernet.net
[65.73.205.5]
5 58 ms 52 ms 47 ms
ge--2-0-0---0.cor01.roch.ny.frontiernet.net [74.40.3.205]
6 62 ms 76 ms 61 ms
xe-0-0-0--0.cor02.asbn.va.frontiernet.net [74.40.5.18]
7 64 ms 61 ms 61 ms
xe-11-0-0--0.cbr01.asbn.va.frontiernet.net [74.40.2.178]
8 61 ms 61 ms 61 ms xe-6-1-0.edge2.Washington4.Level3.net
[4.53.114.69]
9 62 ms 62 ms 62 ms ae-4-99.edge1.Washington4.Level3.net
[4.68.17.210]
10 64 ms 63 ms 82 ms 4.68.62.26
11 86 ms 191 ms 87 ms cr1.wswdc.ip.att.net [12.122.88.174]
12 86 ms 88 ms 86 ms cr2.phlpa.ip.att.net [12.122.4.53]
13 86 ms 86 ms 85 ms cr2.cl2oh.ip.att.net [12.122.2.209]
14 86 ms 86 ms 87 ms cr1.cl2oh.ip.att.net [12.122.2.125]
15 86 ms 86 ms 88 ms cr2.nsvtn.ip.att.net [12.122.28.73]
16 84 ms 86 ms 85 ms gar1.nsvtn.ip.att.net [12.123.129.81]
17 86 ms 87 ms 87 ms 12.87.103.106
18 86 ms 137 ms 85 ms fios.asurion.com [12.191.160.39]
19 85 ms 85 ms 86 ms fios.asurion.com [12.191.160.39]
20 88 ms 86 ms 85 ms fios.asurion.com [12.191.160.39]
21 86 ms 86 ms 86 ms fios.asurion.com [12.191.160.39]

Trace complete.

And, I don't understand the redundant IP addresses for the last four
hits shown in all the successful traces.

I suspect there are some errors in the DNS lookups, and possibly what
DNS servers a user is looking at may influence what path is is taken.

....Bob