Upload issues

UltimateHigh1 · Post by **UltimateHigh1** » Wed Apr 09, 2008 8:49 pm

My speedtest suggest that my upload can hit 800kbps or more on a consistant basis.. However, when I try and upload a file to a site(mediafire), I can barely hit 200kbps. What exactly is going on here?

4mb/1mb cable

trogers · Post by **trogers** » Wed Apr 09, 2008 9:51 pm

Perhaps the server in Mediafire is set to only receive your file at 200kbps.

UltimateHigh1 · Post by **UltimateHigh1** » Wed Apr 09, 2008 11:10 pm

I've also tried Megaupload and various other sites with the same results.

trogers · Post by **trogers** » Wed Apr 09, 2008 11:16 pm

UltimateHigh1 wrote:I've also tried Megaupload and various other sites with the same results.

Then I suspect you misunderstood between kilobytes per second (KB/s) and kilobits per second (kbps or kb/s).

UltimateHigh1 · Post by **UltimateHigh1** » Thu Apr 10, 2008 4:22 am

Megaupload:

Estimated time left:
00:22:05 (2.88 MB of 72.18 MB)
Elapsed time - Transfer rate:
00:00:55 - 54 KB/s -

Mediafire kept going back from 200kbps to 600kbps or kb/s

trogers · Post by **trogers** » Thu Apr 10, 2008 4:58 am

Post your TCP Analyzer report.

Seems your paid speeds from your ISP are 3/1mbps.

Sava700 · Post by **Sava700** » Thu Apr 10, 2008 7:50 am

trogers wrote:Post your TCP Analyzer report.

Seems your paid speeds from your ISP are 3/1mbps.

yeah he's on that same wireless network another guy was on a while back.. he's lucky he's getting what he is.

Some fine tuning with the TCP stack might help his overall performance but the speed isn't going to do much more.

Faster HDD for write/read, more ram, etc might help the impression the files make from the connection.

UltimateHigh1 · Post by **UltimateHigh1** » Thu Apr 10, 2008 6:17 pm

trogers wrote:Post your TCP Analyzer report.

Seems your paid speeds from your ISP are 3/1mbps.

The package I'm paying for is 4mb/1mb but my ISP loves to suck...

« SpeedGuide.net TCP Analyzer Results »
Tested on: 04.10.2008 18:16
IP address: 64.89.xxx.xxx

TCP options string: 020405b40103030101010402
MSS: 1460
MTU: 1500
TCP Window: 128480 (multiple of MSS)
RWIN Scaling: 1
Unscaled RWIN : 64240
Reccomended RWINs: 64240, 128480, 256960, 513920
BDP limit (200ms): 5139kbps (642KBytes/s)
BDP limit (500ms): 2056kbps (257KBytes/s)
MTU Discovery: ON
TTL: 42
Timestamps: OFF
SACKs: ON
IP ToS: 10100000 (160)
Precedence: 101 (CRITIC/ECP)
Delay: 0 (normal delay)
Throughput: 0 (normal throughput)
Reliability: 0 (normal reliability)
Cost: 0 (normal cost)
Check bit: 0 (correct)
DiffServ: CS5 101000 (40) - class 5 (RFC 2474). Similar forwarding behavior to the ToS Precedence field.

trogers · Post by **trogers** » Thu Apr 10, 2008 11:23 pm

If you are on a wireless connection, try out these wireless tweaks:

https://www.speedguide.net/forums/viewtopic.php?t=203247

UltimateHigh1 · Post by **UltimateHigh1** » Sat Apr 12, 2008 2:21 am

I'm on a cable connection

Here's my Linksys cable modem log:

Time Priority Description
2008-04-11 21:09:07 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-04-02 14:19:13 critical SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-04-02 14:19:10 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-04-02 14:13:59 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2008-04-02 14:13:31 critical SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
2008-04-02 14:02:56 critical DHCP WARNING - Non-critical field invalid in response.
2008-04-02 14:02:50 critical No Ranging Response received - T3 time-out
2008-04-02 14:02:46 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2008-04-02 14:02:13 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-04-02 02:24:09 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2008-04-02 02:23:41 critical SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
2008-03-31 21:41:58 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2008-03-31 21:41:30 critical SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
2008-03-31 14:24:45 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-03-30 19:54:09 critical SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
2008-03-30 14:13:44 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-03-29 02:34:54 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-03-21 01:55:57 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2008-03-21 01:55:30 critical SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
1970-01-01 00:01:41 critical DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:01:36 critical No Ranging Response received - T3 time-out
1970-01-01 00:00:28 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:27 critical REG RSP not received
1970-01-01 00:00:16 critical DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:13 critical No Ranging Response received - T3 time-out
1970-01-01 00:00:13 critical DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:13 critical DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:13 critical DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:12 critical DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:10 critical DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:10 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:08 critical No Ranging Response received - T3 time-out

Lock Status Operational
Modulation 64QAM
Channel ID 0
Provisioned Rate 4096 kbps
Symbol Rate 5056.941 Ksym/sec
Downstream Power 10.7 dBmV
SNR 40.7 dB

Upstream Channel

Lock Status Operational
Modulation QPSK
Channel ID 2
Provisioned Rate 1024 kbps
Symbol Rate 2560 Ksym/sec
Upstream Power 53.0 dBmV

What do all of these errors mean?

trogers · Post by **trogers** » Sat Apr 12, 2008 10:27 am

UltimateHigh1 wrote: Downstream Power 10.7 dBmV

Downstream power is too high. Value exceeding +/- 8 dBmV will have connection issues.

Get your ISP tech to look into the connection. He should be able to get the power level down to within +/- 3 dBmV.

UltimateHigh1 · Post by **UltimateHigh1** » Mon Apr 14, 2008 7:45 pm

So here are some results after consulting with my ISP again and receiving a new modem:

URL=http://www.speedtest.net]

[/URL]

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\adam>tracert http://www.yahoo.com

Tracing route to http://www.yahoo-ht3.akadns.net [69.147.114.210]
over a maximum of 30 hops:

1 14 ms 37 ms 42 ms 10.0.99.1
2 57 ms 18 ms 11 ms 66.186.180.209
3 43 ms 15 ms 15 ms 66.186.173.37
4 65 ms 64 ms 58 ms pwn-pi-mont-core.pwless.net [66.186.173.43]
5 65 ms * 61 ms pi-rtr-wt.mainewireless.net [64.89.247.242]
6 * 58 ms 54 ms 64.89.249.97
7 48 ms 101 ms 88 ms 74.221.67.130
8 47 ms 245 ms 190 ms 74.221.67.134
9 185 ms 30 ms 32 ms 198.164.27.13
10 47 ms * 71 ms ge-0-2-2.cr02.stjh.nb.aliant.net [142.166.211.13
0]
11 243 ms 261 ms 280 ms rtp629047rts [64.230.203.29]
12 293 ms 324 ms 309 ms core2-saintjohnnb_pos5-0.net.bell.ca [64.230.167
.73]
13 292 ms 218 ms 257 ms core3-montreal02_pos2-3.net.bell.ca [64.230.147.
45]
14 276 ms 284 ms 313 ms bx4-montreal02_so-0-0-0.net.bell.ca [64.230.170.
174]
15 258 ms 236 ms 246 ms if-6-0-0.mcore4.mtt-montreal.teleglobe.net [216.
6.115.29]
16 233 ms 254 ms 225 ms pos-channel1.mcore3.nyy-newyork.teleglobe.net [2
16.6.81.17]
17 235 ms 271 ms 212 ms if-12-0-0-723.core4.aeq-ashburn.teleglobe.net [2
16.6.42.61]
18 89 ms 111 ms 60 ms 64.86.85.38
19 80 ms 58 ms 59 ms ge-3-1-0-p141.msr1.re1.yahoo.com [216.115.108.59
]
20 74 ms 57 ms 64 ms gi1-23.bas-a1.re3.yahoo.com [68.142.238.67]
21 70 ms 64 ms 84 ms f1.http://www.vip.re3.yahoo.com [69.147.114.210]

Trace complete.

C:\Documents and Settings\adam>

Lock Status Operational
Modulation 64QAM
Channel ID 0
Provisioned Rate 4096 kbps
Symbol Rate 5056.941 Ksym/sec
Downstream Power 9.6 dBmV
SNR 39.2 dB

Lock Status Operational
Modulation QPSK
Channel ID 2
Provisioned Rate 1024 kbps
Symbol Rate 2560 Ksym/sec
Upstream Power 51.0 dBmV

I love it when things go from bad to worse.

trogers · Post by **trogers** » Tue Apr 15, 2008 2:45 am

UltimateHigh1 wrote: So here are some results after consulting with my ISP again and receiving a new modem:
Downstream Power 9.6 dBmV
SNR 39.2 dB
Upstream Power 51.0 dBmV

Just changing the modem will not do. Still high power level for downstream. Your need your ISP tech to check out the cable line that is going into your modem.