Jump to content

Slow UL


halo2

Recommended Posts

I have Cox as my internet provider and my upload is registered at 523kb. I have never gotten anything remotely close to this number, I have tried looking in the tweaks section and I have used van burens cablenut settings.

:::.. Upload Stats ..:::

Connection is:: 112 Kbps about 0.1 Mbps (tested with 1013 kB)

Upload Speed is:: 14 kB/s

Tested From:: https://testmy.net/ (server1)

Test Time:: Sun Sep 25 2005 10:48:37 GMT-0500 (Central Daylight Time)

Bottom Line:: 2X faster than 56K 1MB upload in 73.14 sec

Diagnosis: May need help : running at only 21.41 % of your hosts average (cox.net)

Validation Link:: https://testmy.net/stats/id-YOW26EMIJ

Link to comment
Share on other sites

How about some info first:

1 - Are you running through a router, and do you have more than 1 PC connected?

2 - Have you run updated Antivirus and Spyware tests?

3 - Have you tried a different ethernet cable?

4 - Did you try the suggestions from this thread: http://www.testmy.net/forum/t-2097.0

Also, what brand of modem do you have?

Try opening the diagnostic page: http://192.168.100.1 (<--just try clicking link for most modems)

If it opens, paste the info from the Signal Level page back here.

Link to comment
Share on other sites

I am running through a router, but I have tried just a straight connection and it didn't help.

Yes, I have updated spybot and AVG anti-virus running.

Tried a brand new cat 6 cable (by direct connection) and it didn't help, the original cables appear to fine anyways.

I did the cablenut settings, the ccleaner, the connection sp2 tweak from 10-50 and I have all the latest windows updates.

I have a Toshiba modem (thinking of buying a Motorola surfboard) and the 192.168.100.1 doesn't work.

Link to comment
Share on other sites

I would like to know what your upstream levels are.

If they are maxed, that could very well be your issue.

Does your modem tend to reset on its own occasionally?

Also, what about packet loss?

Try pinging testmy.net : ping testmy.net -n 50

BTW; here is a way to get your levels if you are interested: click here

I have never tries this method myself, so it's up to you.

Link to comment
Share on other sites

No my modem doesn't seem to reset on its own.

ping testmy.net -n 50

Pinging testmy.net [67.18.179.85] with 32 bytes of data:

Reply from 67.18.179.85: bytes=32 time=17ms TTL=51

Reply from 67.18.179.85: bytes=32 time=26ms TTL=49

Reply from 67.18.179.85: bytes=32 time=16ms TTL=50

Reply from 67.18.179.85: bytes=32 time=20ms TTL=51

Reply from 67.18.179.85: bytes=32 time=18ms TTL=49

Reply from 67.18.179.85: bytes=32 time=17ms TTL=51

Reply from 67.18.179.85: bytes=32 time=15ms TTL=49

Reply from 67.18.179.85: bytes=32 time=24ms TTL=49

Reply from 67.18.179.85: bytes=32 time=15ms TTL=51

Reply from 67.18.179.85: bytes=32 time=15ms TTL=49

Reply from 67.18.179.85: bytes=32 time=16ms TTL=51

Reply from 67.18.179.85: bytes=32 time=18ms TTL=50

Reply from 67.18.179.85: bytes=32 time=16ms TTL=50

Reply from 67.18.179.85: bytes=32 time=12ms TTL=50

Reply from 67.18.179.85: bytes=32 time=15ms TTL=49

Reply from 67.18.179.85: bytes=32 time=14ms TTL=51

Reply from 67.18.179.85: bytes=32 time=43ms TTL=50

Reply from 67.18.179.85: bytes=32 time=29ms TTL=49

Reply from 67.18.179.85: bytes=32 time=12ms TTL=50

Reply from 67.18.179.85: bytes=32 time=14ms TTL=49

Reply from 67.18.179.85: bytes=32 time=15ms TTL=51

Reply from 67.18.179.85: bytes=32 time=16ms TTL=51

Reply from 67.18.179.85: bytes=32 time=16ms TTL=49

Reply from 67.18.179.85: bytes=32 time=14ms TTL=51

Reply from 67.18.179.85: bytes=32 time=30ms TTL=49

Reply from 67.18.179.85: bytes=32 time=13ms TTL=50

Reply from 67.18.179.85: bytes=32 time=239ms TTL=51

Reply from 67.18.179.85: bytes=32 time=309ms TTL=49

Reply from 67.18.179.85: bytes=32 time=92ms TTL=49

Reply from 67.18.179.85: bytes=32 time=16ms TTL=50

Reply from 67.18.179.85: bytes=32 time=11ms TTL=49

Reply from 67.18.179.85: bytes=32 time=13ms TTL=49

Reply from 67.18.179.85: bytes=32 time=23ms TTL=51

Reply from 67.18.179.85: bytes=32 time=12ms TTL=49

Request timed out.

Reply from 67.18.179.85: bytes=32 time=46ms TTL=50

Reply from 67.18.179.85: bytes=32 time=13ms TTL=49

Reply from 67.18.179.85: bytes=32 time=14ms TTL=51

Reply from 67.18.179.85: bytes=32 time=13ms TTL=49

Reply from 67.18.179.85: bytes=32 time=66ms TTL=49

Reply from 67.18.179.85: bytes=32 time=13ms TTL=51

Reply from 67.18.179.85: bytes=32 time=15ms TTL=49

Reply from 67.18.179.85: bytes=32 time=17ms TTL=51

Reply from 67.18.179.85: bytes=32 time=12ms TTL=50

Reply from 67.18.179.85: bytes=32 time=16ms TTL=50

Reply from 67.18.179.85: bytes=32 time=15ms TTL=50

Reply from 67.18.179.85: bytes=32 time=18ms TTL=49

Reply from 67.18.179.85: bytes=32 time=15ms TTL=51

Reply from 67.18.179.85: bytes=32 time=12ms TTL=50

Reply from 67.18.179.85: bytes=32 time=16ms TTL=49

Ping statistics for 67.18.179.85:

    Packets: Sent = 50, Received = 49, Lost = 1 (2% loss),

Approximate round trip times in milli-seconds:

    Minimum = 11ms, Maximum = 309ms, Average = 30ms

What do you mean by upstream levels? (newbie)

Link to comment
Share on other sites

The modem has to transmit everything back upstream to your isp.

It can only transmit with so much power (around +58dBmV, depending upon modulation).

Think of it as a person yelling back to your isp.

The more attenuation, or obstacles, in the way, the louder the modem yells.

If there is too much attenuation, then the modem may be screaming at the top of its lungs, but the CMTS (device at your isp that talks to your modem) can barely hear it.

This is one possible cause of slow upload and packet loss.

Noticed you dropped a packet, and the latency rose to 309ms at one point......

Link to comment
Share on other sites

×
×
  • Create New...