- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I can't access to several websites (www.isisparenting.com, www.etvnet.com), including my internet television. So, I'm wasting my money. Traceroute revealed that certain nods are unavailable and stop signal passing. This is weird because the idea of Internet is based on re-routing if such kind of things happens. I chatted to Verizon representative (chat ID# 12261042593) and was suprised to know that this issue is "out of their boundaries". Is this my Internet provider, I ask myself? Seems like charging money is done better by them.
I use MAC so neither firewall nor antivirus are installed that could potentially block some sites. I did basic things like restarting computer, router, trying different browsers. Nothing helped.
Very important that I also tryed to connect via AT&T 3G on my phone and successfully accessed those sites. So, this is obviously Verizon problem.
So, this is tracerouting info for etvnet.com:
traceroute to 74.86.94.186 (74.86.94.186), 64 hops max, 52 byte packets
1 wireless_broadband_router (192.168.1.1) 3.028 ms 3.974 ms 2.489 ms
2 l100.bstnma-vfttp-103.verizon-gni.net (98.118.61.1) 16.394 ms 8.833 ms 7.060 ms
3 g5-2-1703.bstnma-lcr-07.verizon-gni.net (130.81.109.74) 10.051 ms 7.190 ms 7.116 ms
4 so-0-3-0-0.bos-bb-rtr1.verizon-gni.net (130.81.29.252) 10.729 ms 8.852 ms 7.844 ms
5 0.so-0-2-0.xl3.bos4.alter.net (152.63.16.137) 20.736 ms 20.376 ms 20.804 ms
6 0.so-1-2-0.xl3.dfw7.alter.net (152.63.98.77) 66.983 ms 65.998 ms 65.041 ms
7 * * *
8 internapgige1-gw.customer.alter.net (65.208.15.230) 69.765 ms 66.508 ms 67.145 ms
9 border3.tge4-1-bbnet2.ext1.dal.pnap.net (216.52.191.83) 68.599 ms 72.176 ms 65.169 ms
10 * * *
11 po6.dar01.sr01.dal01.networklayer.com (173.192.18.211) 64.929 ms 64.686 ms 66.023 ms
12 po1.cer01.sr01.dal01.networklayer.com (66.228.118.200) 68.144 ms 68.105 ms 77.049 ms
13 npr01.dal01.networklayer.com (66.228.118.129) 68.632 ms 62.707 ms 62.528 ms
14 * * *
15 (66.228.119.3) 70.289 ms 70.432 ms 112.639 ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
Tracerouting to isisparenting.com:
traceroute to 75.126.95.50 (75.126.95.50), 64 hops max, 52 byte packets
1 wireless_broadband_router (192.168.1.1) 17.588 ms 11.954 ms 0.694 ms
2 l100.bstnma-vfttp-103.verizon-gni.net (98.118.61.1) 9.027 ms 19.264 ms 7.177 ms
3 g5-2-1703.bstnma-lcr-07.verizon-gni.net (130.81.109.74) 7.437 ms 6.740 ms 7.426 ms
4 so-0-3-0-0.bos-bb-rtr1.verizon-gni.net (130.81.29.252) 7.733 ms 10.791 ms 10.281 ms
5 0.so-0-2-0.xl3.bos4.alter.net (152.63.16.137) 20.547 ms 20.989 ms 16.719 ms
6 0.so-1-2-0.xl3.dfw7.alter.net (152.63.98.77) 65.444 ms 65.938 ms 67.576 ms
7 tengige0-6-4-0.gw4.dfw13.alter.net (152.63.101.21) 65.436 ms
tengige0-6-1-0.gw4.dfw13.alter.net (152.63.101.13) 62.453 ms
tengige0-6-4-0.gw4.dfw13.alter.net (152.63.101.21) 64.247 ms
8 internapgige1-gw.customer.alter.net (65.208.15.230) 69.588 ms 72.633 ms 65.417 ms
9 border3.tge4-1-bbnet2.ext1.dal.pnap.net (216.52.191.83) 71.218 ms 77.522 ms 68.992 ms
10 * * *
11 po6.dar01.sr01.dal01.networklayer.com (173.192.18.211) 65.208 ms 65.246 ms 143.976 ms
12 po1.fcr01.sr01.dal01.networklayer.com (66.228.118.154) 68.606 ms 90.912 ms 69.501 ms
13 * * *
14 * * *
15 * * *
16 * * *
Pinging 66.228.118.XX gives 100% packet loss.
Problem like this happens time to time (http://forums.verizon.com/t5/FiOS-Internet/Can-t-access-certain-websites-including-my-own-for-second... and how it is resolved is unclear.
I would appreciate if people share their opinion and experience. I would also like to hear some helpful suggestions from Verizon techs.
Thanks!
Solved! Go to Correct Answer
Correct answers
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yeah they have a two to four hour lease time with their ip's. so without calling them and asking that they release the ip address, the 20 minutes would be too short timewise.,
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
it will self heal. BUT you should be able to temporarily access it with a proxy. Go to https://www.megaproxy.com/freesurf/
and u can access it until you get a new ip address.
The best thing for you to do in my opinion is physically power off your router when you got to bed tonight. In the morning when you turn it on you will like get a new ip address and be able to access like normal.
If you can access the site through a proxy (like https://www.megaproxy.com/freesurf/), then that means that fios is providing you a clear path from point a to b.
So what's blocking you? Most of the time its the site itself blocking or banning the ip address you have. Not to any fault of your own probably. The ip addresses are shared between residential users, so whoever had your ip before you may have reeked havoc on their boards.
Its also possible that its something as simple as an out of date Bogon filter and a new ip would solve that too.
Periodically, VZ places new IP blocks into use. If a site (or ISP) has an outdated bogon filter list, it will drop packets from that IP range (typically /16)... If the problem is an outdated bogon filter, the problem has to be fixed by the site with the outdated list.
Something new that has come up for me, that I haven't tried for a Fix is at this link. So give this link a try, follow the instructions and let us know if it works to fix the problem, if it doesn't then you are probably looking at the above scenario's for your answer.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you for suggested solutions.
The last one with port forwarding provided in the link didn't help.
Access with proxy worked, however I wasn't able to login inside the website each time receiving a Megaproxy service error.
Hopefully, everything will be fine with new ip address. I used to turn the router off for 20 minutes and nothing changed. May be longer period is required... Will try...
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yeah they have a two to four hour lease time with their ip's. so without calling them and asking that they release the ip address, the 20 minutes would be too short timewise.,
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good news! Restarting the router by turning off for the whole night helped! The new IP was released and the problem disappeared. So, it's clear now that the problem was caused by blocking IP at some point for unknown reasons.