Sign in with
Sign up | Sign in
Your question

Speed/ping issues with wireless range extender/bridge

Last response: in Wireless Networking
Share
January 7, 2013 9:32:59 PM

Hello,

I have a TP-link wireless router ( ) to distribute our ADSL wirelessly, although because ours is a long, thin flat with bits of pesky concrete I've had to add a range extender, TP-Link TL-WA830RE.

When it was first installed, it worked flawlessly (for about 24h!). Now, when connected either to the LAN port of the extender, or wirelessly at the end of the flat that the extender covers, the service is near-enough useless.

As far as I can establish, it isn't a wireless signal issue, as my macbook pro can pick up full strength signal at the point where the extender is located (with the extender switched off - ie picking up the router's signal).

Can anyone point me in the right direction in terms of getting to the bottom of the problem? I used to know router settings inside out, but with all the zero-configuration bits of kit I've been given by ISPs recently, I've got a bit rusty!

Thanks,
January 7, 2013 9:40:03 PM

oops, I meant to go and check the model of my router and, alas, I forgot.

It's a TD-W8961ND

Here's a ping log from a pc connected via LAN to the extender:

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=481ms TTL=254
Reply from 192.168.1.1: bytes=32 time=526ms TTL=254
Reply from 192.168.1.1: bytes=32 time=297ms TTL=254
Reply from 192.168.1.1: bytes=32 time=351ms TTL=254
Reply from 192.168.1.1: bytes=32 time=796ms TTL=254
Reply from 192.168.1.1: bytes=32 time=501ms TTL=254
Reply from 192.168.1.1: bytes=32 time=393ms TTL=254
Reply from 192.168.1.1: bytes=32 time=200ms TTL=254
Reply from 192.168.1.1: bytes=32 time=250ms TTL=254
Reply from 192.168.1.1: bytes=32 time=665ms TTL=254
Reply from 192.168.1.1: bytes=32 time=464ms TTL=254
Reply from 192.168.1.1: bytes=32 time=747ms TTL=254
Reply from 192.168.1.1: bytes=32 time=290ms TTL=254
Reply from 192.168.1.1: bytes=32 time=231ms TTL=254
Request timed out.
Reply from 192.168.1.1: bytes=32 time=458ms TTL=254
Reply from 192.168.1.1: bytes=32 time=314ms TTL=254
Reply from 192.168.1.1: bytes=32 time=457ms TTL=254
Reply from 192.168.1.1: bytes=32 time=141ms TTL=254
Reply from 192.168.1.1: bytes=32 time=212ms TTL=254
Reply from 192.168.1.1: bytes=32 time=402ms TTL=254
Reply from 192.168.1.1: bytes=32 time=821ms TTL=254
Reply from 192.168.1.1: bytes=32 time=424ms TTL=254
Reply from 192.168.1.1: bytes=32 time=1065ms TTL=254
Reply from 192.168.1.1: bytes=32 time=733ms TTL=254
Reply from 192.168.1.1: bytes=32 time=379ms TTL=254
Reply from 192.168.1.1: bytes=32 time=1231ms TTL=254
Reply from 192.168.1.1: bytes=32 time=2610ms TTL=254
Reply from 192.168.1.1: bytes=32 time=1455ms TTL=254
Reply from 192.168.1.1: bytes=32 time=755ms TTL=254
Reply from 192.168.1.1: bytes=32 time=851ms TTL=254
Reply from 192.168.1.1: bytes=32 time=383ms TTL=254
Reply from 192.168.1.1: bytes=32 time=1968ms TTL=254
Reply from 192.168.1.1: bytes=32 time=713ms TTL=254
Reply from 192.168.1.1: bytes=32 time=548ms TTL=254
Reply from 192.168.1.1: bytes=32 time=906ms TTL=254
Reply from 192.168.1.1: bytes=32 time=235ms TTL=254
Reply from 192.168.1.1: bytes=32 time=903ms TTL=254
Reply from 192.168.1.1: bytes=32 time=233ms TTL=254
Reply from 192.168.1.1: bytes=32 time=2324ms TTL=254
Reply from 192.168.1.1: bytes=32 time=1979ms TTL=254
Reply from 192.168.1.1: bytes=32 time=1ms TTL=254
Reply from 192.168.1.1: bytes=32 time=1891ms TTL=254
Reply from 192.168.1.1: bytes=32 time=1ms TTL=254
Reply from 192.168.1.1: bytes=32 time=1456ms TTL=254
Reply from 192.168.1.1: bytes=32 time=1585ms TTL=254
Reply from 192.168.1.1: bytes=32 time=1ms TTL=254

Ping statistics for 192.168.1.1:
Packets: Sent = 47, Received = 46, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2610ms, Average = 731ms
Control-Break
Reply from 192.168.1.1: bytes=32 time=2236ms TTL=254
Reply from 192.168.1.1: bytes=32 time=615ms TTL=254
Reply from 192.168.1.1: bytes=32 time=934ms TTL=254
Reply from 192.168.1.1: bytes=32 time=1574ms TTL=254
Reply from 192.168.1.1: bytes=32 time=1ms TTL=254
Reply from 192.168.1.1: bytes=32 time=6ms TTL=254
Reply from 192.168.1.1: bytes=32 time=1694ms TTL=254
Reply from 192.168.1.1: bytes=32 time=3390ms TTL=254

Ping statistics for 192.168.1.1:
Packets: Sent = 55, Received = 54, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 3390ms, Average = 816ms
January 9, 2013 11:06:47 PM

for once, official support beat the forums! Here's Cora from TP-Link's response:

Dear Thom,

Thank you very much for your email requesting information about our product.

If the computer can ping the IP address of TD-W8961ND, can it ping 8.8.8.8? Can it get reply from this IP address? What is the IP address of the range extender? Is it 192.168.0.254 which is the default one?
If so, please change the IP address of the rang extender to 192.168.1.254 to avoid IP problems.

You can log into the TP-LINK page by the default IP address 192.168.0.254. Due to DHCP disabled for range extender, you need set a static IP on Windows 7.Go to StartàControl PanelàNetwork and InterentàNetwork and Sharing CenteràLocal Area ConnectionàRight clickàPropertiesàInternet protocol Version4àdouble clickàUse the following IP addressàIp address 192.168.0.100,subnetmarsk:255.255.255.0àOKàOK again.

Go to the browser type in the :192.168.0.254 in the address bar. Username and password botu “admin” in lower case. Go to NetworkàIp addressàChange the IP address to 192.168.1.254, gatway to 192.168.1.1àSave and then reboot the range extender and then give a try for Interent.


What is more, here is the instruction on how to set up range extender manually. Maybe you can have a check.
http://www.tp-link.com/en/article/?faqid=250






If you need any further help, please feel free to let me know.
To get technical support more quickly, please go to http://www.tp-link.com/en/support/faq

Everything seems to be working just fine now. I've been pinging for about half an hour and it's been coming back with solid <1ms

Hope this helps anyone else who comes across this!
January 14, 2013 2:46:52 PM

The problem seems to have reared its ugly head again, despite my changing the IP address of the extender.

Any thoughts?
!