prowley79

Quick follow up: Meru had us turn off the Virtual Cell technology in the code, which affects how clients roam between bssid's. Also, we found two settings on the Ralink card that were disabled. The settings were Multimedia-Gaming Mode and Power Management. We enabled the multimedia mode (it was disabled) We set the Power Management to "CAM" or constantly awake mode, which WAS set to max power savings. Changes to our controller along with the two changes on the Ralink driver seem to have solved our issues. I hope my experience can be of some help to you as well!

Unfortunately, its back to the drawing board again w/Meru support. The changes made to our "beacon frame" setup have only made marginal improvements and the large portion of our 175 or so clients on the ProBook 4430 are still reporting poor performance. We directed students to a couple locations where we have LAN drops so they could complete several standardized tests this week. So, being able to gather more stats on the wireless performance has been hit and miss. I am asking Meru support to escalate to the next level of their support chain as we've wasted enough time gathering information and trying things. We need a real solution soon. I'm putting this on Meru because the issue didn't begin until we updated to a new controller.

We ran into this problem after upgrading our Meru wireless controller to their MC-4200 appliance. HP ProBook 4430s units that WERE connecting fine with our earlier Meru controller were suddenly experiencing issues. After much back/forth with Meru support, they adjusted our "beacon frame" settings on several APs across our enterprise. We are still in "testing mode" but hoping for good news based on the improved connections we saw today. After I learned of the change, I Googled "beacon Ralink" or some such combination and arrived at this site. Hoping my tip will help some of you who have struggled w/this issue!