Welcome to TP-LINK Tech Support Forum
+ Reply to Thread
Page 2 of 6 FirstFirst 1 2 3 4 ... LastLast
Results 16 to 30 of 82
  1. #16

    I am facing the same problem. Any solutions?

    Quote Originally Posted by xiaonvren View Post
    A couple of hours after posting the above I started seeing the same problem again






    ________________________
    fifa coins

    I am facing the same problem. Any solutions?

  2. #17

    Angry Seeing same behaviour...

    Quote Originally Posted by Vanwegen View Post
    I've got exactly the same issues with this kit. Tried two of them, in two different networks.
    After some weird behaviour during setup, I configured the 4220 as a second AP in my network.

    Setup runs fine for less than a day, after that clients connection through wifi stop receiving IP adresses. With a fixed IP or when connecting with a cable everything works as it should

    latest firmware is installed. Now in contact with TP-link support to resolve the issue.
    This is exactly the behaviour I'm seeing. Setting a static IP is a partial workaround but some devices,like my google Chromecast, don't have this option. I've now put my TP-Link on a mains timer switch to reboot it twice daily but this is a) a nasty kludge b) still not always resolving the problem. I'm very much hoping TP-Link address this with a firmware fix.

    Ed

  3. #18

    Same thing

    I purchased the 422 kit for my father so he could use a chromecast. I set it up to clone his WiFi and it was working great when i left. The next day he tried to use it and he had no connection to the chromecast. I suspect the same thing others have experienced is happening here - DHCP traffic issues. I am going to use his router's MAC Address IP Reservation to set static IP's to everything in his house and see if that corrects the issue. Researching this seems to turn up quite a few customers who have the exact same problem since nearly a year ago. How has TP-Link not addressed this yet??? I tried calling their tech support, but they make you PRESS #1 EVERY 20 SECONDS OR THEY DISCONNECT YOU!!! That became so unbelievably frustrating and I never made it through because i got distracted and didn't press #1 in time. Anyone find a proper solution?

  4. #19
    We have tested TL-WPA4220 many and many times, and I can promise you that there is no such problem on TL-WPA4220.
    Any device which is connected to TL-WPA4220 will obtain IP address from the main router directly, and TL-WPA4220 is just like invisible between your device and the main router.

    Sorry about the inconvenience caused to you.
    If you feel this problem truly exists, you can apply for warranty as maybe there is something wrong with your product.

  5. #20
    That's surely incorrect though. Many of us here are having exactly the same problem and I can repeat it reliably with my WPA4220. Can I assist you with your testing in some way if you are unable to replicate this? It may be dependent on specific setups or routers but I can assure you that this problem does exist.

  6. #21

    Angry sigh

    Exactly the same problem. I had it working for about 3 months fine but had to reset my router to factory settings for another unrelated issue.

    Went through the set up procedures with the powerline and all hell broke loose.

    AV500 keeps reassigning itself a new IP and has a limited connection. No internet connection either.

    newest firmware as well.

    expensive waste of money to have it die after 3 months of use. should never have gone against my gut and purchased tp link.

  7. #22
    Members Mavis is on a distinguished road
    Join Date
    Nov 2012
    Posts
    957
    My kit is working OK. Have you tried to reset them and pair them again? Your devices are still under warranty, right?

  8. #23

    Lightbulb TL-WPA4220 IP issues and internet issues - TL-WPA4220 Setup and solution

    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)

  9. #24

    Any update?

    Quote Originally Posted by napervilleitsolutions View Post
    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

  10. #25

    update?

    Quote Originally Posted by napervilleitsolutions View Post
    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.

  11. #26
    Members Mavis is on a distinguished road
    Join Date
    Nov 2012
    Posts
    957
    Cable connection to WPA4220 works OK or it drops as well?

  12. #27

    Could this be the problem?

    @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

  13. #28
    No idea about the DHCP issue. Did you try static IP on your PC?
    WPA281 and WPA4220 can work together indeed.

  14. #29
    Quote Originally Posted by Jon_I View Post
    @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.

  15. #30

    Thumbs up

    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


 

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Copyright 1996-2017 TP-LINK Technologies Co., Ltd. All rights reserved.