NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Unable to access a website on a R6300
Yesterday a website I frequent became unavailable. i get ERR_CONNECTION_TIMED_OUT. It is 69.73.172.48(www.waguns.org).
I can tracert to it but not PING it. When I connect directly into my broadband modem I have no issues.
I have reset(earased) all setting on my R6300v1. I have restored to e previous point on my computer. I have 2 and both get the same error along with my cell phone when connected wired or wireless to the R6300. I have followed the common steps of renewing, flushing/releasing my IP and reset the modem and router mulitme times. I also tried using Google's DNS. No luck.
Ping results.
Request timed out
Request timed out
Request timed out
Request timed out
Ping request could not find host 69.73.172.48. Please check the name and try again.
Tracert results
1 4 ms <1 ms <1 ms 192.168.1.1
2 19 ms 19 ms 19 ms 10.60.128.1
3 28 ms 24 ms 30 ms 24.113.43.225
4 23 ms 20 ms 27 ms 24.113.39.146
5 36 ms 32 ms 23 ms 24.113.43.25
6 25 ms 19 ms 29 ms 24.113.43.9
7 28 ms 19 ms 29 ms 216.243.24.89
8 15 ms 22 ms 13 ms 174.127.140.137
9 19 ms 32 ms 15 ms 208.185.155.61
10 61 ms 54 ms 59 ms 64.125.31.49
11 81 ms 83 ms 77 ms 64.125.31.170
12 98 ms 99 ms 109 ms 64.125.31.206
13 127 ms 114 ms 105 ms 64.125.25.46
14 113 ms 129 ms 99 ms 64.125.31.197
15 97 ms 120 ms 238 ms 128.177.104.134
16 125 ms 99 ms 89 ms 207.210.124.186
17 117 ms 109 ms 108 ms 69.73.135.230
18 127 ms 99 ms 99 ms 69.73.137.130
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
Finished
Hi INFTeamLeader,
If you are with a cable ISP, you may try performing MAC spoofing and see if it works. You may refer to the link below for the instructions:
http://kb.netgear.com/app/answers/detail/a_id/1086
Regards,
Dexter
Community Team
11 Replies
Hi INFTeamLeader,
Is the tracert command that you have performed through the router? If it is, it does show that it is being routed going out to your ISP but it gets dropped somewhere over the Internet (starting from line 19). Can you try using OpenDNS? You may refer to this link on how to set it up.
Regards,
Dexter
Community Team
Maybe it wasn't clear. the tracert shows I can make it past my router using a tracert, but my router is not letting the PING leave. Hence not letting my browser traffic leave.
I can connect directly to the MODEM and get to the site no problem.
I can NOT connect through the router and get to the site.
Hi INFTeamLeader,
If you are with a cable ISP, you may try performing MAC spoofing and see if it works. You may refer to the link below for the instructions:
http://kb.netgear.com/app/answers/detail/a_id/1086
Regards,
Dexter
Community Team
- Ahh, so hop 19 is the actual destination. I'll wager that MAC spoofing had nothing to do with it. The destination was simply down and came back up. You could try removing the MAC spoofing and see if it immediately falls. Or, if you rather not bother because things are working, then declare victory and move on.
The site was up the entire time and I could access it via cellular, VPN tunnel into work or any other location but via through my router.
- Yes that's possible but it wouldn't explain why it didn't work without any MAC spoofing. Oh well, I have no explanation. A change in Layer 2 addressing should not affect Layer 3 in this instance.
