Problems with wireless and an HP Laptop

[mark]

Trying to connect an brand new HP Pavillion dv6527ea laptop with Vista Home Premium wirelessly to a Netgear DG834G v3

Without any security enabled the laptop connected fine. Enable security and it wouldn't connect, using every setting. Tried removing security again and still wouldn't connect. Re-booted everything lots, removed the Broadcom hardware, re-booted - nada.

Installed an updated driver for the Broadcom WLAN adaptor - and we had unsecured access again!! yay! ...tried enabling security again and it wouldn't connect again! - and the same as before, whatever I did, re-installing these drivers nothing would work.

I removed Norton Internet Security, which hadn't been installed yet (never underestimate the foobar powers of Norton :P) and the HP Wireless assistant. Also I disabled the Windows firewall.

I'm thinking it's got to be a problem with the driver, but can find no other record on the web, tho' my google powers are weak

Any ideas?

[OutToLunch]

Not speaking from direct experience, but I'm sure this has been mentioned recently as being related to a bug in Vista? I remember the thread but not enough keywords to dig it up for you... Something about laptops/WPA/vista/XP :S

Edit:
http://support.microsoft.com/kb/932063
http://www.edugeek.net/index.php?nam...wtopic&t=11380

HTH

[mark]

Cheers- will look them up

[mark]

Does anyone have that MS hotfix linked above that they're willing to share?

n/m it's here: http://thehotfixshare.net/board/inde...&showfile=3381

[Psymon]

We had a problem with the firmware on the wireless module. Updated the firmware and Vista was able to connect no probs.

Si

[contink]

Found this little nugget following a phone call from my father who's been wasting two days trying to resolve two wireless adapters not talking to a D-link router.

http://www.reviewingit.com/index.php/content/view/61/1/

No idea how well it works but it basically sorts problems with DHCP.

This is for Vista (any version) specific wireless issue. On some routers it appears that the default forced broadcasting is no supported thus causing the DHCP allocation to fail. In consequence, and APIPA (Automatic Private IP Allocation, always 169.254.x.x) address is received. This does not allow access to the internet.

Editing the registry and disabling the force bcast resolved the problem.
The following 3 entries are needed:
With Encryption and without.
DhcpConnDisableBcastFlagToggle 1 - must be added manually
DhcpConnBcastFlagToggle 0 - must be added manually
DhcpConnForceBroadcastFlag 0 - must be changed from its default.

The following MS article partially addresses this flaw:
http://support.microsoft.com/kb/928233

Reference: http://notgartner.wordpress.com/2007...ireless-stack/