TL-WA801N as universal repeater dropping connection every 14 min for ~35 second

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

TL-WA801N as universal repeater dropping connection every 14 min for ~35 second

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
TL-WA801N as universal repeater dropping connection every 14 min for ~35 second
TL-WA801N as universal repeater dropping connection every 14 min for ~35 second
2019-10-19 14:45:32 - last edited 2019-10-21 07:12:11
Model: TL-WA801ND  
Hardware Version: V2
Firmware Version: 3.16.9 Build 150422 Rel.54631n

I've got a TL-WA801N set up in our garage as Universal Repeater, connected via 2.4ghz to a Linksys range extender in the home with a fixed IP on the same subnet.

 

Firmware Version:

3.16.9 Build 150422 Rel.54631n

Hardware Version:

WA801N v2 00000000

 

Operation Mode: Universal Repeater  
Wireless Name of Root AP: xxxxxxxxxx
Channel: 11
Mode: 11n only
Channel Width: 20MHz
Max Tx Rate: 130Mbps

 

Here is the network setup:

 

TL-WA801N (garage, Universal Repeater) <---2.4ghz------> Linksys RE6500 Range Extender (home upstairs) <---2.4ghz------> Netgear R7800 wifi Router (home downstairs)<---1GB Ethernet------> Home Windows server

 

Running ping test from a server connected via ethernet to my Netgear wifi router, I get ping times consistently and under 10ms on average. I'm running the Emco ping monitor app on the same server and it reports that the IP address drops about every 14 minutes and recovers after 35-37 seconds. I've tried changing the channel, Mode, Channel Width on the TP Link device but nothing changes this behavior. I'm also pinging the Linksys RE6500 and its reporting 100%, no drops. 

 

Any help/advise on troubleshooting/resolving this is much appreciated

 

Emco recent results

 

Up    TPLink (10.0.10.19)    The state of the 'TPLink (10.0.10.19)' host was changed to 'Up'. The connection was restored after being down for 00:00:38.    10/19/2019 7:33:34 AM


Down    TPLink (10.0.10.19)    The state of the 'TPLink (10.0.10.19)' host was changed to 'Down'. The connection was lost. Ping reply was not received within the allotted time (IP status: 11010).    10/19/2019 7:32:56 AM

 


Up    TPLink (10.0.10.19)    The state of the 'TPLink (10.0.10.19)' host was changed to 'Up'. The connection was restored after being down for 00:00:35.    10/19/2019 7:13:06 AM


Down    TPLink (10.0.10.19)    The state of the 'TPLink (10.0.10.19)' host was changed to 'Down'. The connection was lost. Ping reply was not received within the allotted time (IP status: 11010).    10/19/2019 7:12:31 AM

 


Up    TPLink (10.0.10.19)    The state of the 'TPLink (10.0.10.19)' host was changed to 'Up'. The connection was restored after being down for 00:00:37.    10/19/2019 6:58:38 AM
Down    TPLink (10.0.10.19)    The state of the 'TPLink (10.0.10.19)' host was changed to 'Down'. The connection was lost. Ping reply was not received within the allotted time (IP status: 11010).    10/19/2019 6:58:01 AM


Up    TPLink (10.0.10.19)    The state of the 'TPLink (10.0.10.19)' host was changed to 'Up'. The connection was restored after being down for 00:00:35.    10/19/2019 6:44:09 AM


Down    TPLink (10.0.10.19)    The state of the 'TPLink (10.0.10.19)' host was changed to 'Down'. The connection was lost. Ping reply was not received within the allotted time (IP status: 11010).    10/19/2019 6:43:34 AM

 


Up    TPLink (10.0.10.19)    The state of the 'TPLink (10.0.10.19)' host was changed to 'Up'. The connection was restored after being down for 00:00:36.    10/19/2019 6:29:41 AM
Down    TPLink (10.0.10.19)    The state of the 'TPLink (10.0.10.19)' host was changed to 'Down'. The connection was lost. Ping reply was not received within the allotted time (IP status: 11010).    10/19/2019 6:29:05 AM


Up    TPLink (10.0.10.19)    The state of the 'TPLink (10.0.10.19)' host was changed to 'Up'. The connection was restored after being down for 00:00:38.    10/19/2019 6:15:13 AM
Down    TPLink (10.0.10.19)    The state of the 'TPLink (10.0.10.19)' host was changed to 'Down'. The connection was lost. Ping reply was not received within the allotted time (IP status: 11010).    10/19/2019 6:14:35 AM


Up    TPLink (10.0.10.19)    The state of the 'TPLink (10.0.10.19)' host was changed to 'Up'. The connection was restored after being down for 00:00:38.    10/19/2019 6:00:45 AM


Down    TPLink (10.0.10.19)    The state of the 'TPLink (10.0.10.19)' host was changed to 'Down'. The connection was lost. Ping reply was not received within the allotted time (IP status: 11010).    10/19/2019 6:00:07 AM

 


