Does Vista have a Bug in it's Wireless Networking?


Recommended Posts

  Sleeper said:
well this is my ping i did to my router over a period of about 4/5 mins during which the signal strength was Excellent....

Pinging 192.168.0.1 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=50ms TTL=64
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=17ms TTL=64
Request timed out.
Reply from 192.168.0.1: bytes=32 time=13ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
Reply from 192.168.0.1: bytes=32 time=21ms TTL=64
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=21ms TTL=64
Request timed out.
Reply from 192.168.0.1: bytes=32 time=13ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Request timed out.
Reply from 192.168.0.1: bytes=32 time=15ms TTL=64
Reply from 192.168.0.1: bytes=32 time=21ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.

I used to get that on my wireless network on my desktop, that and the odd ping coming back at 2000ms +, in the end i switched the desktop from wireless to a powerline network, which works a lot better.

although mine was no where near as bad as that.

After using ethernet cable for a while I tried my wireless again. So now it didn't take that long before the problem occured.

It knocked out my internet/router for about 30 min. What I could see in the router logs, the router couldn't renew it's DNS address. And the IP from the ISP didn't work either. I got a local address instead, 192. etc. Very strange. Removing the power cable didn't work.

Also I couldn't recieve IP or anything from my router myself.

So this must only be related to wireless only. I had some small hick ups on the ethernet cable aswell, but that's nothing compared to this.

well done some futher trouble shooting on mine and found that if I change the security on the router from WPA-PSK to unsecured the pc works fine... so could it be a issure with the drivers for the usb wireless adapter dealing with WPA..... hmmmmmmm

I also get that problem here alot.

For the record, I'm using Vista RTM, and also using WPA-PSK security. With mine, it will be perfect for a certain period of time, sometimes the DNS fails, and sometimes the connection drops altogether. I've tried using an external USB, and also using my old router, and it does the same. Fine over a wired conneciton though.

As for the ping, my ping seems to be fine (while working) although the odd one does shoot up to 160-ish MS

I'm only using WEP for now though (no real need for more around here), but I could change to WPA-PSK when I come home from work and do some tests. I doubt this is a driver issue. Seems more related to the router software. Like it would be needing a firmware update. I don't know how Vista's network traffic is compared to XP/2K, but since the stack is different mabye routers have trouble.

I don't use wireless so I can't confirm if this works, but I noticed a couple of hotfixes that might be related to the problem.

http://www.microsoft.com/downloads/details...;displaylang=en

http://support.microsoft.com/kb/929451/en-us

More Vista hotfixes here:

http://www.vistasp1.net/

http://aaron-kelley.net/downloads/hotfix/

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.