Jump to content
Sign in to follow this  
scumbucketsex

hi im new here, sorry to bother you all but is this right?

Recommended Posts

hi all i just ran a test on www.testmy.net and it cam up like this:

Connection is:: 482 Kbps about 0.5 Mbps (tested with 2992 kB)

Download Speed is:: 59 kB/s

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

Test Time:: Sun Feb 5 12:36:53 UTC 2006

Bottom Line:: 9X faster than 56K 1MB download in 17.36 sec

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

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

is this right?im currently on tesco broadband, 1meg package, anyone know what i can do to improve this or is this how it should b?sorry to bother you sll bet you get asked these sort of things all the time.

Share this post


Link to post
Share on other sites

this is the first one

SpeedGuide.net TCP/IP Analyzer

TCP properties for IP =

Browser/OS = Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; Tesco; .NET CLR 1.1.4322)

Notes: Read the Analyzer FAQ if the above is not your IP address.

Your IP  appears to be behind a web proxy server  and results shown might not be for your system.

TCP options string = 020405b401010402

MTU = 1500

MTU is fully optimized for broadband.

MSS = 1460

Maximum useful data in each packet = 1460, which equals MSS.

Default TCP Receive Window (RWIN) = 35040

RWIN Scaling (RFC1323) = 0 bits

Unscaled TCP Receive Window = 35040

RWIN is a multiple of MSS

Other values for RWIN that might work well with your current MTU/MSS:

513920 (MSS x 44 * scale factor of 8)

256960 (MSS x 44 * scale factor of 4)

128480 (MSS x 44 * scale factor of 2)

64240 (MSS x 44) 

bandwidth * delay product (Note this is not a speed test):

Your TCP Window limits you to: 1401.6 kbps (175.2 KBytes/s) @ 200ms

Your TCP Window limits you to: 560.64 kbps (70.08 KBytes/s) @ 500ms

MTU Discovery (RFC1191) = ON

Time to live left = 42 hops

TTL value is ok.

Timestamps (RFC1323) = OFF

Selective Acknowledgements (RFC2018) = ON

IP type of service field (RFC1349) = 00000000 (0)

Share this post


Link to post
Share on other sites

TCP/Web100 Network Diagnostic Tool v5.3.3d

click START to begin

Checking for Middleboxes . . . . . . . . . . . . . . . . . .  Done

running 10s outbound test (client to server) . . . . . 245.21Kb/s

running 10s inbound test (server to client) . . . . . . 476.08kb/s

Your PC is connected to a Cable/DSL modem

Information: The receive buffer should be 196.04 Kbytes to maximize throughput

Share this post


Link to post
Share on other sites

------  Web100 Detailed Analysis  ------

Cable modem/DSL/T1 link found.

Link set to Full Duplex mode

No network congestion discovered.

Good network cable(s) found

Normal duplex operation found.

Web100 reports the Round trip time = 540.05 msec; the Packet size = 1460 Bytes; and

No packet loss - but packets arrived out-of-order 3.98% of the time

This connection is receiver limited 83.93% of the time.

  Increasing the the client's receive buffer (34.0 KB) will improve performance

This connection is network limited 16.04% of the time.

Web100 reports TCP negotiated the optional Performance Settings to:

RFC 2018 Selective Acknowledgment: ON

RFC 896 Nagle Algorithm: ON

RFC 3168 Explicit Congestion Notification: OFF

RFC 1323 Time Stamping: OFF

RFC 1323 Window Scaling: OFF

Packet size is preserved End-to-End

Server IP addresses are preserved End-to-End

Client IP addresses are preserved End-to-End

Share this post


Link to post
Share on other sites

WEB100 Kernel Variables:

Client: localhost/127.0.0.1

AckPktsIn: 204

AckPktsOut: 0

BytesRetrans: 0

CongAvoid: 184

CongestionOverCount: 0

CongestionSignals: 0

CountRTT: 189

CurCwnd: 27740

CurMSS: 1460

CurRTO: 680

