Quote:
Originally Posted by Nateydawgy
Any solutions if that's what is causing it then?
|
It's always doing this? It times out at #2? Here's my tracert to a Riot server:
Tracing route to 216.133.234.54 over a maximum of 30 hops
1 11 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 5 ms 4 ms L100.WASHDC-VFTTP-123.verizon-gni.net [96.255.20
0.1]
3 11 ms 14 ms 7 ms G0-10-3-4.WASHDC-LCR-21.verizon-gni.net [130.81.
137.210]
4 10 ms 9 ms 10 ms so-13-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.
22.54]
5 13 ms 12 ms 14 ms 0.xe-7-0-0.XL3.IAD8.ALTER.NET [152.63.34.201]
6 84 ms 90 ms 84 ms 0.so-7-0-0.XL3.LAX15.ALTER.NET [152.63.112.53]
7 88 ms 84 ms 84 ms POS6-0-0.GW3.LAX15.ALTER.NET [152.63.112.105]
8 88 ms 85 ms 87 ms internapGIGE-gw.customer.alter.net [157.130.236.
110]
9 89 ms 88 ms 85 ms border1.po2-20g-bbnet2.lax010.pnap.net [216.52.2
55.103]
10 ^C
As you can see, it starts at my router, goes to what seems to be Verizon's hub in DC, then through different routers until it reaches Riot (at which point their firewall says fk you to me so I terminate). Anyways the moral of the story is that the earlier in the hop points, the closer the problem is to you. If you're timing out as early as hop #2, then it's either your router (check firewalls) or your ISP.
Best advice to you would be to try disabling any firewalls.