Link to home
Start Free TrialLog in
Avatar of snobrdrt
snobrdrtFlag for Afghanistan

asked on

Vista and WEP

I have a client who uses WEP for all of their 10 offices. All of the offices have the same SSID with the same WEP key. They can walk into any office and connect with no reconfiguration.

I have walked into this situation. We all know that WEP is the LAST thing you want to use. Every question on this specific topic here on Experts Exchange has been answered by someone saying ... "USE WPA or BETTER!" That's not an answer.

This time I would like someone to ANSWER the question at the heart of the problem.

I have many people who CAN access the wireless using the WEP key with XP and Windows 7. But I have 2 who cannot which are using Windows Vista.

I tried a few fixes like disabling IPv6 on the adapter and going into the registry and turning the DhcpConnForceBroadcastFlag to "0". Nothing has worked.

When I make the router in an office use WPA in testing, it connects instantly. When I turn it back to WEP, it connects but gives me the generic 169.x.x.x address.

For those who say, go to WPA, we would have to go to all the offices, change all the wireless routers and then re-configure EVERY user. Not going to happen. At least right now.

Need a fix for this specific problem.
ASKER CERTIFIED SOLUTION
Avatar of CHutchins
CHutchins

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of snobrdrt

ASKER

Hahaha. I hear ya!

I'm a long time IT guy just for info purposes. So I've tried uninstalling, reinstalling, new drivers, old drivers ... the only think I have not tried is pulling out the Intel wireless application. I'll give it a try but the PROBLEM is something inherent to Windows Vista and WEP marriage.
Avatar of Craig Beck
Are you using a passphrase to enter the WEP key, or just standard HEX?  The latter is usually better.

Try using 40-bit WEP instead of 128-bit.
No real solution to actual problem BUT WPA was the real way to go, even though that path is a very large project.