@dunxd 

Do not use more than 1 Adapter, you can only use one adapter but more extenders .. I had the same problem.  Now dhcp works fine and takes settings from my firewall... 

one AC phase = one adapter (box without wifi) :)) but you can use more extenders :)

@ales  Is this based on your observation or advice from TP-Link support?

It is the WiFi access point models that can act as DHCP servers, not the powerline only models. Power line only models don't have any TCP/IP functionailty as far as I can tell, so I'm not sure how they would cause DHCP to be switched on a different device.

I got the same Problem on a WPA8630P...

Avery month these suckers loose their powerline connection and after rebooting one of them acts as an dhcp server...

Took a while to figure this out.

Ive thrown them out, as it looks like there is no solution. Rebooting every machine isnt a real solution.

8360 model here.  Windows domain network.  My primary DHCP server is offline, and secondary has a 2ms delay.  Apparently this is enough for the 8360 to decide to service clients.

Fix this guys.  DHCP should only service it's own wirelss/switch port clients, and be configurable.  I know you can do it.

Adding my voice that this is unacceptable behaviour on my TL-WPA7510.

I'm considering returning it.

My vote also for TL-WPA4220. Please add option to disable DHCP server, or just disable it completely.

Another option is lowering the interval at which TP-Link powerline devices check for other DHCP servers on the network.

For example, instead of checking every 20 minutes, make it check every 10 seconds or even less, since these devices are clearly not designed to be routers.

It seems the purpose of the DHCP server is to ease the configuration of the devices, but it is introducing highly disruptive behaviour if it boots up before a router.

I actually redesigned my network to connect my router to a UPS just avoid encountering this nonsense again.

This just happened all of the sudden while adding a third TL-WPA4220 to my network.

I have the TL-PA4010 connected to to the router so this is the kit option sharing the routers wifi and using the WiFi-move = ON.

Problem:

After pairing the new devices with the PA4010 Internet broke and another WPA4220 all of the sudden started sharing itself as gateway 192.168.0.254.

Reason:

I figured out that I failed on the pairing, holding the button on PA4010 too long, waiting for LED to start blinking.

So when I pressed the pairing button on new WPA4220 I initiaded pairing from "wrong direction/device".

Solution:

Just redo all the pairing with PA4010 for ALL devices. I.e I plugged the new device back in the closest outlet and it worked.

I went and got the other two (one at time!) WPA4220 and plugged in to the closest outlet of the PA4010 and paired again.

Voila, network restored.

Hope this helps someone as this thread helped me figure out where I went wrong in the installation.

Happy Networking everyone :)