Jump to content

What's wrong?


Moonrider

Recommended Posts

oo and i got a some check file in my D: Disk this what it writes.

The current date is: 2006.02.06

The current time is: 18:10:19,35

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=697ms TTL=47

Reply from 67.18.179.85: bytes=32 time=729ms TTL=47

Reply from 67.18.179.85: bytes=32 time=757ms TTL=47

Reply from 67.18.179.85: bytes=32 time=711ms TTL=47

Reply from 67.18.179.85: bytes=32 time=663ms TTL=47

Reply from 67.18.179.85: bytes=32 time=706ms TTL=47

Reply from 67.18.179.85: bytes=32 time=717ms TTL=47

Reply from 67.18.179.85: bytes=32 time=723ms TTL=47

Reply from 67.18.179.85: bytes=32 time=695ms TTL=47

Reply from 67.18.179.85: bytes=32 time=850ms TTL=47

Reply from 67.18.179.85: bytes=32 time=700ms TTL=47

Reply from 67.18.179.85: bytes=32 time=680ms TTL=47

Ping statistics for 67.18.179.85:

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

Approximate round trip times in milli-seconds:

    Minimum = 663ms, Maximum = 850ms, Average = 719ms

Ping Complete.

Tracing route to testmy.net [67.18.179.85]

over a maximum of 30 hops:

  1    2 ms    7 ms    2 ms  192.168.0.1

  2  531 ms    *      563 ms  193.219.14.254

  3  554 ms  540 ms  594 ms  193.219.13.5

  4    *        *        *    Request timed out.

  5    *        *        *    Request timed out.

  6  510 ms  518 ms  519 ms  212-59-1-253.ip.takas.lt [212.59.1.253]

  7  649 ms  624 ms  673 ms  sl-gw10-fra-6-2.sprintlink.net [217.151.254.189]

  8  518 ms  620 ms  570 ms  81.198.168.9

  9  597 ms  562 ms    *    s-b3-geth2-0.telia.net [213.248.67.105]

10    *      509 ms  688 ms  sl-bb24-nyc-9-0.sprintlink.net [144.232.9.166]

11  535 ms  676 ms  687 ms  kbn-bb2-pos0-0-0.telia.net [213.248.65.29]

12  674 ms  808 ms  694 ms  sl-bb24-chi-2-0.sprintlink.net [144.232.9.156]

13  693 ms    *      693 ms  sl-bb22-chi-9-0.sprintlink.net [144.232.26.110]

14  723 ms  731 ms  580 ms  so-9-1.car1.newyork1.level3.net [209.244.160.161]

15  606 ms  612 ms  738 ms  sl-timewarner-14-0.sprintlink.net [144.223.241.78]

16  716 ms  633 ms  771 ms  as-0-0.bbr2.dallas1.level3.net [64.159.0.137]

17    *      685 ms  823 ms  ae-23-54.car3.dallas1.level3.net [4.68.122.111]

18    *      658 ms  709 ms  4.78.221.146

19  723 ms  664 ms  657 ms  168.215.241.150

20  628 ms  699 ms  672 ms  vl31.dsr02.dllstx3.theplanet.com [70.85.127.30]

21    *        *      739 ms  gi1-0-2.car17.dllstx4.theplanet.com [67.18.116.85]

22  652 ms  593 ms  584 ms  gi1-0-2.car17.dllstx4.theplanet.com [67.18.116.85]

23  694 ms  750 ms  729 ms  85.67-18-179.reverse.theplanet.com [67.18.179.85]

Trace complete.

Link to comment
Share on other sites

I don't have modem , and my internet is not connected thru phone , i have antena near the my computer's window outside . And i have a white box with 2 cables connecting with 1 very big whoose connecting to antena . One blue cable connected to the white box and that blue cable goes to computer . The second is black wich connects with the Big one . And that big one connects to antena.

Link to comment
Share on other sites

Download Very Good! :

Your connection is: 336 Kbps      (about 0.3 Mbps)

You downloaded at: 41 kB/s

Your TRuSPEED: ^info^ 360 Kbps :: 44 kB/s (7% overhead factored)

