Slow speeds

Jolsa

Did it 3 times:

Downstream 734 Kbps (91.8 KB/sec) 792 Kbps (inc. overheads)
Upstream 361 Kbps (45.1 KB/sec) 389 Kbps (inc. overheads)

Downstream 726 Kbps (90.8 KB/sec) 784 Kbps (inc. overheads)
Upstream 370 Kbps (46.3 KB/sec) 399 Kbps (inc. overheads)

Downstream 770 Kbps (96.3 KB/sec) 831 Kbps (inc. overheads)
Upstream 371 Kbps (46.4 KB/sec) 400 Kbps (inc. overheads)

Still nowhere near 400 KB/Sec eh? Whereas if the test was done on the laptops...

TOG - I assume that if I plugged my computer in direct with an ethernet cable, and I got 400 KB/Sec speeds, then it's definitely my wireless card, or the transmission from the Airport Extreme thats the problem? Infact it would have to be the wireless card right? - If the laptops are getting ok speeds?

One thing I do notice when I open up the D-Link Air utility, is that 'signal strength' hovers around 80-90%, and 'link quality' 80-90% with drops now and again to around 60%. However I assume this isn't a problem, given that the rate is 11 Mbps?

Toxteth_OGrady

Jolsa wrote:

TOG - I assume that if I plugged my computer in direct with an ethernet cable, and I got 400 KB/Sec speeds, then it's definitely my wireless card, or the transmission from the Airport Extreme thats the problem? Infact it would have to be the wireless card right? - If the laptops are getting ok speeds?

Correct.

jolsa wrote:

One thing I do notice when I open up the D-Link Air utility, is that 'signal strength' hovers around 80-90%, and 'link quality' 80-90% with drops now and again to around 60%. However I assume this isn't a problem, given that the rate is 11 Mbps?

Again correct.

:cool:

TOG

Jolsa

albertross, this is what I got when I just ran the largest MTU in TCP Optimizer:

Pinging [63.217.30.70] with 40 bytes ->bytes=40 time=1276ms TTL=51
Pinging [63.217.30.70] with 750 bytes ->bytes=750 time=128ms TTL=51
Pinging [63.217.30.70] with 1125 bytes ->bytes=1125 time=134ms TTL=51
Pinging [63.217.30.70] with 1312 bytes ->bytes=1312 time=125ms TTL=51
Pinging [63.217.30.70] with 1406 bytes ->bytes=1406 time=127ms TTL=51
Pinging [63.217.30.70] with 1453 bytes ->Request Timed Out
Pinging [63.217.30.70] with 1453 bytes ->bytes=1453 time=125ms TTL=51
Pinging [63.217.30.70] with 1476 bytes -> ..fragmented
Pinging [63.217.30.70] with 1465 bytes ->bytes=1465 time=129ms TTL=51
Pinging [63.217.30.70] with 1470 bytes ->bytes=1470 time=130ms TTL=51
Pinging [63.217.30.70] with 1473 bytes -> ..fragmented
Pinging [63.217.30.70] with 1472 bytes ->bytes=1472 time=140ms TTL=51
The largest possible non-fragmented packet is 1472 (1500 - 28 ICMP & IP headers).
You can set your MTU to 1500


I also did the ping in dos and got the following:

Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.

Ping statistics for 66.102.9.147:
Packets: Sent=4, Received = 0, Lost=4 (100% loss).

Toxteth_OGrady

Over to you albert. Way past my bedtime - lol.

:cool:

TOG

Jolsa

Thanks very much for your help this evening TOG, I'm sure there's a way of buying you an online beer :-)

Toxteth_OGrady

:beer:

:cool:

TOG

Jolsa

No need for apologies albertross, you've been a great help - thanks. Yeah my PC is running fine, no other problems.

I guess if I plug my PC in direct and I get good speeds, then it can't be anything wrong with my computer or software conflicts, and must be down to the standard of my wireless card/aerial.

Hopefully some answers will come tomorrow :-)

Jolsa

Ok, now I'm amazed, but twice as confused.
Still got poor download speeds this morning, googled a bit more in search of answers.

Decided to switch my network connection to an ad hoc mode - which cut the connection. So put it back to Infrastructure, and all of a sudden I'm downloading the files at 518 KB/Sec !!!

I didnt change anything else! It's good now (for whatever reason) but will it last? lol!

Jolsa

34.7 MB in 1 min17! That's what I'm talking about :-)

Toxteth_OGrady

but will it last? lol!

Well now it's working just stop using it altogether and it'll be fine!! :rotfl:

Good news. I'd hazard a guess that by changing mode you've released and renewed your IP address and cleared the arp cache which has cleared up the bottleneck.

Based on that, if it happens again try "Repair" on your connection.

:cool:

TOG