James, I experienced the same behavior with Intel 2200 b/g adapter. Key negotiation worked correctly, but when it came time to pull a DHCP address it stalled. I have DHCP using static tables for address assignment. After much trial and error, I found that when I removed the 2200's card from the static DHCP list, I could get an address everytime and comunicate normally. I am able to reproduce this behavior at will. I was (and still am) going to dig a little deeper into the DHCP negotiation to see what is different on the client end when the server has a static table. There must be something since turning it off for that MAC address resolved the problem. My AP is using WPA-PSK TKIP encryption. I have not tested this using WEP, WPA2-PSK, or unencrypted. After I decode the DHCP with and without a static table on the server side, I will try testing with these. Phil On 3/15/06, James Garrison <jhg@xxxxxxxxxxxxxxx> wrote: > I installed the latest MS patches and after rebooting, my wireless > network refused to connect. It still showed excellent signal strength > but was unable to establish a connection. I tried using both the > adapter's client (Intel PRO Set) and the standard Windows client, > with identical results. > > Then I uninstalled the patches and this fixed the problem. > > The patches that were installed and then removed were: > > 913807 > 905756 > 913161 > 912945 > 904942 > 912475 > > I'm in the process of opening a call with MS, and will post > more information when it's available. > > -- > James Garrison Athens Group, Inc. > mailto:jhg@xxxxxxxxxxxxxxx 5608 Parkcrest Dr > http://www.athensgroup.com Austin, TX 78731 > PGP: RSA=0x92E90A3B DH/DSS=0x498D331C (512) 345-0600 x150 > > >
