I posted on a different character when the forums were buggy and wouldn’t let me post on any retail character. Similar to right now where the forums will not let me select a character from WoW Classic. They don’t even show up in my list. Here are the three links:
-BLZ51900322 Cannot Load into Kalimdor
-BLZ51900323 and BLZ51900322
-BLZ51900323 in Valdrakken and while Crafting
The post you referenced from July was about an entirely different issue.
You can follow the progression of the issue between the three threads. While I somewhat agree with your assertion that it is my computer, shouldn’t the same behavior be happening everywhere in the game world instead of such limited scope of locations and actions at any given time? Also, that is the first time I’ve tried a different computer so while an interesting datum, it is not yet conclusive.
To add to my confusion, while from the last 30 minutes, the tracert and pathping shown have less than 10% deviation from ones run last night and this morning. Are the shown connection issues between Cox and Blizzard enough to cause the streaming error only to affect Kalimdor? While I suppose that is possible, it would not make sense to me either.
Pardon the edits to invalidate all links, apparently I am not trust level 2 on these forums anymore.
C:>tracert 24.105.62.129
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 5 ms 2 ms 2 ms 192.168.0.1
2 12 ms 28 ms 8 ms -ip98-160-162-1.lv.lv.cox.net [98.160.162.1]
3 8 ms 8 ms 12 ms 172.28.239.134
4 9 ms 8 ms 8 ms 100.120.102.88
5 6 ms 8 ms 7 ms 100.120.102.24
6 12 ms 10 ms 13 ms -langbprj01-ae2.rd.la.cox.net [68.1.4.252]
7 12 ms 74 ms 11 ms 68.105.30.130
8 564 ms 241 ms 168 ms -ae1-br01-eqla1.as57976.net [137.221.68.33]
9 * * * Request timed out.
10 * * * Request timed out.
11 49 ms 52 ms 51 ms 137.221.69.81
12 54 ms 52 ms 55 ms 24.105.62.129
Trace complete.
C:>pathping 24.105.62.129
Tracing route to 24.105.62.129 over a maximum of 30 hops
0 LAPTOP-[192.168.0.251]
1 192.168.0.1
2 -ip98-160-162-1.lv.lv.cox.net [98.160.162.1]
3 172.28.239.134
4 100.120.102.88
5 100.120.102.24
6 -langbprj01-ae2.rd.la.cox.net [68.1.4.252]
7 68.105.30.130
8 -ae1-br01-eqla1.as57976.net [137.221.68.33]
9 * * *
Computing statistics for 200 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 LAPTOP-2K16C0PN [192.168.0.251]
0/ 100 = 0% |
1 7ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 12ms 0/ 100 = 0% 0/ 100 = 0% -ip98-160-162-1.lv.lv.cox.net [98.160.162.1]
0/ 100 = 0% |
3 9ms 0/ 100 = 0% 0/ 100 = 0% 172.28.239.134
0/ 100 = 0% |
4 10ms 0/ 100 = 0% 0/ 100 = 0% 100.120.102.88
0/ 100 = 0% |
5 11ms 0/ 100 = 0% 0/ 100 = 0% 100.120.102.24
0/ 100 = 0% |
6 — 100/ 100 =100% 100/ 100 =100% -langbprj01-ae2.rd.la.cox.net [68.1.4.252]
0/ 100 = 0% |
7 — 100/ 100 =100% 100/ 100 =100% 68.105.30.130
0/ 100 = 0% |
8 269ms 0/ 100 = 0% 0/ 100 = 0% -ae1-br01-eqla1.as57976.net [137.221.68.33]
Trace complete.
C:>tracert 137.221.105.2
Tracing route to 137.221.105.2 over a maximum of 30 hops
1 5 ms 3 ms 2 ms 192.168.0.1
2 8 ms 9 ms 8 ms -ip98-160-162-1.lv.lv.cox.net [98.160.162.1]
3 7 ms 10 ms 7 ms 172.28.239.134
4 7 ms 8 ms 7 ms 100.120.102.88
5 5 ms 6 ms 6 ms 100.120.102.24
6 16 ms 12 ms 12 ms -langbprj01-ae2.rd.la.cox.net [68.1.4.252]
7 15 ms 120 ms 46 ms 68.105.30.130
8 388 ms 178 ms 201 ms -ae1-br01-eqla1.as57976.net [137.221.68.33]
9 * * * Request timed out.
10 21 ms 17 ms 21 ms -et-0-0-0-pe02-swlv10.as57976.net [137.221.83.83]
11 18 ms 16 ms 19 ms -las-swlv10-ia-bons-02.as57976.net [137.221.66.19]
12 20 ms 22 ms 28 ms 137.221.105.2
Trace complete.
C:>pathping 137.221.105.2
Tracing route to 137.221.105.2 over a maximum of 30 hops
0 LAPTOP-[192.168.0.251]
1 192.168.0.1
2 -ip98-160-162-1.lv.lv.cox.net [98.160.162.1]
3 172.28.239.134
4 100.120.102.88
5 100.120.102.24
6 -langbprj01-ae2.rd.la.cox.net [68.1.4.252]
7 68.105.30.130
8 -ae1-br01-eqla1.as57976.net [137.221.68.33]
9 * * *
Computing statistics for 200 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 LAPTOP-2K16C0PN [192.168.0.251]
0/ 100 = 0% |
1 4ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 10ms 0/ 100 = 0% 0/ 100 = 0% -ip98-160-162-1.lv.lv.cox.net [98.160.162.1]
0/ 100 = 0% |
3 8ms 0/ 100 = 0% 0/ 100 = 0% 172.28.239.134
0/ 100 = 0% |
4 8ms 0/ 100 = 0% 0/ 100 = 0% 100.120.102.88
0/ 100 = 0% |
5 9ms 0/ 100 = 0% 0/ 100 = 0% 100.120.102.24
0/ 100 = 0% |
6 — 100/ 100 =100% 100/ 100 =100% -langbprj01-ae2.rd.la.cox.net [68.1.4.252]
0/ 100 = 0% |
7 — 100/ 100 =100% 100/ 100 =100% 68.105.30.130
0/ 100 = 0% |
8 158ms 0/ 100 = 0% 0/ 100 = 0% -ae1-br01-eqla1.as57976.net [137.221.68.33]
Trace complete.
This has me stumped because I can’t work the logic through any particular problem, even my own computer, because the behavior is inconsistent and shows possible issues in a bunch of different directions.