LoneWolf
Senior Member
Side hobby: I repair broken laptops and upgrade them sometimes as well for fun. I have one with a pretty normal Intel 3945ABG wifi card in it at the moment. In the house, I have the RT-AC66R, and I have a Buffalo WLI-TX4-AG300N wireless bridge for the SO's desktop and our color laser. I have the bridge set to connect on the 2.4GHz band because signal strength was much better on the 5GHz. Bridge is set to 40MHz (it can be hardware switch-selected between 20MHz/40MHz)
Oddly enough, the laptop with the Intel card can see both the 2.4GHz and 5GHz SSIDs (it of course, can't connect to the 5GHz one), but connecting it will more often than not kill the connection between the router and the bridge. I didn't have this issue with my previous router (which was dual-band but not simultaneous), a Buffalo WZR-HP-G300NH(v1), which I ran at 2.4GHz 40MHz; everything worked fine. My own laptop is connected to the 5GHz band, and there are no issues there.
Any suggestions? This was a problem on both the .266 and .270 firmwares, and while the Intel wifi card is old, I've not had a problem with them in the past, and I can't see why this should be happening. For grins, I replaced the card with another identical one, and that didn't fix it, so I know it's not a defective Intel card.
Oddly enough, the laptop with the Intel card can see both the 2.4GHz and 5GHz SSIDs (it of course, can't connect to the 5GHz one), but connecting it will more often than not kill the connection between the router and the bridge. I didn't have this issue with my previous router (which was dual-band but not simultaneous), a Buffalo WZR-HP-G300NH(v1), which I ran at 2.4GHz 40MHz; everything worked fine. My own laptop is connected to the 5GHz band, and there are no issues there.
Any suggestions? This was a problem on both the .266 and .270 firmwares, and while the Intel wifi card is old, I've not had a problem with them in the past, and I can't see why this should be happening. For grins, I replaced the card with another identical one, and that didn't fix it, so I know it's not a defective Intel card.