Hi all,
I bought a replacement for the Sky hub (SR101) on ADSL2+ in the form of a TP-Link TD-W8968.
I extracted the username and password from the Sky hub and connected successfully with the TP-Link.
The downstream rate jumped from 4998Kbps to 6023Kbps and it says the internet status is up.
Connecting to any website is extremely slow (as in, unusable). This is the same on both wired and WIFI (PC and smartphone do the same).
Outlook, IE and Chrome are all affected.
I plugged the Sky hub back in and speeds went back to normal.
I factory reset the TP-Link and tried again. Same outcome.
It seems as though the TP-Link is causing a bottleneck but I don�t know why or how to fix it.
Here are some settings from the devices in case they help:
SKY HUB
Connection Speed D: 4998 kbps; U: 1023 kbps
Line Attenuation D: 48.5 dB; U: 26.9 dB
Noise Margin D: 8.3 dB; U: 6.6 dB
Connection Type: PPPoA
Obviously the TP-Link offers a few more settings:
TP-LINK
Connection Speed D: 6023 kbps; U: 1023 kbps
Line Attenuation see below
Noise Margin see below
WAN Type: ATM WAN
Layer2 Interface: atm1(0/38)
Connection Type: PPPoA
Interface atm0 / atm1
Vpi 8 / 0
Vci 35 / 38
Link Type EoA / PPPoA
Encapsulation LLC / VC/MUX
Category UBR / UBR
Conn Mode VlanMuxMode / DefaultMode
IP QoS Enabled / Enabled
Sched Alg WRR / WRR
Queue Weight 1 / 1
Group Precedence 8 / 8
This is the data after about 10 minutes of uptime:
FIRST NUMBER IS DOWNSTREAM, SECOND IS UPSTREAM.
Line Coding(Trellis): On On
SNR Margin (0.1 dB): 63 68
Attenuation (0.1 dB): 495 263
Output Power (0.1 dBm):192 122
Attainable Rate (Kbps): 6,420 934
Rate (Kbps): 5,742 1,023
MSGc (# of bytes in overhead channel message): 65530 14
B (# of bytes in Mux Data Frame): 245 13
M (# of Mux Data Frames in FEC Data Frame): 1 16
T (Mux Data Frames over sync bytes): 0 7
R (# of check bytes in FEC Data Frame): 6 16
S (ratio of FEC over PMD Data Frame length): 1.4769 7.5
L (# of bits in PMD Data Frame): 1365 256
D (interleaver depth): 1 8
Delay (msec): 0 15
INP (DMT symbol): 26 2
Super Frames: 0 0
Super Frame Errors: 1,044 0
RS Words: 2,830,732 557,044
RS Correctable Errors: 13,024 6
RS Uncorrectable Errors: 0 0
HEC Errors: 0 0
OCD Errors: 0 0
LCD Errors: 0 0
Total Cells: 13,644,396 2,512,408
Data Cells: 52,200 17,854
Bit Errors: 0 0
Total ES: 643 0
Total SES: 0 0
Total UAS: 51 51
Pings from command prompt on the PC:
Pinging GOOGLE.COM [2.127.252.152] with 32 bytes of data:
Reply from 2.127.252.152: bytes=32 time=27ms TTL=61
Reply from 2.127.252.152: bytes=32 time=27ms TTL=61
Reply from 2.127.252.152: bytes=32 time=27ms TTL=61
Reply from 2.127.252.152: bytes=32 time=27ms TTL=61
Ping statistics for 2.127.252.152:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 27ms, Average = 27ms
Pinging BBC.CO.UK [212.58.244.20] with 32 bytes of data:
Reply from 212.58.244.20: bytes=32 time=31ms TTL=56
Reply from 212.58.244.20: bytes=32 time=32ms TTL=56
Reply from 212.58.244.20: bytes=32 time=28ms TTL=56
Reply from 212.58.244.20: bytes=32 time=27ms TTL=56
Ping statistics for 212.58.244.20:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 32ms, Average = 29ms
Pinging FACEBOOK.COM [173.252.120.6] with 32 bytes of data:
Reply from 173.252.120.6: bytes=32 time=116ms TTL=84
Reply from 173.252.120.6: bytes=32 time=124ms TTL=84
Reply from 173.252.120.6: bytes=32 time=115ms TTL=84
Reply from 173.252.120.6: bytes=32 time=116ms TTL=84
Ping statistics for 173.252.120.6:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 115ms, Maximum = 124ms, Average = 117ms
Thanks in advance for any help anyone can offer!
Regards,
Steve



Pages in this thread:
Print Thread
beercan