The average gamer between us, having a wireless connection, might experience latency spikes in their multiplayer games. It's quite frustrating when you're about to frag someone, they shoot you instead 🙂

We could blame the router, the wireless adapter or the OS. I tried two different wireless adapters which didn't solve the problem. I tried different computers, but still no go.
So, for months, I thought the blame was on my router which wasn't sending a consistent signal. Even when a new router came in with QoS support (a D-link DSL-2740B for those who are interested 😛 ) I still experienced lag each ~minute.

When pinging the router, you can see an extremely high ping result aka lag in the command prompt.

> ping -t 192.168.1.1

Antwoord van 192.168.1.1: bytes=32 tijd=3 ms TTL=64
Antwoord van 192.168.1.1: bytes=32 tijd=3 ms TTL=64
Antwoord van 192.168.1.1: bytes=32 tijd=1065 ms TTL=64
Antwoord van 192.168.1.1: bytes=32 tijd=3 ms TTL=64
Antwoord van 192.168.1.1: bytes=32 tijd<1 ms TTL=64
..........
Antwoord van 192.168.1.1: bytes=32 tijd=5 ms TTL=64
Antwoord van 192.168.1.1: bytes=32 tijd=1707 ms TTL=6
Antwoord van 192.168.1.1: bytes=32 tijd=4 ms TTL=64
..........

You can't find anything on the net but useless advice on this issue.

Now here's the key:
Windows has an implemented wireless configuration tool, the "Wireless Zero Configuration Service". This service automatically loads on startup and is the dialog you use to connect to your wireless network. Every minute the service will scan all wireless channels in an attempt to find wireless networks. However, this scanningprocess will cause the lag spikes. Blame microshit.

How to solve:
Disable the Wireless Zero Configuration Service by going to the Configuration Panel > Administrative Tools > Computer Management > Services.
You can also do this by fireing up a Run-dialog, and typing "net stop wzcsvc".

If you want to use the wireless configuration tool again after you're done gaming, you'll have to do the reverse process or "net start wzcsvc".
You can also create shortcuts on your desktop ofc or use an alternate configuration client.

> ping -t 192.168.1.1

Antwoord van 192.168.1.1: bytes=32 tijd=3 ms TTL=64
Antwoord van 192.168.1.1: bytes=32 tijd=4 ms TTL=64
Antwoord van 192.168.1.1: bytes=32 tijd=2 ms TTL=64
Antwoord van 192.168.1.1: bytes=32 tijd<1 ms TTL=64
Antwoord van 192.168.1.1: bytes=32 tijd=1 ms TTL=64
Antwoord van 192.168.1.1: bytes=32 tijd=1 ms TTL=64

GL/HF! 8)