Bottom Line: You are running: 6 times faster than 56K and can download 1 megabyte in 24.98 second(s)

Diagnosis: ^info^ Awesome! 20% + : 145.26 % faster than the average for host (is.lt)

Results Comparison

Upload :

Your connection is: 17 Kbps      (about 0 Mbps)

You uploaded at: 2 kB/s

Your TRuSPEED: ^info^ 18 Kbps :: 2 kB/s (7% overhead factored)

Bottom Line: You are running: 0 times faster than 56K and can upload 1 megabyte in 512 second(s)

Diagnosis: ^info^ May need help : running at only 80.95 % of your hosts average (is.lt)

Upload still bad :(

Link to comment
Share on other sites

I do not think your line is 256/256 Kbps as you can test faster than that. Maybe it is 512/512 like your friend. Check the two cable connections in the white box to see if they are ok. Also make sure there is no electrical devices close to the white box. If yes, move the electrical devices a few feet away from the white box.

Try this ccs file.

Link to comment
Share on other sites

Your connection is: 233 Kbps      (about 0.2 Mbps)

You downloaded at: 28 kB/s

Your TRuSPEED: ^info^ 249 Kbps :: 30 kB/s (7% overhead factored)

Bottom Line: You are running: 4 times faster than 56K and can download 1 megabyte in 36.57 second(s)

Diagnosis: ^info^ Awesome! 20% + : 56.38 % faster than the average for host (is.lt)

Upload still very bad . I think that ccs file you gave me 32120-32120-1500.ccs is better than this one 64240-6420st.ccs. Coz download speed was better then . No electiric things near my white box.

Link to comment
Share on other sites

Ohh ok , i got it now :

Statistics:

WEB100 Enabled Statistics:

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

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

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

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

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

Java data: Vendor = Sun Microsystems Inc., Version = 1.4.2

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

Cable modem/DSL/T1 link found.

Link set to Full Duplex mode

Information: throughput is limited by other network traffic.

Good network cable(s) found

Normal duplex operation found.

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

There were 9 packets retransmitted, 29 duplicate acks received, and 29 SACK blocks received

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

This connection is network limited 99.66% of the time.

  Contact your local network administrator to report a network problem

  Contact your local network admin and report excessive packet reordering

    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

Information: Network Address Translation (NAT) box is modifying the Client's IP address

Server says [195.182.95.61] but Client says [192.168.0.11]

More Details :

WEB100 Kernel Variables:

Client: localhost/127.0.0.1

AckPktsIn: 117

AckPktsOut: 0

BytesRetrans: 13140

CongAvoid: 51

CongestionOverCount: 0

CongestionSignals: 2

CountRTT: 81

CurCwnd: 13140

CurMSS: 1460

CurRTO: 616

CurRwinRcvd: 64240

CurRwinSent: 5840

CurSsthresh: 8760

DSACKDups: 0

DataBytesIn: 0

DataBytesOut: 293460

DataPktsIn: 0

DataPktsOut: 201

DupAcksIn: 29

ECNEnabled: 0

FastRetran: 2

MaxCwnd: 26280

MaxMSS: 1460

MaxRTO: 959

MaxRTT: 642

MaxRwinRcvd: 64240

MaxRwinSent: 5840

MaxSsthresh: 13140

MinMSS: 1460

MinRTO: 614

MinRTT: 301

MinRwinRcvd: 64240

MinRwinSent: 5840

NagleEnabled: 1

OtherReductions: 0

PktsIn: 117

PktsOut: 201

PktsRetrans: 9

X_Rcvbuf: 1114624

RcvWinScale: 2147483647

SACKEnabled: 3

SACKsRcvd: 29

SendStall: 0

SlowStart: 28

SampleRTT: 362

SmoothedRTT: 407

X_Sndbuf: 1114624

SndWinScale: 2147483647

SndLimTimeRwin: 0

SndLimTimeCwnd: 10809887

SndLimTimeSender: 37246

SndLimTransRwin: 0

SndLimTransCwnd: 1

SndLimTransSender: 1

SndLimBytesRwin: 0

SndLimBytesCwnd: 293460

SndLimBytesSender: 0

SubsequentTimeouts: 0

SumRTT: 35600

Timeouts: 0

TimestampsEnabled: 0

WinScaleRcvd: 2147483647

WinScaleSent: 2147483647

DupAcksOut: 0

StartTimeUsec: 203757

Duration: 10857620

c2sData: 2

c2sAck: 1

s2cData: 8

s2cAck: 2

half_duplex: 0

link: 100

congestion: 1

bad_cable: 0

mismatch: 0

spd: 0.00

bw: 0.25

loss: 0.009950249

avgrtt: 439.51

waitsec: 0.00

timesec: 10.00

order: 0.2479

rwintime: 0.0000

sendtime: 0.0034

cwndtime: 0.9966

rwin: 0.4901

swin: 8.5039

cwin: 0.2005

rttsec: 0.439506

Sndbuf: 1114624

Checking for mismatch condition

(cwndtime > .3) [0.99>.3], (MaxSsthresh > 0) [13140>0],

(PktsRetrans/sec > 2) [0.9>2], (estimate > 2) [0.25>2]

Checking for mismatch on uplink

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

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

Checking for excessive errors condition

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

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

Checking for 10 Mbps link

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

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

Checking for Wireless link

(sendtime = 0) [0.00=0], (speed < 5) [0<5]

(Estimate > 50 [0.25>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) [0.0034=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) [13140>0]

estimate = 0.25 based on packet size = 11Kbits, RTT = 439.51msec, and loss = 0.009950249

The theoretical network limit is 0.25 Mbps

The NDT server has a 1088.0 KByte buffer which limits the throughput to 19.34 Mbps

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

The network based flow control limits the throughput to 0.45 Mbps

Client Data reports link is 'T1', Client Acks report link is 'Dial-up'

Server Data reports link is 'OC-48', Server Acks report link is 'T1'

Link to comment
Share on other sites

Go to this site. A smaller window will appear . Click 'START' button and the test will begin. When test is completed, 2 buttons appear at the bottom of the small window.

Click "STATISTICS' and a report will come out. Copy report and save to Wordpad.

Click 'MORE DETAILS' and another report will come out. Copy report and save with first report inside Wordpad.

Then copy the report in Wordpad and post to this forum. 

Link to comment
Share on other sites

K: More details :

WEB100 Kernel Variables:

Client: localhost/127.0.0.1

AckPktsIn: 125

AckPktsOut: 0

BytesRetrans: 11680

CongAvoid: 48

CongestionOverCount: 0

CongestionSignals: 2

CountRTT: 76

CurCwnd: 11680

CurMSS: 1460

CurRTO: 811

CurRwinRcvd: 32120

CurRwinSent: 5840

CurSsthresh: 10220

DSACKDups: 0

DataBytesIn: 0

DataBytesOut: 293460

DataPktsIn: 0

DataPktsOut: 201

DupAcksIn: 38

ECNEnabled: 0

FastRetran: 2

MaxCwnd: 26280

MaxMSS: 1460

MaxRTO: 1135

MaxRTT: 783

MaxRwinRcvd: 32120

MaxRwinSent: 5840

MaxSsthresh: 13140

MinMSS: 1460

MinRTO: 811

MinRTT: 301

MinRwinRcvd: 32120

MinRwinSent: 5840

NagleEnabled: 1

OtherReductions: 0

PktsIn: 125

PktsOut: 201

PktsRetrans: 8

X_Rcvbuf: 1114624

RcvWinScale: 2147483647

SACKEnabled: 3

SACKsRcvd: 38

SendStall: 0

SlowStart: 26

SampleRTT: 417

SmoothedRTT: 488

X_Sndbuf: 1114624

SndWinScale: 2147483647

SndLimTimeRwin: 0

SndLimTimeCwnd: 10503616

SndLimTimeSender: 37726

SndLimTransRwin: 0

SndLimTransCwnd: 1

SndLimTransSender: 1

SndLimBytesRwin: 0

SndLimBytesCwnd: 293460

SndLimBytesSender: 0

SubsequentTimeouts: 0

SumRTT: 38876

Timeouts: 0

TimestampsEnabled: 0

WinScaleRcvd: 2147483647

WinScaleSent: 2147483647

DupAcksOut: 0

StartTimeUsec: 430746

Duration: 10553072

c2sData: 2

c2sAck: 1

s2cData: 2

s2cAck: 2

half_duplex: 0

link: 100

congestion: 1

bad_cable: 0

mismatch: 0

spd: 0.00

bw: 0.22

loss: 0.009950249

avgrtt: 511.53

waitsec: 0.00

timesec: 10.00

order: 0.3040

rwintime: 0.0000

sendtime: 0.0036

cwndtime: 0.9964

rwin: 0.2451

swin: 8.5039

cwin: 0.2005

rttsec: 0.511526

Sndbuf: 1114624

Checking for mismatch condition

(cwndtime > .3) [0.99>.3], (MaxSsthresh > 0) [13140>0],

(PktsRetrans/sec > 2) [0.8>2], (estimate > 2) [0.22>2]

Checking for mismatch on uplink

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

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

Checking for excessive errors condition

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

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

Checking for 10 Mbps link

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

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

Checking for Wireless link

(sendtime = 0) [0.00=0], (speed < 5) [0<5]

(Estimate > 50 [0.22>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) [0.0036=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) [13140>0]

estimate = 0.22 based on packet size = 11Kbits, RTT = 511.53msec, and loss = 0.009950249

The theoretical network limit is 0.22 Mbps

The NDT server has a 1088.0 KByte buffer which limits the throughput to 16.62 Mbps

Your PC/Workstation has a 31.0 KByte buffer which limits the throughput to 0.47 Mbps

The network based flow control limits the throughput to 0.39 Mbps

Client Data reports link is 'T1', Client Acks report link is 'Dial-up'

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

Now the Statistics :

WEB100 Enabled Statistics:

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

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

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

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

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

Java data: Vendor = Sun Microsystems Inc., Version = 1.4.2

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

Cable modem/DSL/T1 link found.

Link set to Full Duplex mode

Information: throughput is limited by other network traffic.

Good network cable(s) found

Normal duplex operation found.

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

There were 8 packets retransmitted, 38 duplicate acks received, and 38 SACK blocks received

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

This connection is network limited 99.64% of the time.

  Contact your local network administrator to report a network problem

  Contact your local network admin and report excessive packet reordering

    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

Information: Network Address Translation (NAT) box is modifying the Client's IP address

Server says [195.182.95.61] but Client says [192.168.0.11]

The speeds :

Download:

Your connection is: 235 Kbps      (about 0.2 Mbps)

You downloaded at: 29 kB/s

Your TRuSPEED: ^info^ 251 Kbps :: 31 kB/s (7% overhead factored)

Bottom Line: You are running: 4 times faster than 56K and can download 1 megabyte in 35.31 second(s)

Diagnosis: ^info^ Awesome! 20% + : 45.06 % faster than the average for host (is.lt)

Upload :

Your connection is: 38 Kbps      (about 0 Mbps)

You uploaded at: 5 kB/s

Your TRuSPEED: ^info^ 41 Kbps :: 5 kB/s (7% overhead factored)

Bottom Line: You are running: 1 times faster than 56K and can upload 1 megabyte in 204.8 second(s)

Diagnosis: ^info^ Awesome! 20% + : 65.22 % faster than the average for host (is.lt)

Results Comparison

Rofl I got one thing . That my Download speed is Typical DLS or Cable coz my internet tested the 380++ file in 9,5 seconds . DSL 3-12 . But ! The Upload is like Dial-UP.

Link to comment
Share on other sites

You can choose to use any of these 2 ccs files:

32120-32120  this is good for RTT = 500-700 ms

32120-16060  this is good for RTT = 400-500 ms

RTT means round trip time. It is the time for a signal to leave your computer until the info from the website reach you.

Cablenut settings in these 2 files makes your computer optimum.

You have to contact your ISP to ask why upload speed is too bad. The problem is not with your computer. It is with the network of the ISP.

Link to comment
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
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
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.

×
×
  • Create New...