Here are a couple of common ones and what you can do: You might not have to worry if you only see one or two asterisks on a hop, but if you have 3 like in the example above followed by Request timed out, you may have a network issue. If you see an asterisk (*) in place of an RTT, then a packet was not returned within the expected timeframe. Some of the rows, however, may look like this: Each hop is attempted 3 times, which is why there are 3 values for each row. Next to each row number is the Round Trip Time (RTT) in milliseconds-the amount of time it took for your packet (network data) to go from your computer to the endpoint of that hop. ![]() Below is a snippet of what each hop looks like in the log.Įach row starts with a row number-you can ignore that. ![]() The further you are from Riot's server, the more hops it will take. Each row in the tracert log shows how your data hops from one connection to the next until it reaches its destination. Instead, it has everything to do with how your data travels from your computer to Riot. The first line of the tracert output describes what the command is doing, and will look something like this:Ī hop in this case is unrelated to bunnies or your in-game movement. I got the log! Now how do I read this thing?
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |