Lewis G Rosenthal wrote:

Once connected, I turned off beaconing in the AP. The notebooks continued to work for the rest of the time I was there. I had a workstation downstairs with an older LinkSys PCI card in it, which I upgraded (the new card was defective, and kept dropping the signal; a subsequent replacement resolved the issue). A couple days later, my client called me to tell me that he couldn't get either of the notebooks to connect. After a few minutes on the phone, I had him log into the WRT54G from his wired desktop and turn beaconing back on. This seemed to resolve the problem.

I know we have kicked around on this list various issues with GenMAC and non-beaconing AP's. I generally do not have a problem, but I was wondering whether I missed a change in the RFC's somewhere? The workstation downstairs with the LinkSys PCI card had no trouble once I set up the profile with the (rather long) PSK. I was able to reboot several times and get right onto the network.

I don't know if an RFC changed but I have WPA2 and beaconing off and I find on my T42 that I often have to force the connection with Genmac (reboots often just reconnect but if I connected to any other network it won't connect on its own).  If I boot into the XP sp2 partition then Access Connections seems to always pick it up but I do that rarely enough for it not to be a fair test.  The T60 from work with XP sp2 I generally have to tell Access Connections to connect to it as it won't connect on its own.