P4P800-E Deluxe/Asus Wifi-b problems

  • Thread starter Thread starter Frankie Howerd
  • Start date Start date
F

Frankie Howerd

Had trouble with this combo since I set it up, trying to use the wifi-b card
to connect to my wireless network provided by a Linksys router upstairs.
Seemed to work well at first, connection speeds reporting as expected, but
before long my net connection slowed to a crawl. I had installed some
Logitech Quickcam drivers/software, so I reinstalled the Wifi-b drivers and
things seemed back to normal again. Last night I installed some stuff from
the WindowsUpdate site, on reboot the net connection back to a crawl.
Reinstalling the drivers doesn't fix the problem. The Wifi-b utilities
report significant (30-40%) packet loss. Any ideas, other than shitcanning
the proprietary Asus card and switching to a more generic pci wireless lan
card? (I also have a laptop than connects to the wireless network with no
problems from the same location as this machine, so the network/reception
location itself is presumably OK.)
 
"Frankie Howerd" said:
Had trouble with this combo since I set it up, trying to use the wifi-b card
to connect to my wireless network provided by a Linksys router upstairs.
Seemed to work well at first, connection speeds reporting as expected, but
before long my net connection slowed to a crawl. I had installed some
Logitech Quickcam drivers/software, so I reinstalled the Wifi-b drivers and
things seemed back to normal again. Last night I installed some stuff from
the WindowsUpdate site, on reboot the net connection back to a crawl.
Reinstalling the drivers doesn't fix the problem. The Wifi-b utilities
report significant (30-40%) packet loss. Any ideas, other than shitcanning
the proprietary Asus card and switching to a more generic pci wireless lan
card? (I also have a laptop than connects to the wireless network with no
problems from the same location as this machine, so the network/reception
location itself is presumably OK.)
Click to expand...

For a start, I would want to go back through the stuff you added
via Windows Update, to see if there is anything there network
related.

I know it is a lot of work, but I install updates one at a time.
Just so I can observe if something isn't working well after
doing an update. Keeping records of the id number for a patch
will enable you to Google on the patch number, as some of
them caused a lot of problems.

Would this have something to do with a firewall somewhere and
certain blocked ports ? I'm not sure how to interpret the
30-40% packet loss - whether that is at a physical level,
or is measured somewhere else.

Maybe you can fix this by using a restore point ? Not that
I've ever restored from one of those myself.

Paul
 
Back
Top