Hi folks, I've got an odd problem; curious if anyone has ever seen this kind of thing. It has me stumped.
- wireless in my laptop (EMachines/Acer D620) is broadcom based
- have tried a number of different wireless routers, all give same behaviour with this laptop (belkin, linksys, etc)
- when it works, it works fine. But ..intermittently - problem with symptoms:
--- cmd->ping to "google.ca" - or other sites outside my router - returns the message, "hardware error"
--- cmd -> ping to IP address of my wireless router - pings work fine
--- DNS resolution is working, because if I do "ping google.ca" after "fixing network" (Clearing DNS cache among other things) - then it is able to tell me the IP of the host that is giving me "hardware error".
--- during this state, I can easily use my web browser to visit web management page of my router (192.168.XX.XX)
--- likewise, I can RDP connect to a windows Virtual Machine running on a test box (hard-cabled into the router, not connected via wireless) - so long as I make the RDP connection to an IP address
--- Once I'm on the RDP connection, I can browse the web from there perfectly; suggesting that the router itself is not having issues.
The fact that the wireless is able to do traffic .. but not traffic requiring name resolution ... is the weird part of this.
If I reboot my system, often the problem goes away. If I boot into Linux (XUbuntu, latest release - Karmic based) - then I never (!!) have this problem, so I am suspecting that it is an issue around the driver version for my wireless NIC. ie, if it was a true hardware issue, then I should expect Linux Wireless to be equally screwed up on this system.
My WinXP wireless driver is the one provided from EMachines support site for this laptop for WinXP. File / driver ver is called, "Wireless_Broadcom(4312)_v126.96.36.199_XPx86.ZI P"
I've tried similar slightly newer broadcom driver for this same chipset from other vendor (HP) but the driver failed to install cleanly. I'm not sure if there are any other generic / alternative (newer?!) driver available. This one was date-stamped 2007 which seems kind of old.