CurRwinRcvd: 35040

CurRwinSent: 16304

CurSsthresh: 2920

DSACKDups: 0

DataBytesIn: 0

DataBytesOut: 566480

DataPktsIn: 0

DataPktsOut: 388

DupAcksIn: 15

ECNEnabled: 0

FastRetran: 0

MaxCwnd: 27740

MaxMSS: 1460

MaxRTO: 680

MaxRTT: 490

MaxRwinRcvd: 35040

MaxRwinSent: 16304

MaxSsthresh: 2920

MinMSS: 1460

MinRTO: 450

MinRTT: 180

MinRwinRcvd: 35040

MinRwinSent: 16304

NagleEnabled: 1

OtherReductions: 0

PktsIn: 204

PktsOut: 388

PktsRetrans: 0

X_Rcvbuf: 103424

RcvWinScale: 2147483647

SACKEnabled: 3

SACKsRcvd: 19

SendStall: 0

SlowStart: 1

SampleRTT: 460

SmoothedRTT: 450

X_Sndbuf: 103424

SndWinScale: 2147483647

SndLimTimeRwin: 0

SndLimTimeCwnd: 10139600

SndLimTimeSender: 2604

SndLimTransRwin: 0

SndLimTransCwnd: 1

SndLimTransSender: 1

SndLimBytesRwin: 0

SndLimBytesCwnd: 566480

SndLimBytesSender: 0

SubsequentTimeouts: 0

SumRTT: 61080

Timeouts: 0

TimestampsEnabled: 0

WinScaleRcvd: 2147483647

WinScaleSent: 2147483647

DupAcksOut: 0

StartTimeUsec: 447921

Duration: 10144945

c2sData: 2

c2sAck: 2

s2cData: 2

s2cAck: 2

half_duplex: 0

link: 100

congestion: 1

bad_cable: 0

mismatch: 0

spd: 0.00

bw: 34.47

loss: 0.000001000

avgrtt: 323.17

waitsec: 0.00

timesec: 10.00

order: 0.0735

rwintime: 0.0000

sendtime: 0.0003

cwndtime: 0.9997

rwin: 0.2673

swin: 0.7891

cwin: 0.2116

rttsec: 0.323175

Sndbuf: 103424

aspd: 2.06719

Checking for mismatch on uplink

