rseal
@verizon.net
|  Cannot connect to University website(s) via Verizon DSL
I have been unable to connect to my University's website from home since subscribing to Verizon DSL. Here is the traceroute result:
130.203.201.201 is from United States(US) in region North America
TraceRoute to 130.203.201.201 [engr-mis-web02.cedcc.psu.edu]
Hop (ms) (ms) (ms) IP Address Host name
1 9 9 8 72.249.0.65 -
2 5 5 10 206.123.64.22 -
3 7 6 9 216.52.189.9 border4.g3-2.colo4dallas-3.ext1.dal.pnap.net
4 16 7 6 216.52.191.98 core3.tge5-2-bbnet2.ext1.dal.pnap.net
5 7 9 12 207.88.185.73 207.88.185.73.ptr.us.xo.net
6 8 9 6 65.106.4.233 65.106.4.233.ptr.us.xo.net
7 7 9 6 206.111.5.42 206.111.5.42.ptr.us.xo.net
8 53 53 54 208.49.224.198 pittsburgh-supercomputing.ge-3-3-0.405.ar2.cle1.gblx.net
9 Timed out 199 Timed out 192.88.115.1 bar-ccore-squirt-ge-4-3-0-0.3rox.net
10 59 57 59 192.88.114.73 psu-tc-i1.3rox.net
11 Timed out Timed out Timed out -
12 Timed out Timed out Timed out -
13 Timed out Timed out Timed out -
14 Timed out Timed out Timed out -
Trace aborted.
Is this a Verizon issue - or should I look elsewhere?
Ryan |
|
toof
join:2002-11-09
Pottstown, PA
3 edits | said by rseal :
I have been unable to connect to my University's website from home since subscribing to Verizon DSL. Here is the traceroute result:
130.203.201.201 is from United States(US) in region North America
TraceRoute to 130.203.201.201 [engr-mis-web02.cedcc.psu.edu]
Hop (ms) (ms) (ms) IP Address Host name
1 9 9 8 72.249.0.65 -
2 5 5 10 206.123.64.22 -
3 7 6 9 216.52.189.9 border4.g3-2.colo4dallas-3.ext1.dal.pnap.net
4 16 7 6 216.52.191.98 core3.tge5-2-bbnet2.ext1.dal.pnap.net
5 7 9 12 207.88.185.73 207.88.185.73.ptr.us.xo.net
6 8 9 6 65.106.4.233 65.106.4.233.ptr.us.xo.net
7 7 9 6 206.111.5.42 206.111.5.42.ptr.us.xo.net
8 53 53 54 208.49.224.198 pittsburgh-supercomputing.ge-3-3-0.405.ar2.cle1.gblx.net
9 Timed out 199 Timed out 192.88.115.1 bar-ccore-squirt-ge-4-3-0-0.3rox.net
10 59 57 59 192.88.114.73 psu-tc-i1.3rox.net
11 Timed out Timed out Timed out -
12 Timed out Timed out Timed out -
13 Timed out Timed out Timed out -
14 Timed out Timed out Timed out -
Trace aborted.
Is this a Verizon issue - or should I look elsewhere?
Ryan
Nah, it's an issue with the #11 hop after 3rox.net. The #10 router is trying to pass everything down the line, but apparently there's a router down that it's trying to send all the data to.
Once you hit hop #2, you're off of the verizon owned network.
From arin.net:
OrgName: Colo4Dallas LP
OrgID: COLO4
Address: 3000 Irving Blvd
City: Dallas
StateProv: TX
PostalCode: 75247
Country: US
NetRange: 206.123.64.0 - 206.123.127.255
Edit: Sorry, forgot to include a suggestion 
I would suggest contacting 3rox and see what's going on. More than likely it's just a temporary outage.
Their website is »www.3rox.net/
The Three Rivers Optical Exchange is a regional network aggregation point providing high speed commodity and research network access to sites in Western and Central Pennsylvania and West Virginia. The Exchange is based at Carnegie Mellon University and is operated and managed by the Pittsburgh Supercomputing Center. While the primary focus of the Exchange is to provide cost effective, high capacity, state-of-the-art network connectivity to the university community, this infrastructructure also provides well defined network services to both community (K12, government) and commercial entities in Western Pennsylvania. University member sites currently include: Carnegie Mellon University, the Pennsylvania State University, Pittsburgh Supercomputing Center, the University of Pittsburgh and West Virginia University. |
|
rseal
@verizon.net
| Thanks for the advice. The only problem I see is that I have been unable to connect to this website for over a year now. Others (in other parts of town) have no problems. I have sent an e-mail to 3rox to see what they know.
Thanks again,
Ryan |
|
rseal
@verizon.net | Found the real problem; it was a firmware problem with my router, which was blocking certain websites. Traceroute still shows the last hop down - but the website is now visible. All is well for now.
Thanks again,
Ryan |
|
