Boy, when it rains, it pours, for me...
There's a website we are contractually required to use for some reporting
purposes. We can't access it. Firefox reports that it is connected to the
site and waiting for data, and then it gives the "connection was reset"
message.
Our internet connection is working fine and we can get to any other website
we try.
The website itself is up; it can be reached from our location using another
ISP, such as a cell phone broadband connection, or from my home computer
which is about 12 miles away from here.
This website was reachable from our internet connection until sometime
yesterday afternoon, at which time one other person, in a different part of
the building, reported some temporary general connectivity problems. As a
precaution, we rebooted the router that supplies internet to our network.
This did not affect the problem.
Below is a tracert to the problem website, which is hosted by a provider
near Albany, NY. We've done this tracert from several different computers
in this building, at different times, and we get identical results. I see
two anomalies in it that I don't understand. (However, I see similar
anomalies in a tracert to our own website, which is accessible, and hosted
by a different provider, also near Albany, NY). That tracert is also
provided below.
Anomaly 1:
Why do we hop back from the ISP network to an address that would allegedly
be on my private network in hop 3 (except that I have assigned nothing to
that address and we don't even use that range for anything, although we do
have a Class A network)?
Anomaly 2: What is the significance of the timeout at hop 5? (TWTelelcom is
our provider; it was recently bought out by Level 3. So there is a timeout
between segments of our provider's network, but as shown in the second
tracert, two such timeouts in a row don't actually prevent a connection to
our website.)
PROBLEM WEBSITE
Tracing route to 173-198-192-106.static.as40244.net [173.198.192.106]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.1.9.200
2 <1 ms <1 ms <1 ms 64-129-187-97.static.twtelecom.net
[64.129.187.97]
3 1 ms 3 ms 1 ms 10.208.121.21
4 9 ms 9 ms 8 ms nyc2-pr2-xe-0-3-0-0.us.twtelecom.net
[66.192.242.253]
5 * * * Request timed out.
6 9 ms 15 ms 9 ms Cogent-level3-50G.NewYork1.Level3.net
[4.68.62.26]
7 10 ms 11 ms 10 ms be2061.ccr42.jfk02.atlas.cogentco.com
[154.54.3.69]
8 13 ms 18 ms 13 ms be2107.ccr22.alb02.atlas.cogentco.com
[154.54.3.94]
9 12 ms 12 ms 12 ms xe-2-3-0.edge1.ny01.as40244.net
[38.104.52.90]
10 13 ms 13 ms 13 ms te-1-0-1.corea.ny01.as40244.net [66.206.33.4]
11 16 ms 13 ms 14 ms xe-1-0-1.core110.ny01.as40244.net
[66.206.33.92]
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.
WORKING WEBSITE HOSTED BY DIFFERENT PROVIDER, SAME GEOGRAPHIC AREA.
Tracing route to cp-vps0.albyny.inoc.net [64.22.33.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.1.9.200
2 1 ms 1 ms <1 ms 64-129-187-97.static.twtelecom.net
[64.129.187.97]
3 2 ms <1 ms 1 ms 10.208.121.21
4 9 ms 8 ms 9 ms nyc2-pr2-xe-0-3-0-0.us.twtelecom.net
[66.192.242.253]
5 * * * Request timed out.
6 * * * Request timed out.
7 12 ms 11 ms 12 ms INDEPENDENT.ear3.NewYork1.Level3.net
[4.28.130.18]
8 12 ms 12 ms 12 ms e4-8-0.csr0.alb1.inoc.net [64.246.130.10]
9 12 ms 12 ms 12 ms lagg0-40.fgc0.alb1.inoc.net [64.246.132.52]
10 12 ms 12 ms 12 ms cp-vps0.albyny.inoc.net [64.22.33.10]
Trace complete.
Ken Dibble
www.stic-cil.org
From [email protected] Thu Jul 9 09:53:55 2015
Return-Path: <[email protected]>
X-Original-To: [email protected]
Delivered-To: [email protected]
Received: from cdptpa-oedge-vip.email.rr.com
(cdptpa-outbound-snat.email.rr.com [107.14.166.228])
by mail.leafe.com (Postfix) with ESMTP id A97D0B87AE
for <[email protected]>; Thu, 9 Jul 2015 09:53:55 -0500 (CDT)
Authentication-Results: cdptpa-oedge01 [email protected];
auth=pass (LOGIN)
Received: from [64.129.187.98] ([64.129.187.98:2632] helo=PICARD.stny.rr.com)
by cdptpa-oedge01 (envelope-from <[email protected]>)
(ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTPA
id 98/CF-14233-30B8E955; Thu, 09 Jul 2015 14:53:55 +0000
Message-Id: <[email protected]>
X-Sender: [email protected]@POP-Server.stny.rr.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Thu, 09 Jul 2015 10:57:11 -0400
To: [email protected]
From: Ken Dibble <[email protected]>
Subject: [NF] Can't Access Specific Website
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Antivirus: avast! (VPS 150709-1, 07/09/2015), Outbound message
X-Antivirus-Status: Clean
X-RR-Connecting-IP: 107.14.168.118:2525
X-Cloudmark-Score: 0
X-Spambayes-Classification: unsure; 0.90
Boy, when it rains, it pours, for me...
There's a website we are contractually required to use for some reporting
purposes. We can't access it. Firefox reports that it is connected to the
site and waiting for data, and then it gives the "connection was reset"
message.
Our internet connection is working fine and we can get to any other website
we try.
The website itself is up; it can be reached from our location using another
ISP, such as a cell phone broadband connection, or from my home computer
which is about 12 miles away from here.
This website was reachable from our internet connection until sometime
yesterday afternoon, at which time one other person, in a different part of
the building, reported some temporary general connectivity problems. As a
precaution, we rebooted the router that supplies internet to our network.
This did not affect the problem.
Below is a tracert to the problem website, which is hosted by a provider
near Albany, NY. We've done this tracert from several different computers
in this building, at different times, and we get identical results. I see
two anomalies in it that I don't understand. (However, I see similar
anomalies in a tracert to our own website, which is accessible, and hosted
by a different provider, also near Albany, NY). That tracert is also
provided below.
Anomaly 1:
Why do we hop back from the ISP network to an address that would allegedly
be on my private network in hop 3 (except that I have assigned nothing to
that address and we don't even use that range for anything, although we do
have a Class A network)?
Anomaly 2: What is the significance of the timeout at hop 5? (TWTelelcom is
our provider; it was recently bought out by Level 3. So there is a timeout
between segments of our provider's network, but as shown in the second
tracert, two such timeouts in a row don't actually prevent a connection to
our website.)
PROBLEM WEBSITE
Tracing route to 173-198-192-106.static.as40244.net [173.198.192.106]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.1.9.200
2 <1 ms <1 ms <1 ms 64-129-187-97.static.twtelecom.net
[64.129.187.97]
3 1 ms 3 ms 1 ms 10.208.121.21
4 9 ms 9 ms 8 ms nyc2-pr2-xe-0-3-0-0.us.twtelecom.net
[66.192.242.253]
5 * * * Request timed out.
6 9 ms 15 ms 9 ms Cogent-level3-50G.NewYork1.Level3.net
[4.68.62.26]
7 10 ms 11 ms 10 ms be2061.ccr42.jfk02.atlas.cogentco.com
[154.54.3.69]
8 13 ms 18 ms 13 ms be2107.ccr22.alb02.atlas.cogentco.com
[154.54.3.94]
9 12 ms 12 ms 12 ms xe-2-3-0.edge1.ny01.as40244.net
[38.104.52.90]
10 13 ms 13 ms 13 ms te-1-0-1.corea.ny01.as40244.net [66.206.33.4]
11 16 ms 13 ms 14 ms xe-1-0-1.core110.ny01.as40244.net
[66.206.33.92]
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.
WORKING WEBSITE HOSTED BY DIFFERENT PROVIDER, SAME GEOGRAPHIC AREA.
Tracing route to cp-vps0.albyny.inoc.net [64.22.33.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.1.9.200
2 1 ms 1 ms <1 ms 64-129-187-97.static.twtelecom.net
[64.129.187.97]
3 2 ms <1 ms 1 ms 10.208.121.21
4 9 ms 8 ms 9 ms nyc2-pr2-xe-0-3-0-0.us.twtelecom.net
[66.192.242.253]
5 * * * Request timed out.
6 * * * Request timed out.
7 12 ms 11 ms 12 ms INDEPENDENT.ear3.NewYork1.Level3.net
[4.28.130.18]
8 12 ms 12 ms 12 ms e4-8-0.csr0.alb1.inoc.net [64.246.130.10]
9 12 ms 12 ms 12 ms lagg0-40.fgc0.alb1.inoc.net [64.246.132.52]
10 12 ms 12 ms 12 ms cp-vps0.albyny.inoc.net [64.22.33.10]
Trace complete.
Ken Dibble
www.stic-cil.org
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
