Network Issues (High Latency playing Warcraft)

Smedly · Nov 5, 2012

Hey guys

This problem has been going on for about a week now and I know it's not your guys problem but I was wondering if anyone was around who knew a bit about latency problems and could give me a hand. My Pathping does not work (Cos my router blocks the results) so I can only give my tracert, etc.

I have been talking to some Network Technician and he told me to download a programme called DPClat and it tests to see if my Devices are interrupting my network and as he told me, they are, but I don't know what to disable without breaking my PC and I have tried updating them all but it says they are fine. Quite a few people are experiencing these latency problems but all my friends aren't so i'm just worried. Can anyone take a look? Thanks in advance

Some info:

ISP - SKY Broadband
Country - United Kingdom
Router (and firmware version if known) - DSL-2640S D-link (I think) Version - 2.8Sky
Network device (Driver version if available) - Intel(R) 82579V Gigabit Network Connection & Atheros AR9485 WIreless Network Adapter
Type of connection used (Wireless / USB / Ethernet) - Ethernet
Operating System - Windows 7 64bit
Security Software installed (Firewall, Anti-Virus) - Windows Firewall (Off) Avast! Anti Virus

This was me pinging the World of Warcraft server when my latency was GREEN and fine

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>ping -n 100 80.239.179.95

Pinging 80.239.179.95 with 32 bytes of data:
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Request timed out.
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=51ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=54ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Request timed out.
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=54ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=54ms TTL=51
Reply from 80.239.179.95: bytes=32 time=54ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=58ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=54ms TTL=51
Reply from 80.239.179.95: bytes=32 time=55ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=55ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=54ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Request timed out.
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=84ms TTL=51
Reply from 80.239.179.95: bytes=32 time=76ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=56ms TTL=51
Reply from 80.239.179.95: bytes=32 time=66ms TTL=51
Reply from 80.239.179.95: bytes=32 time=84ms TTL=51
Reply from 80.239.179.95: bytes=32 time=59ms TTL=51
Reply from 80.239.179.95: bytes=32 time=63ms TTL=51
Reply from 80.239.179.95: bytes=32 time=70ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=64ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=77ms TTL=51
Reply from 80.239.179.95: bytes=32 time=69ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=55ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=61ms TTL=51
Reply from 80.239.179.95: bytes=32 time=60ms TTL=51
Reply from 80.239.179.95: bytes=32 time=74ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=78ms TTL=51
Reply from 80.239.179.95: bytes=32 time=54ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=54ms TTL=51
Reply from 80.239.179.95: bytes=32 time=76ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=68ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=76ms TTL=51
Reply from 80.239.179.95: bytes=32 time=54ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=60ms TTL=51
Reply from 80.239.179.95: bytes=32 time=65ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=72ms TTL=51
Reply from 80.239.179.95: bytes=32 time=96ms TTL=51
Reply from 80.239.179.95: bytes=32 time=55ms TTL=51
Reply from 80.239.179.95: bytes=32 time=61ms TTL=51
Reply from 80.239.179.95: bytes=32 time=67ms TTL=51
Reply from 80.239.179.95: bytes=32 time=74ms TTL=51
Reply from 80.239.179.95: bytes=32 time=86ms TTL=51
Reply from 80.239.179.95: bytes=32 time=75ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=74ms TTL=51
Reply from 80.239.179.95: bytes=32 time=118ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=62ms TTL=51
Reply from 80.239.179.95: bytes=32 time=90ms TTL=51
Reply from 80.239.179.95: bytes=32 time=69ms TTL=51
Reply from 80.239.179.95: bytes=32 time=67ms TTL=51
Reply from 80.239.179.95: bytes=32 time=54ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=65ms TTL=51

Ping statistics for 80.239.179.95:
Packets: Sent = 100, Received = 97, Lost = 3 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 118ms, Average = 59ms

(waiting for part 2 to be approved by an admin)

Smedly · Nov 5, 2012

This was my latency when my latency was RED and HIGH in game (it was saying I had 3000ms)

C:\Windows\system32>ping -n 100 80.239.179.95
Pinging 80.239.179.95 with 32 bytes of data:
Reply from 80.239.179.95: bytes=32 time=54ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=54ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=55ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=54ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=54ms TTL=51
Reply from 80.239.179.95: bytes=32 time=54ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=54ms TTL=51
Reply from 80.239.179.95: bytes=32 time=54ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=51ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=51ms TTL=51
Reply from 80.239.179.95: bytes=32 time=54ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=51ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=54ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=59ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=54ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=51ms TTL=51
Reply from 80.239.179.95: bytes=32 time=54ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=54ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=54ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=52ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=53ms TTL=51
Reply from 80.239.179.95: bytes=32 time=54ms TTL=51
Ping statistics for 80.239.179.95:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 59ms, Average = 52ms
C:\Windows\system32>

