I have seen this happen before also, but only with secured connections. I have never been able to nail down the actual cause, only the surrounding conditions. I had a wireless connection using Windows 2000 and my son was using XP. After applying SP2, it started acting like yours, yet mine didn't have any problems whatsoever. I tried rebuilding his, and it would work OK for awhile, but whenever it got "fixed" with the latest SP and hardware fixes, it would start acting like that. If the network was unsecured, there was no problem.
The only thing I can think of is that he got to some point where the computer could not calculate the encryption fast enough, or respond fast enough to the router and it would get forced off. Or possibly there was an error in the encryption algorithm that did not show up all the time.
You might try using a less robust algorithm and see if that improves things, or just go unsecure. You might try unsecuring the wireless but suppress the SSI broadcast. That might discourage others from piggy backing on your wireless.
I know this isn't much help, but it is about all I can suggest at this point. My son's problems went away when he got a faster computer, but unfortunately it runs Vista, so saying faster is what fixed it is not a sure thing since the OS is another variable in the mix.