(speed > 50 [0>50], (xmitspeed < 5) [0.24<5]

(rwintime > .9) [0>.9], (loss < .01) [1.0E<.01]

Checking for excessive errors condition

(loss/sec > .15) [1.0E>.15], (cwndtime > .6) [0.99>.6],

(loss < .01) [1.0E<.01], (MaxSsthresh > 0) [2920>0]

Checking for 10 Mbps link

(speed < 9.5) [0<9.5], (speed > 3.0) [0>3.0]

(xmitspeed < 9.5) [0.24<9.5] (loss < .01) [1.0E<.01], (mylink > 0) [3.0>0]

Checking for Wireless link

(sendtime = 0) [3.0E=0], (speed < 5) [0<5]

(Estimate > 50 [34.47>50], (Rwintime > 90) [0>.90]

(RwinTrans/CwndTrans = 1) [0/1=1], (mylink > 0) [3.0>0]

Checking for DSL/Cable Modem link

(speed < 2) [0<2], (SndLimTransSender = 0) [1=0]

(SendTime = 0) [3.0E-4=0], (mylink > 0) [3.0>0]

Checking for half-duplex condition

(rwintime > .95) [0>.95], (RwinTrans/sec > 30) [0>30],

(SenderTrans/sec > 30) [0.1>30], OR (mylink <= 10) [3.0<=10]

Checking for congestion

(cwndtime > .02) [0.99>.02], (mismatch = 0) [0=0]

(MaxSsthresh > 0) [2920>0]

estimate = 34.47 based on packet size = 11Kbits, RTT = 323.17msec, and loss = 1.0E-6

The theoretical network limit is 34.47 Mbps

The NDT server has a 101.0 KByte buffer which limits the throughput to 2.44 Mbps

Your PC/Workstation has a 34.0 KByte buffer which limits the throughput to 0.82 Mbps

The network based flow control limits the throughput to 0.65 Mbps

Client Data reports link is 'T1', Client Acks report link is 'T1'

Server Data reports link is 'T1', Server Acks report link is 'T1'

Share this post


Link to post
Share on other sites

i tryed thccs file, restarted pc and retset

:::.. Download Stats ..:::

Connection is:: 477 Kbps about 0.5 Mbps (tested with 2992 kB)

Download Speed is:: 58 kB/s

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

Test Time:: Sun Feb 5 13:33:52 UTC 2006

Bottom Line:: 9X faster than 56K 1MB download in 17.66 sec

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

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

Share this post


Link to post
Share on other sites

TCP options string = 020405b401010402

MTU = 1500

MTU is fully optimized for broadband.

MSS = 1460

Maximum useful data in each packet = 1460, which equals MSS.

Default TCP Receive Window (RWIN) = 64240

RWIN Scaling (RFC1323) = 0 bits

Unscaled TCP Receive Window = 64240

RWIN is a multiple of MSS

Other values for RWIN that might work well with your current MTU/MSS:

513920 (MSS x 44 * scale factor of 8)

256960 (MSS x 44 * scale factor of 4)

128480 (MSS x 44 * scale factor of 2) 

bandwidth * delay product (Note this is not a speed test):

Your TCP Window limits you to: 2569.6 kbps (321.2 KBytes/s) @ 200ms

Your TCP Window limits you to: 1027.84 kbps (128.48 KBytes/s) @ 500ms

MTU Discovery (RFC1191) = ON

Time to live left = 58 hops

TTL value is ok.

Timestamps (RFC1323) = OFF

Selective Acknowledgements (RFC2018) = ON

IP type of service field (RFC1349) = 00000000 (0)

Share this post


Link to post
Share on other sites

WEB100 Enabled Statistics:

Checking for Middleboxes . . . . . . . . . . . . . . . . . .  Done

running 10s outbound test (client to server) . . . . . 290.81Kb/s

running 10s inbound test (server to client) . . . . . . 470.32kb/s

------  Client System Details  ------

OS data: Name = Windows XP, Architecture = x86, Version = 5.1

Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_04

------  Web100 Detailed Analysis  ------

Cable modem/DSL/T1 link found.

Link set to Full Duplex mode

No network congestion discovered.

Good network cable(s) found

Normal duplex operation found.

Web100 reports the Round trip time = 527.59 msec; the Packet size = 1460 Bytes; and

There were 7 packets retransmitted, 45 duplicate acks received, and 62 SACK blocks received

The connection was idle 0 seconds (0%) of the time

This connection is receiver limited 14.51% of the time.

  Increasing the the client's receive buffer (62.0 KB) will improve performance

This connection is network limited 85.47% of the time.

Web100 reports TCP negotiated the optional Performance Settings to:

RFC 2018 Selective Acknowledgment: ON

RFC 896 Nagle Algorithm: ON

RFC 3168 Explicit Congestion Notification: OFF

RFC 1323 Time Stamping: OFF

RFC 1323 Window Scaling: OFF

Packet size is preserved End-to-End

Server IP addresses are preserved End-to-End

Client IP addresses are preserved End-to-End

Share this post


Link to post
Share on other sites

WEB100 Kernel Variables:

Client: localhost/127.0.0.1

AckPktsIn: 249

AckPktsOut: 0

BytesRetrans: 10220

CongAvoid: 114

CongestionOverCount: 0

CongestionSignals: 1

CountRTT: 199

CurCwnd: 39420

CurMSS: 1460

CurRTO: 890

CurRwinRcvd: 64240

CurRwinSent: 16304

CurSsthresh: 32120

DSACKDups: 0

DataBytesIn: 0

DataBytesOut: 651160

DataPktsIn: 0

DataPktsOut: 446

DupAcksIn: 45

ECNEnabled: 0

FastRetran: 1

MaxCwnd: 65700

MaxMSS: 1460

MaxRTO: 1320

MaxRTT: 940

MaxRwinRcvd: 64240

MaxRwinSent: 16304

MaxSsthresh: 32120

MinMSS: 1460

MinRTO: 560

MinRTT: 190

MinRwinRcvd: 64240

MinRwinSent: 16304

NagleEnabled: 1

OtherReductions: 1

PktsIn: 249

PktsOut: 446

PktsRetrans: 7

X_Rcvbuf: 103424

RcvWinScale: 2147483647

SACKEnabled: 3

SACKsRcvd: 62

SendStall: 0

SlowStart: 59

SampleRTT: 650

SmoothedRTT: 630

X_Sndbuf: 103424

SndWinScale: 2147483647

SndLimTimeRwin: 1516369

SndLimTimeCwnd: 8933732

SndLimTimeSender: 2607

SndLimTransRwin: 1

SndLimTransCwnd: 2

SndLimTransSender: 1

SndLimBytesRwin: 39420

SndLimBytesCwnd: 611740

SndLimBytesSender: 0

SubsequentTimeouts: 0

SumRTT: 104990

Timeouts: 0

TimestampsEnabled: 0

WinScaleRcvd: 2147483647

WinScaleSent: 2147483647

DupAcksOut: 0

StartTimeUsec: 531681

Duration: 10455392

c2sData: 2

c2sAck: 2

s2cData: 9

s2cAck: 2

half_duplex: 0

link: 100

congestion: 0

bad_cable: 0

mismatch: 0

spd: 0.00

bw: 0.45

loss: 0.002242152

avgrtt: 527.59

waitsec: 0.00

timesec: 10.00

order: 0.1807

rwintime: 0.1451

sendtime: 0.0002

cwndtime: 0.8547

rwin: 0.4901

swin: 0.7891

cwin: 0.5013

rttsec: 0.527588

Sndbuf: 103424

aspd: 2.22635

Checking for mismatch on uplink

(speed > 50 [0>50], (xmitspeed < 5) [0.29<5]

(rwintime > .9) [0.14>.9], (loss < .01) [0.00<.01]

Checking for excessive errors condition

(loss/sec > .15) [2.24>.15], (cwndtime > .6) [0.85>.6],

(loss < .01) [0.00<.01], (MaxSsthresh > 0) [32120>0]

Checking for 10 Mbps link

(speed < 9.5) [0<9.5], (speed > 3.0) [0>3.0]

(xmitspeed < 9.5) [0.29<9.5] (loss < .01) [0.00<.01], (mylink > 0) [3.0>0]

Checking for Wireless link

(sendtime = 0) [2.0E=0], (speed < 5) [0<5]

(Estimate > 50 [0.45>50], (Rwintime > 90) [0.14>.90]

(RwinTrans/CwndTrans = 1) [1/2=1], (mylink > 0) [3.0>0]

Checking for DSL/Cable Modem link

(speed < 2) [0<2], (SndLimTransSender = 0) [1=0]

(SendTime = 0) [2.0E-4=0], (mylink > 0) [3.0>0]

Checking for half-duplex condition

(rwintime > .95) [0.14>.95], (RwinTrans/sec > 30) [0.1>30],

(SenderTrans/sec > 30) [0.1>30], OR (mylink <= 10) [3.0<=10]

Checking for congestion

(cwndtime > .02) [0.85>.02], (mismatch = 0) [0=0]

(MaxSsthresh > 0) [32120>0]

estimate = 0.45 based on packet size = 11Kbits, RTT = 527.59msec, and loss = 0.002242152

The theoretical network limit is 0.45 Mbps

The NDT server has a 101.0 KByte buffer which limits the throughput to 1.49 Mbps

Your PC/Workstation has a 62.0 KByte buffer which limits the throughput to 0.92 Mbps

The network based flow control limits the throughput to 0.95 Mbps

Client Data reports link is 'T1', Client Acks report link is 'T1'

Server Data reports link is '10 Gig', Server Acks report link is 'T1'

Share this post


Link to post
Share on other sites

TCP/Web100 Network Diagnostic Tool v5.3.3d

click START to begin

Checking for Middleboxes . . . . . . . . . . . . . . . . . .  Done

running 10s outbound test (client to server) . . . . . 290.81Kb/s

running 10s inbound test (server to client) . . . . . . 470.32kb/s

Your PC is connected to a Cable/DSL modem

Information: The receive buffer should be 193.20 Kbytes to maximize throughput

Share this post


Link to post
Share on other sites

Your connection shows a high latency of over 500 ms. Usual latency to the US is less than 300 ms. The causes for the slow speed could either be bad telephone line or electromagnetic interference (EMI) that is affecting your cable connection.

For further read on sources of EMI go to these links:

https://www.speedguide.net/read_articles.php?id=1885

https://www.speedguide.net/read_articles.php?id=117

Share this post


Link to post
Share on other sites

here is the log

The current date is: 05/02/2006

The current time is: 14:33:11.48

Microsoft Windows XP [Version 5.1.2600]

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

Reply from 67.18.179.85: bytes=32 time=132ms TTL=45

Reply from 67.18.179.85: bytes=32 time=140ms TTL=45

Reply from 67.18.179.85: bytes=32 time=140ms TTL=45

Reply from 67.18.179.85: bytes=32 time=140ms TTL=45

Reply from 67.18.179.85: bytes=32 time=140ms TTL=45

Reply from 67.18.179.85: bytes=32 time=140ms TTL=45

Reply from 67.18.179.85: bytes=32 time=140ms TTL=45

Reply from 67.18.179.85: bytes=32 time=140ms TTL=45

Reply from 67.18.179.85: bytes=32 time=156ms TTL=45

Reply from 67.18.179.85: bytes=32 time=140ms TTL=45

Reply from 67.18.179.85: bytes=32 time=140ms TTL=45

Reply from 67.18.179.85: bytes=32 time=140ms TTL=45

Ping statistics for 67.18.179.85:

    Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 132ms, Maximum = 156ms, Average = 140ms

Ping Complete.

Tracing route to testmy.net [67.18.179.85]

over a maximum of 30 hops:

  1    14 ms    15 ms    15 ms  pete-bam-1.inet.ntl.com [194.145.148.98]

  2    15 ms    15 ms    15 ms  pete-t2core-a-ge-wan62.inet.ntl.com [80.3.129.13]

  3    15 ms    31 ms    15 ms  nth-bb-a-so-130-0.inet.ntl.com [62.253.188.225]

  4    15 ms    31 ms    15 ms  nth-bb-b-ae0-0.inet.ntl.com [62.253.185.118]

  5    31 ms    15 ms    31 ms  pop-bb-a-so-100-0.inet.ntl.com [213.105.172.14]

  6    30 ms    31 ms    31 ms  195.50.91.69

  7    31 ms    15 ms    31 ms  ae-0-54.bbr2.london1.level3.net [4.68.116.98]

  8  140 ms  124 ms  124 ms  ae-0-0.bbr1.dallas1.level3.net [64.159.1.109]

  9  124 ms  124 ms  124 ms  ae-13-55.car3.dallas1.level3.net [4.68.122.143]

10  140 ms  140 ms  140 ms  4.78.220.10

11  140 ms  140 ms  171 ms  vl31.dsr02.dllstx3.theplanet.com [70.85.127.30]

12  140 ms  140 ms  140 ms  vl42.dsr02.dllstx4.theplanet.com [70.85.127.91]

13  140 ms  140 ms  140 ms  gi1-0-2.car17.dllstx4.theplanet.com [67.18.116.85]

14  140 ms  140 ms  140 ms  85.67-18-179.reverse.theplanet.com [67.18.179.85]

Trace complete.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...