Up    TPLink (10.0.10.19)    The state of the 'TPLink (10.0.10.19)' host was changed to 'Up'. The connection was restored after being down for 00:00:38.    10/19/2019 5:46:16 AM

 


Down    TPLink (10.0.10.19)    The state of the 'TPLink (10.0.10.19)' host was changed to 'Down'. The connection was lost. Ping reply was not received within the allotted time (IP status: 11010).    10/19/2019 5:45:38 AM
Up    TPLink (10.0.10.19)    The state of the 'TPLink (10.0.10.19)' host was changed to 'Up'. The connection was restored after being down for 00:00:38.    10/19/2019 5:31:49 AM


Down    TPLink (10.0.10.19)    The state of the 'TPLink (10.0.10.19)' host was changed to 'Down'. The connection was lost. Ping reply was not received within the allotted time (IP status: 11010).    10/19/2019 5:31:11 AM

 

  0      
  0      
#1
Options
3 Reply
Re:TL-WA801N as universal repeater dropping connection every 14 min for ~35 second
2019-10-21 07:11:56 - last edited 2019-10-21 07:12:11

@Gofigure 

 

When it drops connection, please connect your computer to the TL-WA801ND and verify its IP and gateway. Instruction as below:

https://www.tp-link.com/support/faq/838/

 

In the meantime, try to ping the IP of the Linksys extender first and show us the results first; Then please ping the gateway of the Netgear router. 

 

How far away between the TL-WA801ND and the Linksys extender? Next to the TL-WA801ND, please run a computer to test its stability, you can use the ping monitor to verify the communication between the computer and the server. 

 

Try to assign a static IP for the TL-WA801ND; if possible you can connect it to the Linksys extender or Netgear router by wired cable . 

 

Best regards. 

 

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Connect TP-Link Archer BE550 to Germany's DS-Lite (Dual Stack Lite) Internet via WAN Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router Archer BE800 New Firmware Added Support for EasyMesh in AP Mode, DoH&DoT, and 3-Band MLO Connection Archer AX90 New Firmware Added Support for EasyMesh and Ethernet Backhaul If you found a post or response helpful, please click Helpful (arrow pointing upward icon). If you are the author of a topic, remember to mark a helpful reply as the "Recommended Solution" (star icon) so that others can benefit from it.
  0  
  0  
#2
Options
Re:TL-WA801N as universal repeater dropping connection every 14 min for ~35 second
2019-10-22 15:17:51

@Kevin_Z I did all of those and no change. Fyi, my repeater is about 150 ft from the house connected via uni-directional 2.4 ghz antennas. over the weekend I replaced the v.2 WA801N with a version 1 unit I have in storage. Now the drops are less frequent and last only 2-35 seconds. 

 

Up    10/21/2019 4:10:55 PM    10/21/2019 6:29:37 PM    02:18:42
Down    10/21/2019 4:10:20 PM    10/21/2019 4:10:55 PM    00:00:35
Up    10/21/2019 2:34:46 PM    10/21/2019 4:10:20 PM    01:35:34
Down    10/21/2019 2:34:42 PM    10/21/2019 2:34:46 PM    00:00:04
Up    10/21/2019 9:51:07 AM    10/21/2019 2:34:42 PM    04:43:35
Down    10/21/2019 9:51:06 AM    10/21/2019 9:51:07 AM    00:00:01
Up    10/21/2019 8:50:14 AM    10/21/2019 9:51:06 AM    01:00:52
Down    10/21/2019 8:50:12 AM    10/21/2019 8:50:14 AM    00:00:02
Up    10/21/2019 8:37:52 AM    10/21/2019 8:50:12 AM    00:12:20

  0  
  0  
#3
Options
Re:TL-WA801N as universal repeater dropping connection every 14 min for ~35 second
2019-11-01 06:40:29

@Gofigure 

 

Glad to hear that it works better now.

 

FYI, the coverage area of the access point is about 10-15 meters, so the long distance may cause the performance issue, like slow speed or unstable connection. 

 

Besides, there is another network expansion device which can satisfy your needs better, which is called powerline adapter, like TL-WPA8630KIT. TL-WPA7510kit and so on. 

 

Good day. 

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Connect TP-Link Archer BE550 to Germany's DS-Lite (Dual Stack Lite) Internet via WAN Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router Archer BE800 New Firmware Added Support for EasyMesh in AP Mode, DoH&DoT, and 3-Band MLO Connection Archer AX90 New Firmware Added Support for EasyMesh and Ethernet Backhaul If you found a post or response helpful, please click Helpful (arrow pointing upward icon). If you are the author of a topic, remember to mark a helpful reply as the "Recommended Solution" (star icon) so that others can benefit from it.
  0  
  0  
#4
Options