|
Mmm - doesn't seem much wrong there. If your other AP exactly matches those settings then it should work. However, here's a few suggestions.
If possible, enable both TKIP and AES/CCMP/RSN (the latter goes by different names.) TKIP was a klugde to get around "broken" WEP security using WEP hardware. Increasingly everything is moving to AES. If all your client devices support AES, I'd dump TKIP entirely (on both routers.)
Not much uses "B" wifi these days. If none of your clients need it, I'd also turn that off. (I don't think that's the cause of your problem, but it's good housekeeping.)
By way of a test, give your AP's different SSID's temporarily and check that your clients really can associate with both AP's successfully when the only difference between them is the SSID name.
Turn off "N" temporarily and test if it works in a "G" only environment. Likewise, test with "N" only. The G spec was/is more prescriptive about it's implementation and there's not much leeway for interpretation. "N" has a lot more "options" available to the implementors, so it's possible that you're client likes one AP's "N" implementation but not the other. Or it's possible the AP's are offering up variants of N so different to each other that the client won't regard them as "similar" enough to be able to flip from one to the other.
Make sure both AP's are on very different radio channels so they don't interfere with each other.
If everything talks WPA2, ditch WPA and take any incompatibilities there out of the equation.
Ultimately it may be down to some methodical slogging through all the options to find out what works and what doesn't. Sometimes IT problems are "just like that" and there's nothing for it but to roll up ones sleaves and slog though changing/testing one thing at a time until the culprit/solution is found. |
|