bfin Posted December 6, 2014 Share Posted December 6, 2014 1 <1 ms <1 ms <1 ms 192.168.1.1 2 7 ms 8 ms 7 ms 10.189.88.1 3 18 ms 45 ms 10 ms 172.30.76.177 4 10 ms 10 ms 15 ms 172.30.32.69 5 28 ms 25 ms 32 ms cr2.attga.ip.att.net [12.122.140.170] 6 26 ms 23 ms 23 ms cr2.attga.ip.att.net [12.122.140.170] 7 27 ms 25 ms 28 ms 12.122.117.121 8 * * * Request timed out. 9 87 ms 88 ms 85 ms ae-2-70.edge8.SanJose1.Level3.net [4.69.152.84] 10 118 ms 84 ms 85 ms ae-2-70.edge8.SanJose1.Level3.net [4.69.152.84] 11 88 ms 85 ms 85 ms 4.28.172.102 12 85 ms 85 ms 85 ms 159.153.68.252 and this is what i got. Link to comment Share on other sites More sharing options...
Haystak Posted December 7, 2014 Share Posted December 7, 2014 Your going to need to test a few things. However from your traceroute, it looks like your issue is latency with your provider. It could be spurious, or continuous, so your going to need to do a ping -t on that list of IP addresses you have listed in your traceroute. What you are doing here by pinging all of those nodes in your chain is seeing where your latency is coming from. Tracert is good to get the ip addresses. The node thats giving you trouble would be the first one in the list that experiences high latency. Even spurious latency will cause your game to have issues. Once you have identified the node that is having issues, you are going to need to call your provider to see what they can do about it(if its within their network). Link to comment Share on other sites More sharing options...
bfin Posted December 7, 2014 Author Share Posted December 7, 2014 not sure what i'm doing, just getting getting the info for the csr to help me figure it out. plus i don't have a clue how to run a ping. any help would be appreciated Link to comment Share on other sites More sharing options...
bfin Posted December 7, 2014 Author Share Posted December 7, 2014 what i need is a way of knowing how to read what i have gotten in the trace route. Link to comment Share on other sites More sharing options...
Haystak Posted December 7, 2014 Share Posted December 7, 2014 (edited) 192.168.1.1 10.189.88.1 172.30.76.177 172.30.32.69 12.122.140.170 12.122.140.170 12.122.117.121 4.69.152.84 4.69.152.84 4.28.172.102 159.153.68.252 These are the Ip addresses of the devices between you and whatever you are pinging. They are ordered by the path they take from your computer. You can def ignored the stuff in green as its not the issue, as your latency picks up after you start going to those nodes. Now even though 12.122.117.121 is the last decent reply in your route, it doesnt mean that "that" device is what is having issues, as any of the devices before it could of caused the latency. Your next test now is to do a continuous ping to the devices going from your machine to 12.122.117.121. In order to do a ping command go to your command prompt type in ping -t 192.168.1.1 now it will continue pinging until you close the window. The results you are seeing in this window indicate how long it takes for that device to respond to a packet measured in milliseconds. For web traffic, anything under 300 is just fine. For streaming, such as video game, anything over 200 and your going to start to lose packets which is bad, as losing packets means abilities not going off, people and mobs jumps all over. Desync in general, in which your pretty much idle until your client syncs back up. Now if this device never returns a high reply(the example I gave you, is your cable router) then that means your first device is golden. Even if you get a few spurious high pings, its not that bad. If you start to notice groupings of 150ms+ pings then their is your issue. After the first device is done, go on to the next one. Same command, just take the second IP address and it would look like this. ping -t 10.189.88.1 and the next one would be ping -t 172.30.76.177 It is most likely within the first 3 or four devices your trying to communicate with. As once you get past your ISP the interwebs takes over, and theirs a bajillion different routes your data could take. You might be better off having a real tech look at it(dont let your ISP send some contractor bubbah out, they can be intelligent, but often they dont know anything about routing, or latency. They know speedtest.net, and signal stregnth, and when they are done looking, they usually charge you or your provider. GL I hope this helps. Sorry for anyone reading this that is wondering why ther server forum is turning into a call center. Edited December 7, 2014 by Haystak Link to comment Share on other sites More sharing options...
bfin Posted December 8, 2014 Author Share Posted December 8, 2014 thanx and sorry myself for using this forum as a call center but i needed a little help and this was what a rep suggested i do. as far as the tracert. i just needed someone to get me a little further along. working on the situation now. hopefull i can get it resolved soon. Link to comment Share on other sites More sharing options...
Haystak Posted December 9, 2014 Share Posted December 9, 2014 thanx and sorry myself for using this forum as a call center but i needed a little help and this was what a rep suggested i do. as far as the tracert. i just needed someone to get me a little further along. working on the situation now. hopefull i can get it resolved soon. Howd the troubleshooting go? Link to comment Share on other sites More sharing options...
bfin Posted December 10, 2014 Author Share Posted December 10, 2014 well it went as well as expected. think I'm gonna end up having a tech from my ISP come out next time it happens. just wish i could foresee when it would so i could have them here when it happens.....wish i knew more about this stuff personally. but i am much obliged by the assistance you gave me. Finlai Legacy Kuzordin 59 Gaurdian, Kishtira 55 Powertech Link to comment Share on other sites More sharing options...
Lord_Raven_Wolf Posted December 10, 2014 Share Posted December 10, 2014 1 <1 ms <1 ms <1 ms 192.168.1.1 2 7 ms 8 ms 7 ms 10.189.88.1 3 18 ms 45 ms 10 ms 172.30.76.177 4 10 ms 10 ms 15 ms 172.30.32.69 5 28 ms 25 ms 32 ms cr2.attga.ip.att.net [12.122.140.170] 6 26 ms 23 ms 23 ms cr2.attga.ip.att.net [12.122.140.170] 7 27 ms 25 ms 28 ms 12.122.117.121 8 * * * Request timed out. 9 87 ms 88 ms 85 ms ae-2-70.edge8.SanJose1.Level3.net [4.69.152.84] 10 118 ms 84 ms 85 ms ae-2-70.edge8.SanJose1.Level3.net [4.69.152.84] 11 88 ms 85 ms 85 ms 4.28.172.102 12 85 ms 85 ms 85 ms 159.153.68.252 and this is what i got. How did you do this trace? I'm trying to help a friend who is having problems staying connected to the server. He's done a trace and the IP giving him problems is 4.28.172.102 According to customer service helping him that IP is dropping 100% of his data. Any help with any of this would be appreciated. Thanks. Link to comment Share on other sites More sharing options...
bfin Posted December 11, 2014 Author Share Posted December 11, 2014 actually, i'm not all that knowledgeable in this area. but if you'll look at what haystack replied that should give you some help. or get your friend's isp to send out a technician. but as it was suggested to me......make sure its one from the provider not a sub-contractor. as the former should have more knowledge than the latter. i'm learning as i go myself. Finlai legacy Kuzordin 60 Guardian, Kishtira 56 Powertech Link to comment Share on other sites More sharing options...
itsmymillertime Posted December 12, 2014 Share Posted December 12, 2014 How did you do this trace? I'm trying to help a friend who is having problems staying connected to the server. He's done a trace and the IP giving him problems is 4.28.172.102 According to customer service helping him that IP is dropping 100% of his data. Any help with any of this would be appreciated. Thanks. Its a level 3 server: https://db-ip.com/4.28.172.102 Link to comment Share on other sites More sharing options...
Haystak Posted December 13, 2014 Share Posted December 13, 2014 How did you do this trace? I'm trying to help a friend who is having problems staying connected to the server. He's done a trace and the IP giving him problems is 4.28.172.102 According to customer service helping him that IP is dropping 100% of his data. Any help with any of this would be appreciated. Thanks. to issue a trace route command go to your command prompt...you can look it up in your windows start menu. once the command prompt is up type tracert http://www.google.com or any address that you want to know the route of. The first 3 to 6 entries are usually your ISP, and you can usually tell by what their IP addresses are. Link to comment Share on other sites More sharing options...
swredrage Posted December 17, 2014 Share Posted December 17, 2014 1 <1 ms <1 ms <1 ms 192.168.1.1 2 7 ms 8 ms 7 ms 10.189.88.1 3 18 ms 45 ms 10 ms 172.30.76.177 4 10 ms 10 ms 15 ms 172.30.32.69 5 28 ms 25 ms 32 ms cr2.attga.ip.att.net [12.122.140.170] 6 26 ms 23 ms 23 ms cr2.attga.ip.att.net [12.122.140.170] 7 27 ms 25 ms 28 ms 12.122.117.121 8 * * * Request timed out. 9 87 ms 88 ms 85 ms ae-2-70.edge8.SanJose1.Level3.net [4.69.152.84] 10 118 ms 84 ms 85 ms ae-2-70.edge8.SanJose1.Level3.net [4.69.152.84] 11 88 ms 85 ms 85 ms 4.28.172.102 12 85 ms 85 ms 85 ms 159.153.68.252 and this is what i got. your connection looks okay givin this trace route. Not amazing but not horrible either. the request timed out is NOT uncommon and nothing to concern yourself with as long as your getting to the end host. Many ISPs disable/block the ICMP protocol (what ping and tracert/traceroute use) on their routers for many reasons, one to help limit DoS attacks. when you have issues THEN run a tracert from the command prompt. You can also do a ping -t 159.153.68.252 when this happens as well. ctrl+c to stop the ping. I think someone else also mentioned this. Link to comment Share on other sites More sharing options...
Recommended Posts