Hi I'm new to EE and have previously used powerline adapters for a garden room

[Trickydicky75]

Hi, I'm new to EE and my tplink av600 powerline adapters won't work in my garden log cabin, they previously did with sky, I think it is possibly because they are wpa2 and my new EE 7 router is wpa3. I don't want to spend on new wpa 3 powerline adapters if they don't work is there any recommendations to what powerline adapters that are wpa3 would work best with ee's new router and TV mini box. Any help much appreciated . Thanks in advance.

[Mustrum]

@Trickydicky75   yes you are barking up a wrong tree.

There have been reports of problems connecting to the LAN ports on some routers, but using a Gb switch inbetween the router and the first powerline has helped in some cases.

WPA2/3 is a router WiFi issue, but your powerline should have an ethernet connection to the router.

[Trickydicky75]

One end  of my power line is next to the router and is connected via ethernet?

[Trickydicky75]

All sorted now, went into router administrator web settings and set up a compatible network using WPA 2 instead of WPA 3 all devices including my old laptop now connect and the av600 power line adapters now work perfectly and I am able to use them to clone the WiFi, as I did previously with sky.

[Mustrum]

@Trickydicky75   glad to hear it is working for you now, and thanks for letting us know.

As per my suggestion in the first reply 😎

[JimM11]

@Mustrum Some day's just go better than other's, and sometimes it is better to say 😶!

[bobpullen]

---

@Trickydicky75 wrote:

It connects to the tv mini box  in the garden room from an ethernet from the powerline adapter, this periodically drops connection. No one can connect to the cloned WiFi from the powerline adapter in  the garden room, the message you get is access is denied due to router administrator. I've been on the router settings to no avail and have read it's a compatibly issue with av600 being wpa2 and new EE router being wpa3. Maybe I'm barking up the wrong tree?

---

You are not barking up the wrong tree.

That message is exactly what I would expect an Android device to do if it supports WPA3 and is instructed to connect to a WiFi network/SSID that it thinks should support WPA3 but is only offering WPA2 as a connection method.

Many newer devices will not like the security mechanism being demoted for a known Wi-Fi network. The symptoms differ but you can expect things like the Administrator message you've quoted on Android, a blunt "Unable to join network" message on iOS, WiFi username/password errors, or oddities where the Wi-Fi connection will seemingly drop unexpectedly after a period time. There can actually be problems going in the other direction too (WPA2 > WPA3) however, that's less common.

To get around the problem, you need to 'forget' and recreate the saved Wi-Fi connection on the affected device, or find a way to 'reset' it's network settings and start from scratch. In your scenario, this won't work though, as you have (had) two competing access points running simultaneously, one with WPA2, and one with WPA3-Personal-Transition. At some point, affected devices would associate with the WPA3 access point and you'd be back to square one again.

I see you've worked around it by using the Compatible WiFi network (which is configured to use WPA2). An alternative would have been to either acquire a Powerline adapter that supports WPA3-Personal-Transition (as you alluded to), or refrain from cloning the SSID on the far end of the Powerline link and configure to use a unique WI-Fi network name instead.

TL:DR: Running two WIFi networks, with the same network name/SSID but different WPA security mechanisms, is a very bad idea and will lead to problems.