I think I have confirmed we ALL have W7, wi-fi issues

pampum said:

....Just a lot of people may not notice it much or be that bothered by it. Personnaly I cant stand it.

In short, wi-fi latency has gone from consistently under 1ms on XP, and vista AFAIK, to anywhere between 2-50ms. To your own router!

I have done many tests and pretty much isolated its the OS. I have tried it at friends places as well, and their windows 7 x64 does the same, ping's are around 3-8. They dont have that initial spike, but otherwise the same as me.

Give it a go, if you are running 7 preferably 64 bit 7, find your wireless routers IP address, open cmd from the start orb, and in there type

ping "your routers IP adress" -n 100

so bassialy if yor ip is 192.1.1.10 you type

ping 192.1.1.10 -n 100

And watch the pings roll by.

Heres the aboslute best results I have gotten. Pings are worse now, about 3,4 4, 6, 4, 3 etc.

Anything over 1ms consistently is just a joke.

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=44ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 44ms, Average = 12ms

check out my thread as well

Extremely poor Wi-fi performance in 7. Max signal. W7 constantly scanning wi-fi? Is it W7?

Lets try get a fix going. This is ridiculous. Is this the future of computing, laggier networking performance?

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

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64

Ping statistics for 192.168.0.1:
Packets: Sent = 18, Received = 18, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 3ms, Average = 0ms
Control-C
^C

No issues here. Recipe:
$25 draft-n router
Newegg.com - Rosewill RNX-EasyN400 IEEE 802.11b&#47;g&#47;n Wireless-N Draft 2.0 compatible Broadband Router &#40;1T1R&#41; Up to 150Mbps Data Rates&#47; WPA Personal and Enterprise, WPA2, 64 &#38; 128 bit WEP, PSK, TKIP, AES, WPS Security with 2 dBi
$17 g wifi pci card
Newegg.com - Rosewill RNX-G300EX IEEE 802.11b&#47;g PCI Wireless Card Up to 54Mbps Data Rates 64&#47;128-Bit WEP, 802.1x, WPA, WPA2, AES, TKIP with 100cm cable external 2 dBi Antenna - Wireless Adapters
54Mbps link, full bars signal from the other side of the house through several walls. See my system info below for more info.

pampum said:

I think I have confirmed we ALL have W7, wi-fi issues
....Just a lot of people may not notice it much or be that bothered by it. Personnaly I cant stand it.

Simply not true. If I have a problem, I would not even think to state 'Because I have a problem, it's confirmed we all have a problem!'.

Kari

pampum said:

Well this is good news then it mens there is a possible solution. I assumed everyone has it like this becasue I trried it on 3 sepearte setups, not within my home and 7 always all had these bad results!
Simply trying xp on the same setup worked fine, it seemend imposible for the culprit not to be 7. I think my assumption was reasnable because of so many repeat tests. Plus I said "I THINK"

I have no idea what you guys ahave different and i have tried everything with no luck ?

So this is definitely pining the wireless router?


All mine were tested on G. the signal has nothing to do with it btw.

So what settings,for your windows and wirelss drivers are you guys using?

I think the problem is windows is scanning wi-fi networks on the fly, it doesnt connect and lock on like XP does.

Some drivers default to aggressive channel scans. Lock your router and nic to the same address, usually 11.

pampum said:

baarod, i have set everything to full 54g, locked onto it. Nothing is set to auto or scan. Speed is full 54g max signal.

My wirelss laptop card is 4965AGN. Roaming agrresiveness etc have treid from low to high makes no diff.

Actually to all those not having problems, are you guys trying it on laptops?

I even installed

Home-WLAN Optimizer - Optimize wireless gaming, audio and video streaming...

with no help.

Just tried on my EeePC 1000HE. Clean pings.