I have a system with 5 EAP access points covering a fairly large area. I have two EAP245s, an EAP225, an EAP225-Outdoor, and I once had an EAP235-Wall covering the far end of the space. The wall unit was most approriate for that location because it gave me an extra wired Ethernet that I needed, but it did tend to cause minor issues because it did not support seamless roaming, so sometimes a device would take a long time to switch to or from this Access Point. I was doing some research recently and found that the newer EAP615-Wall has been released since this was installed, and it is basically the same thing but supports seamless roaming, so I purchased one and installed it in place of the EAP235-Wall.

I started experiencing very odd behavior on a couple of devices, and troubleshooting has led me to the EAP615-Wall as the definite source of the problem.

I have an Android phone and a Windows based Laptop that now will connect exclusively to the EAP615-Wall. They will not roam to another AP, and if I power off the EAP615-Wall they will fail to connect to the SSIDs provided by the other APs. They can 'see' the SSID still but will not connect, and give me an error if I try to force a connection. If I 'forget' the SSID and re-add it, they will connect using the other APs as normal until I power the EAP615-Wall back on. Once they have roamed to this AP the issue occurs again. Unfortunately this means that I have devices that for a fair section of the physical space my WiFI covers, they have either very slow WiFi or no WiFi at all because they are too far from the EAP615-Wall for an effective connection and they will not connect to the nearby AP as they should.

I have looked through the settings and cannot find anything that seems to apply to just this device that makes any difference. Is this a bug, or is this a defect with my particular unit?