×

Switch Account

Unable to access a frequently-used website

Unable to access a frequently-used website

SOLVED
Reply
Copper Contributor brh
Copper Contributor
Posts: 10
Registered: ‎01-21-2011
Message 1 of 7
(6,260 Views)

Good evening all.

 

For over a month now, I've been unable to access a website that I've been visiting for over 3 years now.  I've been in contact with Verizon's support team several times now, and they have jdusted their hands off the matter, stating that the problem lies outside of their network. 

 

I contacted the webmaster of this domain and he assured me that he isn't blocking me.  So, what can I do now?  I've used a proxy which works, but is cumbersome, with advertizing and some features in the forums don't work.

 

The website is www.northamericangp.com and the error message is:

 

The connection has timed out.
The server at www.northamericangp.com is taking too long to respond.     


      

Traceroute results in the following:


C:\>nslookup www.northamericangp.com
Server:  myrouter.home
Address:  192.168.1.1

Non-authoritative answer:
Name:    northamericangp.com
Address:  67.15.211.17
Aliases:  www.northamericangp.com


C:\>tracert www.northamericangp.com

Tracing route to northamericangp.com [67.15.211.17]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2     5 ms     4 ms     4 ms  L100.DLLSTX-VFTTP-69.verizon-gni.net [96.226.221.1]
  3     5 ms     6 ms     5 ms  P4-0.DLLSTX-LCR-02.verizon-gni.net [130.81.48.134]
  4     7 ms     8 ms     9 ms  so-6-2-0-0.DFW01-BB-RTR2.verizon-gni.net [130.81.28.210]
  5     9 ms     9 ms     7 ms  0.ae2.BR1.DFW13.ALTER.NET [152.63.2.149]
  6     8 ms     8 ms     8 ms  ae6.edge2.dallas3.level3.net [4.68.62.165]
  7    68 ms    56 ms    73 ms  ae-91-90.ebr1.Dallas1.Level3.net [4.69.145.242]
  8    64 ms    64 ms    66 ms  ae-1-13.bar1.Houston1.Level3.net [4.69.137.137]
  9    15 ms    14 ms    13 ms  ae-0-11.bar2.Houston1.Level3.net [4.69.137.134]
 10    14 ms    14 ms    14 ms  THE-PLANET.bar2.Houston1.Level3.net [4.78.10.30]
 11    35 ms    35 ms    49 ms  e1-3.ibr01.hstntx2.networklayer.com [70.87.253.154]
 12    37 ms    36 ms    35 ms  te2-1.dsr01.hstntx2.networklayer.com [74.55.252.146]
 13    37 ms    38 ms    36 ms  po1.car12.hstntx2.networklayer.com [74.55.252.170]
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.

 

I'm not sure what to do next, any ideas?

 

Bjoern


6 REPLIES 6
Gold Contributor III
Gold Contributor III
Posts: 1,122
Registered: ‎12-04-2009
Message 2 of 7
(6,230 Views)

Did your WAN IP address change when this started? 

 

Sometimes sties or ISPs have outdated bogon filters.  These can block access to web sites if you are assigned an IP address in an IP block that VZ has recently put into service and the site or ISP has out of date filters.  From the traceroute, it looks as if the site's ISP might be using bogon filters.

 

No problem accessing it from a 98.111.x.x address.

 

Tracing route to northamericangp.com [67.15.211.17]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     5 ms     4 ms     4 ms  L100.PHLAPA-VFTTP-64.verizon-gni.net [98.111.x.x]
  3     5 ms     4 ms     4 ms  G2-0-0-864.PHLAPA-LCR-08.verizon-gni.net [130.81.133.188]
  4     5 ms     4 ms     4 ms  so-3-0-1-0.PHIL-BB-RTR2.verizon-gni.net [130.81.29.6]
  5    11 ms    12 ms    12 ms  so-7-1-0-0.RES-BB-RTR2.verizon-gni.net [130.81.19.106]
  6    11 ms    12 ms    12 ms  0.so-6-3-0.XL4.IAD8.ALTER.NET [152.63.32.161]
  7    47 ms    12 ms    12 ms  0.ae4.BR1.IAD8.ALTER.NET [152.63.33.121]
  8    13 ms    14 ms    14 ms  ae6.edge1.washingtondc4.level3.net [4.68.62.133]

  9    14 ms    14 ms    14 ms  vlan90.csw4.Washington1.Level3.net [4.69.149.254]
 10    15 ms    14 ms    14 ms  ae-91-91.ebr1.Washington1.Level3.net [4.69.134.141]
 11    15 ms    14 ms    14 ms  ae-8-8.ebr1.Washington12.Level3.net [4.69.143.218]
 12    30 ms    34 ms    37 ms  ae-6-6.ebr1.Atlanta2.Level3.net [4.69.148.105]
 13    50 ms    49 ms    72 ms  ae-1-7.bar2.Houston1.Level3.net [4.69.137.141]
 14    50 ms    49 ms    49 ms  THE-PLANET.bar2.Houston1.Level3.net [4.78.10.30]

 15    53 ms    44 ms    44 ms  e1-3.ibr01.hstntx2.networklayer.com [70.87.253.154]
 16    45 ms    44 ms    44 ms  te2-1.dsr01.hstntx2.networklayer.com [74.55.252.146]
 17    45 ms    44 ms    44 ms  po1.car11.hstntx2.networklayer.com [74.55.252.166]
 18    44 ms    44 ms    44 ms  ns1.siteground175.com [67.15.211.17]