Tracing route to 80-239-179-95.customer.teliacarrier.com [80.239.179.95]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms myrouter.home [192.168.0.1]
2 * * * Request timed out.
3 52 ms 47 ms 47 ms ip-89-200-131-115.ov.easynet.net [89.200.131.115]
4 49 ms 47 ms 51 ms ip-84-38-37-96.easynet.co.uk [84.38.37.96]
5 45 ms 45 ms 44 ms 195.50.122.113
6 46 ms 75 ms 45 ms ae-1-51.edge5.London1.Level3.net [4.69.139.75]
7 44 ms 45 ms 45 ms ldn-b5-link.telia.net [213.248.91.57]
8 45 ms 44 ms 159 ms ldn-bb1-link.telia.net [80.91.246.144]
9 53 ms 53 ms 53 ms adm-bb4-link.telia.net [213.155.130.90]
10 54 ms 53 ms 97 ms adm-b5-link.telia.net [80.91.253.186]
11 54 ms 53 ms 53 ms 80-239-179-95.customer.teliacarrier.com [80.239.179.95]
Trace complete.

(Telia is Blizzards servers) This is my tracert during lag :S

Please remember, this lag ONLY HAPPENS IN WORLD OF WARCRAFT, NOT IN ANY OTHER GAME!

Here are some screenshots of that programme in action, the red bar means I have a device problem :S (apparently)

Marks · Nov 5, 2012

Ping has started…

PING 80.239.179.95 (80.239.179.95): 56 data bytes
64 bytes from 80.239.179.95: icmp_seq=0 ttl=54 time=46.718 ms
64 bytes from 80.239.179.95: icmp_seq=1 ttl=54 time=45.530 ms
64 bytes from 80.239.179.95: icmp_seq=2 ttl=54 time=44.488 ms
64 bytes from 80.239.179.95: icmp_seq=3 ttl=54 time=46.824 ms
64 bytes from 80.239.179.95: icmp_seq=4 ttl=54 time=45.824 ms
64 bytes from 80.239.179.95: icmp_seq=5 ttl=54 time=44.560 ms
64 bytes from 80.239.179.95: icmp_seq=6 ttl=54 time=46.448 ms
64 bytes from 80.239.179.95: icmp_seq=7 ttl=54 time=45.986 ms
64 bytes from 80.239.179.95: icmp_seq=8 ttl=54 time=46.139 ms
64 bytes from 80.239.179.95: icmp_seq=9 ttl=54 time=45.389 ms

--- 80.239.179.95 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 44.488/45.791/46.824/0.772 ms

Is my result with virgin broadband.

This is wired however, just wired up a couple of days ago, i have found that wireless regularly has problems with short sections of delay.

Download this http://www.metageek.net/products/inssider/ and run it now, check for other networks that overlap your channel, the more that overlap the more your going to have problems. Also checkout the wireless signal strength where you use the computer. You may find sitting on different chair might get you a much better signal.

Just noticed you said the connection is wired.

You could do with connecting to your router and checking if you can monitor what is using the bandwidth.

You also shouldn't get any packet loss if your connection is good. Might be worth running speedtest and pingtest and finding out what results you get, this could help you build up a picture over time, you may need to speak to your provider, you can always do the IT favorite of turn it off and turn it back on again.

Smedly · Nov 5, 2012

Thanks for the reply.

I generally get 8MB with Sky and speedtests show 30-50ms all the time, everytime :S

I haven't turned off and on again my router yet haha

How does one connect to their router?

also I found a noobed up thing, my Intel Connection device wasn't updated to latest version >.< it was almost a year out of date :S lets see if this works

Smedly · Nov 6, 2012

Too good to be true I s'pose, the update didn't work :S

LFFPicard · Nov 6, 2012

Your ping results show no issues at all.
When you say WoW is pinging red in game to you your ping was only 52 to the server.

The conclusion I have come up with is it is either a add-on that is causing a issue or the WoW server. Try disabling all your add-ons on login and play again.
Also try a different server, I am on bronzebeard and never have a issue, infact my ping sits between 12-20.

You could also try making WoW an exception in Avast, its nto recommended incase you download a virus add-on but if you stick to Curse, wow interface etc you will be fine. Just make the WoW exempt to on-access scanning by Avast.

Hope this helps.

terhil · Nov 10, 2012

Have you downloaded Leatrix Latency Fix, works wonders for me when I play World of Warcraft

Network Issues (High Latency playing Warcraft)

Smedly

Active member

Smedly

Active member

Marks

Bronze Level Poster

Smedly

Active member

Smedly

Active member

LFFPicard

Godlike

terhil

Active member