Jump to content
Sign in to follow this  
Guh-reg

Need Help!

Recommended Posts

1. I am running Win98SE

2. My ISP is mediacom http://www.mchsi.com

The advertised speed for downloads is "up to 3 megabytes". They don't seem to advertise upload speeds. This is all I can find: "* Cable modems provide access speeds that are 50 times faster than 28.8Kbps dial-up connections. They are faster than 768Kbps digital subscriber line (DSL) services, and they don't tie up the phone line. Speeds may vary and are based on download rate.". My up load rate is already about 9% greater than the mchsi average, so no worries there.

3. Installed tweaking programs: II installed cablenut and used VanBuren's settings v7.0. No change. I also made some tweaks with DrTCP. I calculated my optimal RWIN at 49,640 and set the MRU for my wireless adapter to 1492.

Test results as asked: http://ttester.broadbandreports.com/tweak/block:46dd68e?service=cable&speed=3000&os=win98SE&via=normal

4. Test results:

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

Connection is:: 234 Kbps about 0.2 Mbps (tested with 97 kB)

Upload Speed is:: 29 kB/s

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

Test Time:: Fri Sep 30 2005 08:36:10 GMT-0400 (Eastern Daylight Time)

Bottom Line:: 4X faster than 56K 1MB upload in 35.31 sec

Diagnosis: Looks Great : 9.35 % faster than the average for host (mchsi.com)

Validation Link:: https://testmy.net/stats/id-3K4O5J6UF

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

Connection is:: 1493 Kbps about 1.5 Mbps (tested with 2992 kB)

Download Speed is:: 182 kB/s

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

Test Time:: Fri Sep 30 2005 09:05:53 GMT-0400 (Eastern Daylight Time)

Bottom Line:: 27X faster than 56K 1MB download in 5.63 sec

Diagnosis: May need help : running at only 45.16 % of your hosts average (mchsi.com)

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

Test results from http://nitro.ucsc.edu/ :

------  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 = 147.89 msec; the Packet size = 1452 Bytes; and

There were 5 packets retransmitted, 52 duplicate acks received, and 54 SACK blocks received

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

This connection is network limited 99.97% 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

Information: Network Middlebox is modifying MSS variable

Server IP addresses are preserved End-to-End

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

Server says [xxxxxxxxxxxxxx] but Client says [xxxxxxxxxxx]

Tracert and Ping program results:

Current date is Fri 09-30-2005

Current time is  9:12:43.68a

Windows 98 [Version 4.10.2222]

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

Reply from 67.18.179.85: bytes=32 time=44ms TTL=54

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

Reply from 67.18.179.85: bytes=32 time=42ms TTL=54

Reply from 67.18.179.85: bytes=32 time=42ms TTL=54

Ping statistics for 67.18.179.85:

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

Approximate round trip times in milli-seconds:

    Minimum = 42ms, Maximum =  47ms, Average =  43ms

Ping Complete.

All other steps done completed.

Note: All test results are from after all relevant recommended steps where followed.

Also I am on warless LAN sharing an internet connection. I use a befw11s4 v4 Linksys router with firmware version 1.52.02 and a wusb11 ver.2.6 wireless USB adapter ).  I would be very gratefull for any help!  :D

Share this post


Link to post
Share on other sites

Welcome to the forum, Guh-reg. :wave:

I would personally like to see a speed test on your wired connection straight to the modem (NOT wireless, and NOT through the router).

This will tell us if it is good or bad there, then we'll know where to start.

Share this post


Link to post
Share on other sites
Welcome to the forum, Guh-reg. wave

Thanks.

I would personally like to see a speed test on your wired connection straight to the modem (NOT wireless, and NOT through the router).

This will tell us if it is good or bad there, then we'll know where to start.

Will do. It might take me a few hours though (other people using it etc).

Share this post


Link to post
Share on other sites

Will do. It might take me a few hours though (other people using it etc).

Not a problem at all.

I am here on and off, and there is always someone else around to help.

I think we need to know where your connection stands straight from the cable modem before you can work on improvements through the router.

Share this post


Link to post
Share on other sites

Here are the test results. The TCPdump on this computer hasn't been tweaked yet.

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

Connection is:: 1058 Kbps about 1.1 Mbps (tested with 1013 kB)

Download Speed is:: 129 kB/s

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

Test Time:: Fri Sep 30 11:19:44 EDT 2005

