NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Waynefi
Dec 31, 2016Aspirant
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...
- Jan 08, 2017
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.
StephenB
Jan 06, 2017Guru - Experienced User
Can you save off a tracert from the neighbor's PC, and perhaps run a fresh one from yours? Then you can compare the two route paths.
Waynefi
Jan 07, 2017Aspirant
Below is neighbors system that connects to the site, ping and tracert. Below this is mine that does not. 2 postings above this one is a summary of all that was done without success. Both using same ISP. WOW Wideopenwest
Pinging smith-wessonforum.com [208.71.128.50] with 32 bytes of data
Reply from 208.71.128.50: bytes=32 time=45ms TTL=53
Reply from 208.71.128.50: bytes=32 time=46ms TTL=53
Reply from 208.71.128.50: bytes=32 time=46ms TTL=53
Reply from 208.71.128.50: bytes=32 time=46ms TTL=53
Ping statistics for 208.71.128.50: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds:
Minimum = 45ms, Maximum = 46ms, Average = 45ms
tracert smith-wessonforum.com Tracing route to smith-wessonforum.com [208.71.128.50] over a maximum of 30 hops:
1 8 ms 18 ms 8 ms 23.28.124.1
2 11 ms 11 ms 10 ms dynamic-76-73-172-93.knology.net [76.73.172.93]
3 9 ms 12 ms 10 ms 76-73-168-108.knology.net [76.73.168.108]
4 10 ms 11 ms 11 ms 76-73-168-106.knology.net [76.73.168.106]
5 11 ms 11 ms 8 ms 76-73-168-104.knology.net [76.73.168.104]
6 24 ms 23 ms 20 ms static-69-73-0-141.knology.net [69.73.0.141]
7 22 ms 21 ms 23 ms dynamic-75-76-35-8.knology.net [75.76.35.8]
8 22 ms 24 ms 23 ms ae14.cr1-chi1.ip4.gtt.net [77.67.77.109]
9 45 ms 43 ms 43 ms xe-2-1-1.cr1-nyc4.ip4.gtt.net [89.149.134.133]
10 43 ms 45 ms 43 ms techie-media-gw.ip4.gtt.net [77.67.71.18]
11 44 ms 46 ms 43 ms mail.smith-wessonforum.com [208.71.128.50]
Trace complete.
Below from my system
Pinging smith-wessonforum.com [208.71.128.50] with 32 bytes of data
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 208.71.128.50:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
Tracing route to smith-wessonforum.com [208.71.128.50]
over a maximum of 30 hops:
1 3 ms <1 ms <1 ms 192.168.1.1
2 10 ms 23.28.124.1 reports: Destination host unreachable.
Trace complete.
Anybody
- WaynefiJan 08, 2017Aspirant
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.