Mikel
Topic Starter
I've been having some trouble experiencing lag shortly into online games, while other times the game is virtually lag free. I am running Vista 32-bit OS. I ran one test and the report that came up looked like this:
TCP/Web100 Network Diagnostic Tool v5.4.12
click START to begin
Connected to: nitro.ucsc.edu – Using IPv4 address
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 501.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 4.36Mb/s
Your PC is connected to a Cable/DSL modem
Alarm: Duplex Mismatch condition detected Switch=Full and Host=half <—- This part alarms me. I wikipedia'd 'duplex mismatch' and the symptoms it describes match closely to what might cause the lag in my games. Here is a quote from wikipedia about duplex mismatch:
'Communication is possible over a connection in spite of a duplex mismatch. Single packets are sent and acknowledged without problems. As a result, a simple ping command fails to highlight a duplex mismatch because single packets and their resulting acknowledgments at 1-second intervals do not cause any problem on the network. A terminal session which sends data slowly (in very short bursts) can also communicate successfully. However, as soon as either end of the connection attempts to send any significant amount of data, the network suddenly slows to very low speed. Since the network is otherwise working, the cause is not so readily apparent.
A duplex mismatch causes problems when both ends of the connection attempts to transfer data at the same time. This happens even if the channel is used (from a high-level or user's perspective) in one direction only, in case of large data transfers. Indeed, when a large data transfer is sent over a TCP, data is sent in multiple packets, some of which will trigger an acknowledgment packet back to the sender. This results in packets being sent in both directions at the same time.'
I also ran several infinite ping tests to my ISP's website (www.rogers.com) and every signal sent has timed out. Other websites have yielded fairly stable pings. Youtube.com ping test was also stable but resulted in timeouts every 30 pings or so.
Help?
Edit: Here is a tracert to www.rogers.com:
Tracing route to www.rogers.com [207.245.252.27]
over a maximum of 30 hops:
1 9 ms 9 ms 6 ms 10.116.0.1
2 8 ms 7 ms 7 ms vl-201.gw03.grnsbr.phub.net.cable.rogers.com [[removed]]
3 8 ms 7 ms 7 ms gi-1-1-0.gw01.grnsbr.phub.net.cable.rogers.com [[removed]]
4 42 ms 8 ms 8 ms so-4-0-0.gw02.mtnk.phub.net.cable.rogers.com [[removed]]
5 10 ms 9 ms 9 ms so-2-0-0.gw02.ym.phub.net.cable.rogers.com [[removed]]
6 10 ms 10 ms 8 ms gw01.mtmc.phub.net.cable.rogers.com [[removed]]
7 9 ms 9 ms 10 ms ge10-0.gwy2-tor.bb.allstream.net [[removed]]
8 10 ms 9 ms 9 ms ge-wan7-1.hcap4-tor.bb.allstream.net [[removed]]
9 9 ms 12 ms 12 ms [removed]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Here is a tracert to the game server I currently experience lag on:
Microsoft Windows [Version 6.0.6001]
Copyright © 2006 Microsoft Corporation. All rights reserved.
C:\Users\Michael>tracert useast.battle.net
Tracing route to useast.battle.net [63.240.202.139]
over a maximum of 30 hops:
1 8 ms 8 ms 9 ms 10.116.0.1
2 9 ms 15 ms 7 ms vl-201.gw03.grnsbr.phub.net.cable.rogers.com [[removed]]
3 8 ms 7 ms 7 ms gi-0-1-0.gw01.grnsbr.phub.net.cable.rogers.com [[removed]]
4 7 ms 9 ms 7 ms so-4-0-0.gw02.mtnk.phub.net.cable.rogers.com [[removed]]
5 11 ms 9 ms 11 ms gw02.ym.phub.net.cable.rogers.com [[removed]]
6 52 ms 50 ms 51 ms pos-3-0.igw01.chfdrl.phub.net.cable.rogers.com [[removed]]
7 50 ms 49 ms 49 ms so-4-1.ar5.CHI1.gblx.net [[removed]]
8 118 ms 67 ms 70 ms te4-2-10G.ar2.CHI2.gblx.net [[removed]]
9 35 ms 34 ms 35 ms [removed]
10 52 ms 53 ms 52 ms tbr1.cgcil.ip.att.net [[removed]]
11 55 ms 55 ms 55 ms cr1.cgcil.ip.att.net [[removed]]
12 55 ms 54 ms 53 ms cr1.cl2oh.ip.att.net [[removed]]
13 52 ms 50 ms 49 ms cr2.cl2oh.ip.att.net [[removed]]
14 56 ms 59 ms 55 ms cr2.phlpa.ip.att.net [[removed]]
15 53 ms 53 ms 51 ms cr1.wswdc.ip.att.net [[removed]]
16 58 ms 54 ms 55 ms tbr1.wswdc.ip.att.net [[removed]]
17 58 ms 52 ms 53 ms [removed]
18 57 ms 55 ms 55 ms 12-122-254-98.attens.net [[removed]]
19 65 ms 55 ms 55 ms mdf001c7613r0003-gig-10-1.wdc1.attens.net [[removed]]
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.