Bottom Line:: 19X faster than 56K 1MB download in 7.94 sec

Diagnosis: May need help : running at only 31.99 % of your hosts average (mchsi.com)

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

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

Connection is:: 235 Kbps about 0.2 Mbps (tested with 97 kB)

Upload Speed is:: 29 kB/s

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

Test Time:: Fri Sep 30 11:20:35 EDT 2005

Bottom Line:: 4X faster than 56K 1MB upload in 35.31 sec

Diagnosis: Looks Great : 9.81 % faster than the average for host (mchsi.com)

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

TCP/Web100 Network Diagnostic Tool v5.3.3d

click START to begin

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

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

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

Your PC is connected to a Cable/DSL modem

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

More Details:

WEB100 Enabled Statistics:

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

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

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

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

OS data: Name = Windows 98, Architecture = x86, Version = 4.10

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

------  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 = 169.37 msec; the Packet size = 1460 Bytes; and

There were 14 packets retransmitted, 39 duplicate acks received, and 46 SACK blocks received

The connection stalled 1 times due to packet loss

The connection was idle 0.4 seconds (3.63%) of the time

This connection is network limited 99.97% of the time.

Excessive packet loss is impacting your performance, check the auto-negotiate function on your

local PC and network switch

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

http://ttester.broadbandreports.com/tweak/block:257a255?service=cable&speed=3000&os=win98SE&via=normal

Current date is Fri 09-30-2005

Current time is 12:29:37.22p

Windows 98 [Version 4.10.1998]

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

Reply from 67.18.179.85: bytes=32 time=39ms TTL=54

Reply from 67.18.179.85: bytes=32 time=39ms TTL=54

Reply from 67.18.179.85: bytes=32 time=39ms TTL=54

Reply from 67.18.179.85: bytes=32 time=39ms TTL=54

Ping statistics for 67.18.179.85:

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

Approximate round trip times in milli-seconds:

    Minimum = 39ms, Maximum =  39ms, Average =  39ms

Ping Complete.

Tracing route to testmy.net [67.18.179.85]

over a maximum of 30 hops:

  1    23 ms    10 ms    12 ms  10.20.50.1

  2    12 ms    14 ms    13 ms  12-215-19-129.client.mchsi.com [12.215.19.129]

  3    22 ms    26 ms    24 ms  12-215-0-18.client.mchsi.com [12.215.0.18]

  4    40 ms    38 ms    37 ms  gbr2-p70.attga.ip.att.net [12.123.21.6]

  5    41 ms    41 ms    41 ms  tbr2-p013602.attga.ip.att.net [12.122.12.37]

  6    48 ms    40 ms    40 ms  tbr1-cl1.dlstx.ip.att.net [12.122.2.89]

  7    39 ms    39 ms    40 ms  gar1-p360.dlrtx.ip.att.net [12.123.196.101]

  8    38 ms    39 ms    39 ms  12.119.136.14

  9    39 ms    42 ms    43 ms  vl31.dsr01.dllstx3.theplanet.com [70.85.127.29]

10    45 ms    51 ms    41 ms  dist-vlan41.dsr2-1.dllstx4.theplanet.com [70.85.127.83]

11    40 ms    40 ms    40 ms  gig1-0-1.tp-car9-1.dllstx4.theplanet.com [67.18.116.69]

12    41 ms    42 ms    53 ms  testmy.net [67.18.179.85]

Trace complete.

Share this post


Link to post
Share on other sites

I had to hook the PC back up to the WAP. I tweaked the TCP dump and got some improvement but still gettign reports of the same problem:

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

Connection is:: 2230 Kbps about 2.2 Mbps (tested with 2992 kB)

Download Speed is:: 272 kB/s

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

Test Time:: Sat Oct 1 02:21:54 EDT 2005

Bottom Line:: 40X faster than 56K 1MB download in 3.76 sec

Diagnosis: May need help : running at only 67.41 % of your hosts average (mchsi.com)

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

Current date is Sat 10-01-2005

Current time is  2:19:06.69a

Windows 98 [Version 4.10.1998]

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

Reply from 67.18.179.85: bytes=32 time=39ms TTL=54

Reply from 67.18.179.85: bytes=32 time=39ms TTL=54

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

Reply from 67.18.179.85: bytes=32 time=40ms TTL=54

Ping statistics for 67.18.179.85:

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

