Home Network Community >
Powerline Adapters >
TL-WPA4220KIT and wifi extension problems: wrong ip-range
TL-WPA4220KIT and wifi extension problems: wrong ip-range
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
TL-WPA4220KIT and wifi extension problems: wrong ip-range
Posts: 1
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2014-02-14
2014-02-14 03:46:33
Posts: 1
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2014-02-14
TL-WPA4220KIT and wifi extension problems: wrong ip-range
2014-02-14 03:46:33
Tags:
Region : Sweden
Model : TL-WPA4220
Hardware Version : V1
Firmware Version :
ISP : Telenor
Hi,
I'm having problems using the TL-WPA4220KIT to extend my existing wifi network. I've tried both the "wi-fi clone" and manual setup way without success. My setup is as follows:
4G Modem/Router (D-link DWR-923) - [Cat6 lan cable] - TL-PA4010 - [electrical wire] - TL-WPA4220
The router is providing IP-addresses to the network (DHCP) in the range 192.168.1.(2 - 155), subnet 255.255.255.0
I've assigned a static IP to the TL-WPA4220 via the DHCP reserve ip functionality (MAC address - IP link) and set it to use the same SSID and encryption method + password as the main router.
If I connect a laptop via cable to the TL-WPA4220 everything works fine; I get internet access and good speeds. But when I try to connect on the wifi-network when I'm in the zone extended by the TL-WPA4220 I do not get internet access ... my iPad and iPhone just shows a spinning "connecting to network" circle and after a while when checking the network details I see that an IP-address in the 169.x.x.x, subnet 255.255.0.0 has been assigned.
It seems like the TL-WPA4220 is not re-distributing the main router's IP-addresses provided by DHCP, but instead picks them from "its own range". How do I fix this (the TL-WPA4220 should be a slave device to the router in all ways [SSID, encryption, DHCP, etc])?
[Bump] Do anyone have any input on this?
Solution
Model : TL-WPA4220
Hardware Version : V1
Firmware Version :
ISP : Telenor
Hi,
I'm having problems using the TL-WPA4220KIT to extend my existing wifi network. I've tried both the "wi-fi clone" and manual setup way without success. My setup is as follows:
4G Modem/Router (D-link DWR-923) - [Cat6 lan cable] - TL-PA4010 - [electrical wire] - TL-WPA4220
The router is providing IP-addresses to the network (DHCP) in the range 192.168.1.(2 - 155), subnet 255.255.255.0
I've assigned a static IP to the TL-WPA4220 via the DHCP reserve ip functionality (MAC address - IP link) and set it to use the same SSID and encryption method + password as the main router.
If I connect a laptop via cable to the TL-WPA4220 everything works fine; I get internet access and good speeds. But when I try to connect on the wifi-network when I'm in the zone extended by the TL-WPA4220 I do not get internet access ... my iPad and iPhone just shows a spinning "connecting to network" circle and after a while when checking the network details I see that an IP-address in the 169.x.x.x, subnet 255.255.0.0 has been assigned.
It seems like the TL-WPA4220 is not re-distributing the main router's IP-addresses provided by DHCP, but instead picks them from "its own range". How do I fix this (the TL-WPA4220 should be a slave device to the router in all ways [SSID, encryption, DHCP, etc])?
[Bump] Do anyone have any input on this?
Solution
TP-Admin wrote
Hi All,
TP-Link is aware of this issue. Following our research and investigation, we found that this issue due to some routers' default LAN IP is 192.168.1.1 which is the same as the TL-WPA4220_V1 default IP. So there will be IP address conflict when you first setup or reset the TL-WPA4220_V1. ( Our TL-WPA4220 will change its IP address after detecting IP address conflict, but there still will be a short IP address conflict. )
In order to help these customers who are affected by this reason our R&D have made a beta firmware ( TL-WPA4220_V1_180509_Beta ) to change the TL-WPA4220_V1 default IP from 192.168.1.1 to 192.168.0.254.
You can visit our official website try to download and upgrade the latest beta firmware to resolve this issue.
Note: After upgrading this firmware, you need manually reset this device to make it work.
For TL-WPA4220(EU/UK)_V1 : https://www.tp-link.com/en/download/TL-WPA4220_V1.html#Firmware
For TL-WPA4220(US)_V1 : https://static.tp-link.com/2018/201805/20180510/TL-WPA4220(US)_V1_180509(beta).zip
#1
Options
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Thread Manage
Announcement Manage
96 Reply
Posts: 791
Helpful: 25
Solutions: 0
Stories: 0
Registered: 2012-11-02
Re:TL-WPA4220KIT and wifi extension problems: wrong ip-range
2014-11-10 14:30:46
My kit is working OK. Have you tried to reset them and pair them again? Your devices are still under warranty, right?
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#22
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Announcement Manage
Posts: 3
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2014-11-21
TL-WPA4220 IP issues and internet issues - TL-WPA4220 Setup and solution
2014-11-21 23:56:35
Hello I had the same problem. Everything was running fine for 1 day. So I decided to test the throughput by using 4 PC's and 2 Phones steaming 4 1080P Bluray video locally, 8 Youtube HD test video 720P 1080P and 4K. I
then tried to connect the phones and I could not get an IP. Then I could not get an IP on any of my laptops or wireless devices. I tried to reset to factory defaults, updated firmware, restored my backup config files. But nothing worked.
I was about to take these back to the store but they were just working flawlessly!!
Solution:
( To save installation time and frustration, I would do this for the initial setup instead of plugging these into your wall jacks.)
I connected all of the adapters to my surge protector with nothing else connected to it the surge protector, plugged them in all in a row. Paired them 1 at a time (took only a few seconds).
Now I can get an IP without a problem. Unplugged them and plugged them back in and they worked right away. Make sure that you are plugging this directly into your router, not a switch.
I tested them for 24 hours now and all is good. I used TamoSoft Throughput test to test the WiFi and it did not drop signal at all. I tested streaming 4K video, 1080P, 720p, from yourtube and my DNLA media server on 4 computers, 2 phones, 1 samsung tablet, 55" vizio smart TV using DNLA streaming a blueray movie approx 5GB movie and everything worked. I was also able to send a 8GB file over with a transfer rate of 4.5Mbps during steaming to all the devices. Plus I could browse the internet without a problem. After sending the 8GB file, browsing my media server was slow (LAN side) but the internet was fine.
I am still testing them out but this definitely fixed my DHCP IP Addressing issue. (obtaining IP / Unknown Network / Discovering issues)
Try using your Android or iPhone to connect to the WiFi again.
I cloned these from my router using WPS and also manually cloned them using the Powerline Scan.exe tool from tp link.
Hope this helps!
I will update this soon. (November, 21 2014)
then tried to connect the phones and I could not get an IP. Then I could not get an IP on any of my laptops or wireless devices. I tried to reset to factory defaults, updated firmware, restored my backup config files. But nothing worked.
I was about to take these back to the store but they were just working flawlessly!!
Solution:
( To save installation time and frustration, I would do this for the initial setup instead of plugging these into your wall jacks.)
I connected all of the adapters to my surge protector with nothing else connected to it the surge protector, plugged them in all in a row. Paired them 1 at a time (took only a few seconds).
Now I can get an IP without a problem. Unplugged them and plugged them back in and they worked right away. Make sure that you are plugging this directly into your router, not a switch.
I tested them for 24 hours now and all is good. I used TamoSoft Throughput test to test the WiFi and it did not drop signal at all. I tested streaming 4K video, 1080P, 720p, from yourtube and my DNLA media server on 4 computers, 2 phones, 1 samsung tablet, 55" vizio smart TV using DNLA streaming a blueray movie approx 5GB movie and everything worked. I was also able to send a 8GB file over with a transfer rate of 4.5Mbps during steaming to all the devices. Plus I could browse the internet without a problem. After sending the 8GB file, browsing my media server was slow (LAN side) but the internet was fine.
I am still testing them out but this definitely fixed my DHCP IP Addressing issue. (obtaining IP / Unknown Network / Discovering issues)
Try using your Android or iPhone to connect to the WiFi again.
I cloned these from my router using WPS and also manually cloned them using the Powerline Scan.exe tool from tp link.
Hope this helps!
I will update this soon. (November, 21 2014)
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#23
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Announcement Manage
Posts: 3
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2014-12-12
Any update?
2014-12-12 16:19:37
napervilleitsolutions wrote
Hello I had the same problem. Everything was running fine for 1 day. So I decided to test the throughput by using 4 PC's and 2 Phones steaming 4 1080P Bluray video locally, 8 Youtube HD test video 720P 1080P and 4K. I
then tried to connect the phones and I could not get an IP. Then I could not get an IP on any of my laptops or wireless devices. I tried to reset to factory defaults, updated firmware, restored my backup config files. But nothing worked.
I was about to take these back to the store but they were just working flawlessly!!
Solution:
( To save installation time and frustration, I would do this for the initial setup instead of plugging these into your wall jacks.)
I connected all of the adapters to my surge protector with nothing else connected to it the surge protector, plugged them in all in a row. Paired them 1 at a time (took only a few seconds).
Now I can get an IP without a problem. Unplugged them and plugged them back in and they worked right away. Make sure that you are plugging this directly into your router, not a switch.
I tested them for 24 hours now and all is good. I used TamoSoft Throughput test to test the WiFi and it did not drop signal at all. I tested streaming 4K video, 1080P, 720p, from yourtube and my DNLA media server on 4 computers, 2 phones, 1 samsung tablet, 55" vizio smart TV using DNLA streaming a blueray movie approx 5GB movie and everything worked. I was also able to send a 8GB file over with a transfer rate of 4.5Mbps during steaming to all the devices. Plus I could browse the internet without a problem. After sending the 8GB file, browsing my media server was slow (LAN side) but the internet was fine.
I am still testing them out but this definitely fixed my DHCP IP Addressing issue. (obtaining IP / Unknown Network / Discovering issues)
Try using your Android or iPhone to connect to the WiFi again.
I cloned these from my router using WPS and also manually cloned them using the Powerline Scan.exe tool from tp link.
Hope this helps!
I will update this soon. (November, 21 2014)
Any update? Im having the same issue. Was going to add reservations for all devices via the Virgin HomeHub
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#24
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Announcement Manage
Posts: 3
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2014-12-12
update?
2014-12-15 05:14:10
napervilleitsolutions wrote
Hello I had the same problem. Everything was running fine for 1 day. So I decided to test the throughput by using 4 PC's and 2 Phones steaming 4 1080P Bluray video locally, 8 Youtube HD test video 720P 1080P and 4K. I
then tried to connect the phones and I could not get an IP. Then I could not get an IP on any of my laptops or wireless devices. I tried to reset to factory defaults, updated firmware, restored my backup config files. But nothing worked.
I was about to take these back to the store but they were just working flawlessly!!
Solution:
( To save installation time and frustration, I would do this for the initial setup instead of plugging these into your wall jacks.)
I connected all of the adapters to my surge protector with nothing else connected to it the surge protector, plugged them in all in a row. Paired them 1 at a time (took only a few seconds).
Now I can get an IP without a problem. Unplugged them and plugged them back in and they worked right away. Make sure that you are plugging this directly into your router, not a switch.
I tested them for 24 hours now and all is good. I used TamoSoft Throughput test to test the WiFi and it did not drop signal at all. I tested streaming 4K video, 1080P, 720p, from yourtube and my DNLA media server on 4 computers, 2 phones, 1 samsung tablet, 55" vizio smart TV using DNLA streaming a blueray movie approx 5GB movie and everything worked. I was also able to send a 8GB file over with a transfer rate of 4.5Mbps during steaming to all the devices. Plus I could browse the internet without a problem. After sending the 8GB file, browsing my media server was slow (LAN side) but the internet was fine.
I am still testing them out but this definitely fixed my DHCP IP Addressing issue. (obtaining IP / Unknown Network / Discovering issues)
Try using your Android or iPhone to connect to the WiFi again.
I cloned these from my router using WPS and also manually cloned them using the Powerline Scan.exe tool from tp link.
Hope this helps!
I will update this soon. (November, 21 2014)
Any update on this situation. Recently purchased a wpa4220 and its just drops an internet connectivity.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#25
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Announcement Manage
Posts: 791
Helpful: 25
Solutions: 0
Stories: 0
Registered: 2012-11-02
Re:TL-WPA4220KIT and wifi extension problems: wrong ip-range
2014-12-15 17:22:50
Cable connection to WPA4220 works OK or it drops as well?
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#26
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Announcement Manage
Posts: 1
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2014-12-28
Could this be the problem?
2014-12-28 17:29:55
@Vincent. I'm having lots of issues with these too.
1) It would seem to me that when a device first connects to a home router it is given a dynamic (DHCP) address.
2) Once I extend my wireless network with your powerline then my devices work great as part of the network until their lease expires, or something is powercycled.
3) After the lease expires then my device tries to get a new address or a new lease for the last one
4) I think my device is now asking the powerline for a new IP lease (as its the last access point my device connected too). As powerline doesn't have a DHCP server my device is falling back to an internal 169 address.
I think this is why devices are dropping off the network. I think the powerlines need to be able to proxy DHCP requests to stop this happening.
On a separate note should WPA281 and WPA4220 be ok working on the same network?
Thanks
Jon
1) It would seem to me that when a device first connects to a home router it is given a dynamic (DHCP) address.
2) Once I extend my wireless network with your powerline then my devices work great as part of the network until their lease expires, or something is powercycled.
3) After the lease expires then my device tries to get a new address or a new lease for the last one
4) I think my device is now asking the powerline for a new IP lease (as its the last access point my device connected too). As powerline doesn't have a DHCP server my device is falling back to an internal 169 address.
I think this is why devices are dropping off the network. I think the powerlines need to be able to proxy DHCP requests to stop this happening.
On a separate note should WPA281 and WPA4220 be ok working on the same network?
Thanks
Jon
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#27
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Announcement Manage
Posts: 862
Helpful: 7
Solutions: 1
Stories: 0
Registered: 2012-11-05
Re:TL-WPA4220KIT and wifi extension problems: wrong ip-range
2014-12-29 17:37:10
No idea about the DHCP issue. Did you try static IP on your PC?
WPA281 and WPA4220 can work together indeed.
WPA281 and WPA4220 can work together indeed.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#28
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Announcement Manage
Posts: 12
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2014-06-30
Re:TL-WPA4220KIT and wifi extension problems: wrong ip-range
2014-12-29 22:19:46
Jon_I wrote
@Vincent. I'm having lots of issues with these too.
1) It would seem to me that when a device first connects to a home router it is given a dynamic (DHCP) address.
2) Once I extend my wireless network with your powerline then my devices work great as part of the network until their lease expires, or something is powercycled.
3) After the lease expires then my device tries to get a new address or a new lease for the last one
4) I think my device is now asking the powerline for a new IP lease (as its the last access point my device connected too). As powerline doesn't have a DHCP server my device is falling back to an internal 169 address.
I think this is why devices are dropping off the network. I think the powerlines need to be able to proxy DHCP requests to stop this happening.
This is exactly what I'm experiencing. The 4220 does not renew DCHP leases correctly and the device ends up with a 169.x.x.x address. With static IP addresses everything works correctly but this is not an acceptable workaround.
Many of us have been reporting this issue for months.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#29
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Announcement Manage
Posts: 1
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2015-03-02
Re:TL-WPA4220KIT and wifi extension problems: wrong ip-range
2015-03-02 08:14:19
I'm have also exactly same problem because unfortunately I can't get any renew DHCP messages across WPA4220.
Is there any solution beside assigning a static IP address because that is not a option for me!! :(((
Regards
Is there any solution beside assigning a static IP address because that is not a option for me!! :(((
Regards
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#30
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Announcement Manage
Posts: 14
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2014-07-23
Re:TL-WPA4220KIT and wifi extension problems: wrong ip-range
2015-03-07 00:03:50
Mavis wrote
Cable connection to WPA4220 works OK or it drops as well?
Both cabled and wireless drops connection intermittently in my case.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#31
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Announcement Manage
Posts: 1
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2014-02-14
2014-02-14 03:46:33
Posts: 1
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2014-02-14
Information
Helpful: 0
Views: 31738
Replies: 96
Voters 0
No one has voted for it yet.
Tags
Report Inappropriate Content
Transfer Module
New message