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 ...
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
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
AMAZING. MAC Spoofing worked. So now the question is, is that an issue with my router or the ISP? I use Wave Broadband and never have seen this issue before.
Tracert works by sending individual packets to each hop between your router and the destination. Each hop responds with information about the its IP address and response time.
A ping works by sending a packet to the destination, which then responds with similar details; intermediate hops just forward ping packets and don't send any responses back to the sender.
Your tracert is not making it all the way to the destination. Everything from hop 19 onwards is failing. If the destination cannot be reached through tracert, then ping will also fail. Since tracert is failing deep inside the Internet, your router is not the problem. You claim, however, that you can reach the website when directly connected to the modem. If so, please post a tracert to the website when directly connected to the modem.
[Edit: I just saw your reply about MAC spoofing fixing your problem. It will be great if you can post a new tracert.]
Post MAC Spoofing.
1 1 ms <1 ms <1 ms 192.168.1.1
2 132 ms 137 ms 147 ms 10.60.128.1
3 129 ms 162 ms 186 ms 24.113.43.225
4 54 ms 41 ms 62 ms 24.113.39.146
5 30 ms 59 ms 63 ms 24.113.43.25
6 106 ms 89 ms 83 ms 24.113.43.9
7 103 ms 63 ms 75 ms 216.243.24.89
8 161 ms 151 ms 96 ms 174.127.140.137
9 106 ms 61 ms 75 ms 208.185.155.61
10 214 ms 212 ms 143 ms 64.125.31.49
11 205 ms 237 ms 240 ms 64.125.31.170
12 218 ms 179 ms 188 ms 64.125.31.206
13 249 ms 218 ms 156 ms 64.125.25.46
14 108 ms 125 ms 192 ms 64.125.31.197
15 303 ms 179 ms 180 ms 128.177.104.134
16 146 ms 136 ms 267 ms 207.210.124.186
17 167 ms 346 ms 253 ms 69.73.135.230
18 137 ms 111 ms 129 ms 69.73.137.130
19 112 ms 124 ms 119 ms 69.73.172.48
Finished
Still concerning that changing my MAC address on the router changed my access to the specific site.