Approximate round trip times in milli-seconds:

    Minimum = 39ms, Maximum =  43ms, Average =  40ms

Ping Complete.

Tracing route to testmy.net [67.18.179.85]

over a maximum of 30 hops:

  1  <10 ms  <10 ms    1 ms  xxx.xxx.x.x

  2    11 ms    11 ms    11 ms  10.20.50.1

  3    14 ms    14 ms    16 ms  12-215-19-129.client.mchsi.com [12.215.19.129]

  4    24 ms    23 ms    28 ms  12-215-0-18.client.mchsi.com [12.215.0.18]

  5    38 ms    41 ms    41 ms  GBr2-p70.attga.ip.att.net [12.123.21.6]

  6    43 ms    42 ms    44 ms  tbr2-p013602.attga.ip.att.net [12.122.12.37]

  7    41 ms    42 ms    42 ms  tbr1-cl1.dlstx.ip.att.net [12.122.2.89]

  8    39 ms    40 ms    52 ms  12.122.82.37

  9    50 ms    41 ms    41 ms  12.119.136.14

10    42 ms    41 ms    39 ms  vl31.dsr02.dllstx3.theplanet.com [70.85.127.30]

11    40 ms    53 ms    38 ms  dist-vlan-42.dsr2-2.dllstx4.theplanet.com [70.85.127.91]

12    50 ms    43 ms    42 ms  gig1-0-1.tp-car9-1.dllstx4.theplanet.com [67.18.116.69]

13    41 ms    40 ms    41 ms  testmy.net [67.18.179.85]

Trace complete.

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

------  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 = 159.77 msec; the Packet size = 1460 Bytes; and

There were 16 packets retransmitted, 28 duplicate acks received, and 34 SACK blocks received

The connection stalled 2 times due to packet loss

The connection was idle 0.8 seconds (8.0%) of the time

This connection is network limited 99.97% of the time.

Excessive packet loss is impacting your performance, check the auto-negotiate function on your local PC and network switch

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 [xxxxxxxxxxxxx] but Client says [xxxxxxxxxxx]

I also thought this was intersting:

estimate = 0.27 based on packet size = 11Kbits, RTT = 159.77msec, and loss = 0.067567568

The theoretical network limit is 0.27 Mbps

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

Your PC/Workstation has a 46.0 KByte buffer which limits the throughput to 2.26 Mbps

The network based flow control limits the throughput to 0.62 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'

http://ttester.broadbandreports.com/tweak/block:ef754f?service=cable&speed=3000&os=win98SE&via=normal

Share this post


Link to post
Share on other sites

OKay, I fixed the packet loss problem (it was caused by a bug in win98 that caused packet redirection etc. I downloaded a patch and it fixed the packet loss problem) and I am no longer getting reports of throughput bieng limited by other network traffic or suggestions of adjusting reciever buffer size. Everything looks fine now but I am still only getting around 60-68% of my hosts average rate.

TCP/Web100 Network Diagnostic Tool v5.3.3d

click START to begin

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

running 10s outbound test (client to server) . . . . . 249.03kB/s

running 10s inbound test (server to client) . . . . . . 3.72Mb/s

Your PC is connected to a Cable/DSL modem

WEB100 Enabled Statistics:

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

running 10s outbound test (client to server) . . . . . 249.03kB/s

running 10s inbound test (server to client) . . . . . . 3.72Mb/s

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

OS data: Name = Windows 98, Architecture = x86, Version = 4.10

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

------  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 = 129.9 msec; the Packet size = 1460 Bytes; and

No packet loss was observed.

This connection is receiver limited 89.7% of the time.

This connection is network limited 10.28% 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

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

Server says [xxxxxxxxxxxxx] but Client says [xxxxxxxxxxxxxxx]

WEB100 Enabled Statistics:

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

running 10s outbound test (client to server) . . . . . 249.03kB/s

running 10s inbound test (server to client) . . . . . . 3.72Mb/s

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

OS data: Name = Windows 98, Architecture = x86, Version = 4.10

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

------  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 = 129.9 msec; the Packet size = 1460 Bytes; and

No packet loss was observed.

This connection is receiver limited 89.7% of the time.

This connection is network limited 10.28% 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

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

Server says [xxxxxxxxx] but Client says [xxxxxxxxx]

See, all better!

removed your IP adress, not a good idea to post em in public

Share this post


Link to post
Share on other sites
Sign in to follow this  

×
×
  • Create New...