EAP 225 WiFi 2.4Ghz AP on b/g/n mode not compatible with legacy devices
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.EAP 225 WiFi 2.4Ghz AP on b/g/n mode not compatible with legacy devices
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I have the EAP configured as b/g/n for 2.4Ghz WiFi AP, and a few legacy devices on the network are having trouble using the EAP 225.
The legacy devices will either:
A) not see the WiFi AP at all (cant find SSID) or
B) see and connect to the SSID, get an IP from the DHCP server, but not be able to transmit any packets after that (even ARP [ping] won't get through).
One device is a Dell laptop (Windows 10) which has an Intel Centrino-N2230 wireless card. This guy can't see the EAP225 at all (case "A" above)...
Another device is a Grace Digital Radio (GDI-IRD4500M). This is an internet radio. This device behaves as case "B" above. Which is weird... Why would it be able to attach to the SSID, go through the whole DHCP sequence and obtain an address from the DHCP server on the network, but yet not be able to send/receive ANY packets AFTER that?!?
Anyway, any help would be appreciated.
PS. All the devices, including the 2 above, which have issues with the EAP225 work just fine with other b/g/n WiFi APs/Routers on 2.4GHz, such as netgear WNDR3800.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@jorgeC I had similar issue on the 2.4GHz radio with my audio system which crashed, or lost connection or "disappeared" after appr. 10-12 hours. The root cause was the one Wireless setting of the EAP225 called "Airtime Fairness". Once disabled my audio system/internet radio works perfectly fine.
- Copy Link
- Report Inappropriate Content
Woohoo... @jonas and the TP-Link guys fixed my issue. They had a look at all the wireshark traces I took and figured out that the issue I had was with some of these client devices which have legacy drivers (and which can't be udpdated) not handling the signaling that is used when the "20/40" bandwidth setting is enabled.
TP-Link will be releasing a firmware update that includes the fix for this issue some time soon.
In the meantime, if you are having issues similar to mine, you can check if "20/40" is enabled and try disabling it. I did check that doing that worked for me but obviously that's not the ideal solution, just a temporary one.
Thanks Jonas! You guys showed a lot of customer focus in working on this issue and that's what will keep us being repeat customers. :-)
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 5859
Replies: 12
Voters 0
No one has voted for it yet.