NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Router blocking 1 website
Hello, I have read through the other similar discussions. One specific website has stopped connecting thru my router. This started all of a sudden a few weeks ago. Devices that I can bypass the r...
Thanks to all who tried to help. Through process of elimination, I decided to exchange the modem under warranty. Installed the new upgraded modem, had it activated by my ISP WOW, and the site is back ??
Whatever, it worked, sad though the hours and hours spent trying to figure this out.
I did try going directly PC to modem, but had the same result. Before I forget thanjs for your interest and help !!!
I have never played with any parental controls from the ISP or Netgear, or Norton for that matter.
The only way I reach that one site from here is through Ipad and I phone with the WiFi disconnected on the device.
This is what happened with the PC direct to modem:
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\Users\Wayne>tracert smith-wessonforum.com
Tracing route to smith-wessonforum.com [208.71.128.50]
over a maximum of 30 hops:
1 12 ms 12 ms 12 ms 23.28.124.1
2 12 ms 10 ms 17 ms dynamic-76-73-172-89.knology.net [76.73.172.89]
3 11 ms 12 ms 12 ms 76-73-168-108.knology.net [76.73.168.108]
4 16 ms 12 ms 13 ms 76-73-168-106.knology.net [76.73.168.106]
5 11 ms 11 ms 11 ms 76-73-168-104.knology.net [76.73.168.104]
6 23 ms 23 ms 22 ms static-69-73-0-141.knology.net [69.73.0.141]
7 24 ms 25 ms 22 ms dynamic-75-76-35-8.knology.net [75.76.35.8]
8 24 ms 26 ms 23 ms ae14.cr1-chi1.ip4.gtt.net [77.67.77.109]
9 46 ms 46 ms 45 ms xe-1-0-2.cr1-nyc4.ip4.gtt.net [89.149.134.117]
10 * * * Request timed out.
11 * * * Request timed out.
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.
C:\Users\Wayne>
Waynefi wrote:
I did try going directly PC to modem, but had the same result.
If you can't connect to the site when you are bypassing the modem, then it isn't the router doing the blocking.
It does look like a routing issue, since DNS did resolve the address. So I suggest contacting your ISP.
FWIW Verizon Fios will let me access the site, and ping also works for me.
I am also on Verizon FIOS (RI) and can access it. Here is tracert.
Tracing route to mail.smith-wessonforum.com [208.71.128.50]
over a maximum of 30 hops:
1 8 ms 2 ms 1 ms router.asus.com [192.168.1.1]
2 5 ms 4 ms 7 ms lo0-100.PRVDRI-VFTTP-315.verizon-gni.net [72.92.234.1]
3 10 ms 6 ms 7 ms B3315.PRVDRI-LCR-22.verizon-gni.net [100.41.0.144]
4 * * * Request timed out.
5 13 ms 14 ms 14 ms 0.xe-1-1-0.IL2.NYC9.ALTER.NET [152.63.26.66]
6 14 ms 14 ms 14 ms 0.ae8.GW10.EWR6.ALTER.NET [140.222.231.131]
7 13 ms 14 ms 14 ms customer.customer.alter.net [157.130.91.86]
8 14 ms 22 ms 14 ms techie-ic-133875-nyk-b2.c.telia.net [213.248.79.2]
9 14 ms 14 ms 14 ms mail.smith-wessonforum.com [208.71.128.50]
Trace complete.Second, here is a tracert from GTT's looking glass out of Chicago. Notice it routes to et-8-1-0.cr8-nyc3.ip4.gtt.net instead of xe-1-0-2.cr1-nyc4.ip4.gtt.net.
IPv4 traceroute to 208.71.128.50 traceroute to 208.71.128.50 (208.71.128.50), 12 hops max, 52 byte packets 1 et-8-1-0.cr8-nyc3.ip4.gtt.net (89.149.180.206) 26.181 ms 24.544 ms 24.151 ms MPLS Label=417607 CoS=0 TTL=1 S=1 2 xe-2-0-1.cr1-nyc4.ip4.gtt.net (89.149.134.125) 24.287 ms xe-1-2-2.cr1-nyc4.ip4.gtt.net (89.149.134.121) 23.352 ms xe-1-0-2.cr1-nyc4.ip4.gtt.net (89.149.134.117) 24.041 ms 3 techie-media-gw.ip4.gtt.net (77.67.71.18) 164.708 ms 28.815 ms 202.420 ms 4 mail.smith-wessonforum.com (208.71.128.50) 22.930 ms !<10> 24.205 ms !<10> 25.478 ms !<10>Also, do you live in MI? Seems like there are some issues with WOW in MI.See thread here. Overall I would suggest contacting your ISP and see if there are outages in your area. If not, then ask for Tier 2 (I hear bad things about WoW support) and see if they tracert to the site.
Motorola Arris from my Modem, suggest having the ISP Reprovision my Modem to IPV6 ???
Still nothing happening.
Talked to WOW cable 3 times, supposedly this incident it sent in to the next level of support to review.
Is it worth paying Netgear Premium Service to try and figure it out ?
Anybody ? Any last thoughts ?
It is more likely to be an ISP problem.
Actually, I can go next door and get the site in question using the same ISP.
Hi Waynefi,
Try MAC spoofing. Some reported that this step works on issues like this.
http://kb.netgear.com/app/answers/detail/a_id/1086
Regards,
Dexter
Community Team
Waynefi wrote:
Actually, I can go next door and get the site in question using the same ISP.
I misread your earlier post saying that you connected normally when you bypassed the router (I thought you said it failed both ways).
So Mac spoofing is worth a try (setting the router WAN mac address to match the PC that works when you do the bypass). It is weird though.
Been through all that please see postings.
