I've had a Samsung Series 9 Ultrabook (NP900X4C-A01US) with an Intel 6235 card for just over a year, and have suffered the sporadic wireless drops for most if not all of that time.
I finally had time to focus on the issue and found this thread--all 49 pages of it! It's a TRAVESTY that Intel hasn't chimed in. From the variety of manufacturers and models, it seems highly probable that it's a driver problem.
For those who have just found this thread, and for my own benefit, I'm going to summarize some key takeaways, and then I'll update the thread with my experiences as I try to solve the problem.
- The Intel 6235 card seems to drop connectivity pretty regularly for a lot of people, on a lot of different devices. Folks have done solid troubleshooting/testing (as have I) to confirm that it's not a problem with their routers (e.g. every other device maintains connectivity). This is a REAL PROBLEM and neither Intel nor manufacturers have helped. [Kinda wish the MacBooks had 6235s cuz Apple users would set the Wall Street Journal on fire if this was affecting them!]
- Out of all the proposed and tried solutions, it seems that changing the driver is one of the most popular. Much older versions of the driver seem not to have this problem. Suggestions are that the bug was introduced when WiDi was added as a feature. Will try this...
- The other is to change wireless settings on the router--specifically setting a specific wireless channel, rather than "Auto."
What strikes me as interesting is that #2 and #3 actually are somewhat consistent with each other. I notice that my Netgear Push2TV says, very specifically, that the wireless router must be set to a specific channel and not to "auto." Seems like there's something in the WiDi spec that doesn't like Auto... That could explain the situation if either #2 or #3 fix the problem. Any thoughts?
So this is my "pre-troubleshooting" post... I will now try #3 then #2. More soon...