Trace complete.

Silver Contributor IV
Silver Contributor IV
Posts: 588
Registered: ‎12-22-2009
Message 3 of 7
(6,224 Views)

I just went to that website and it came up instantaneously.  I am using IE8 and Windows XP.  Perhaps if you give more information about your computer and programs, someone will be able to help you.

Gold Contributor V
Gold Contributor V
Posts: 1,692
Registered: ‎05-17-2009
Message 4 of 7
(6,208 Views)

Well according to your tracert. Verizon is right. The problem is outside their network. And it looks like the web host is wrong. They are blocking you. They likely have a filter on that is blocking your IP.




====================================================================================

Error exists between keyboard and chair.
Copper Contributor brh
Copper Contributor
Posts: 10
Registered: ‎01-21-2011
Message 5 of 7
(6,191 Views)

 


@Anti-Phish wrote:

Did your WAN IP address change when this started? 

 

Sometimes sties or ISPs have outdated bogon filters.  These can block access to web sites if you are assigned an IP address in an IP block that VZ has recently put into service and the site or ISP has out of date filters.  From the traceroute, it looks as if the site's ISP might be using bogon filters.

 

No problem accessing it from a 98.111.x.x address.

 

Tracing route to northamericangp.com [67.15.211.17]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     5 ms     4 ms     4 ms  L100.PHLAPA-VFTTP-64.verizon-gni.net [98.111.x.x]
  3     5 ms     4 ms     4 ms  G2-0-0-864.PHLAPA-LCR-08.verizon-gni.net [130.81.133.188]
  4     5 ms     4 ms     4 ms  so-3-0-1-0.PHIL-BB-RTR2.verizon-gni.net [130.81.29.6]
  5    11 ms    12 ms    12 ms  so-7-1-0-0.RES-BB-RTR2.verizon-gni.net [130.81.19.106]
  6    11 ms    12 ms    12 ms  0.so-6-3-0.XL4.IAD8.ALTER.NET [152.63.32.161]
  7    47 ms    12 ms    12 ms  0.ae4.BR1.IAD8.ALTER.NET [152.63.33.121]
  8    13 ms    14 ms    14 ms  ae6.edge1.washingtondc4.level3.net [4.68.62.133]

  9    14 ms    14 ms    14 ms  vlan90.csw4.Washington1.Level3.net [4.69.149.254]
 10    15 ms    14 ms    14 ms  ae-91-91.ebr1.Washington1.Level3.net [4.69.134.141]
 11    15 ms    14 ms    14 ms  ae-8-8.ebr1.Washington12.Level3.net [4.69.143.218]
 12    30 ms    34 ms    37 ms  ae-6-6.ebr1.Atlanta2.Level3.net [4.69.148.105]
 13    50 ms    49 ms    72 ms  ae-1-7.bar2.Houston1.Level3.net [4.69.137.141]
 14    50 ms    49 ms    49 ms  THE-PLANET.bar2.Houston1.Level3.net [4.78.10.30]

 15    53 ms    44 ms    44 ms  e1-3.ibr01.hstntx2.networklayer.com [70.87.253.154]
 16    45 ms    44 ms    44 ms  te2-1.dsr01.hstntx2.networklayer.com [74.55.252.146]
 17    45 ms    44 ms    44 ms  po1.car11.hstntx2.networklayer.com [74.55.252.166]
 18    44 ms    44 ms    44 ms  ns1.siteground175.com [67.15.211.17]

Trace complete.


 

Thanks for the reply, Anti-Phish.

 

According to your trace, the second-last hop is po1.car11.hstntx2.networklayer.com, whereas my last hop is po1.car12.hstntx2.networklayer.com.  Could it be that this particlular router (car12) is faulty?  I will also try to contact the domain host of NAGP.

 

 

Bjoern

 

Highlighted
Platinum Contributor III
Platinum Contributor III
Posts: 5,881
Registered: ‎07-22-2009
Message 6 of 7
(6,167 Views)

If you can access the site through www.megaproxy.com/freesurf/ or a similiar web proxy service, then Verizon is giving you access.   The Web Host probably has an out of date filter.

 

He can either add your subnet to his network, or you can simply turn off your modem for four hours (there is a lease time on the ip address that doesn't expire for 4 hours) and then turn it back on.   I usually tell folks to do this at night when they go to bed.   Basically just unplug the modem and don't plug it back in until the morning.

 

OR if you want it right away, you can try chat support or Call Verizon, and don't bother telling them your problem AT ALL.  just ask for tech support and ask if they can release your IP Address, or break the dhcp lease.

 

you should have your modem powered off when they do that, and don't plug it back in for AT LEAST 3 to 5 minutes before plugging it back in. 

 

If you plug it in immediately, then you run the risk of that IP address coming right back to you, but if you give it a few minutes, it will most likely go back into the dhcp pool and get assigned to someone else, and you will be in perfect shape to get a new ip address.

Copper Contributor brh
Copper Contributor
Posts: 10
Registered: ‎01-21-2011
Message 7 of 7
(5,935 Views)

Thanks Hub.

 

Your suggestion to switch my router/modem off for a couple of hours did the trick..

 

Smiley Wink

 

 

How-To Videos
 
The following videos were produced by users like you!
   
Videos are subject to the Verizon Fios Community Terms of Service and User Guidelines and contains content that is not created by Verizon.


Browse Categories
Categories:
Posts

Verizon Troubleshooters
Unable to find your answer here? Try searching Verizon Troubleshooters for more options.