REALLY Need Help

[Jodokast96]

New here, so Hi to everyone.  Here are the problems I've been having.  Rather than typing it all out (again), here's a link to my current situation.  http://www.dslreports.com/forum/remark,15258334  I believe I've covered everything from the "Before you post" sticky.  ZA has been uninstalled, but there is no difference.  Results on the following tests show about the same pattern as those from my link.  Can anyone help me out here?

I have MTU set to 1492, not 1484.  DSLReports TweakTest shows Max packet sent (MTU) as 1484 and Max packet recd (MTU) as 1492.

TCP options string = 020405a401010402

MTU = 1484

MTU is somewhat optimized for broadband. If you're not on a PPPoE DSL connection that limits packet size, consider increasing your MTU to 1500 for optimal throughput.

MSS = 1444

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

Default Receive Window (RWIN) = 13068

RWIN Scaling (RFC1323) = 0 bits

Unscaled Receive Window = 13068

For optimum performance, consider changing RWIN to a multiple of MSS.

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

508288 (MSS x 44 * scale factor of

254144 (MSS x 44 * scale factor of 4)

127072 (MSS x 44 * scale factor of 2)

63536 (MSS x 44) 

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

Your RcvWindow limits you to: 522.72 kbps (65.34 KBytes/s) @ 200ms

Your RcvWindow limits you to: 209.088 kbps (26.136 KBytes/s) @ 500ms

Consider increasing your RWIN value to optimize TCP/IP for broadband.

MTU Discovery (RFC1191) = ON

Time to live left = 123 hops

TTL value is ok.

Timestamps (RFC1323) = OFF

Selective Acknowledgements (RFC2018) = ON

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

UCSC TEST:

TCP/Web100 Network Diagnostic Tool v5.3.3d

click START to begin

Another client is currently being served, your test will begin within 45 seconds

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

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

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

Your PC is connected to a Cable/DSL modem

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

Testmy.net SmartTest:

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

Connection is:: 1711 Kbps about 1.7 Mbps (tested with 2992 kB)

Download Speed is:: 209 kB/s

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

Test Time:: Wed Jan 18 06:28:17 EST 2006

Bottom Line:: 31X faster than 56K 1MB download in 4.9 sec

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

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

Testmy.net NY server:

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

Connection is:: 2713 Kbps about 2.7 Mbps (tested with 3151 kB)

Download Speed is:: 331 kB/s

Tested From:: http://www.bafserv.com

Test Time:: 

Bottom Line:: 48X faster than 56K 1MB download in 3.09 sec

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

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

Ping and Tracert Results:

The current date is: Wed 01/18/2006

The current time is:  6:22:41.43

Microsoft Windows 2000 [Version 5.00.2195]

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

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

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

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

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

Ping statistics for 67.18.179.85:

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

Approximate round trip times in milli-seconds:

    Minimum = 49ms, Maximum =  50ms, Average =  49ms

Ping Complete.

Tracing route to testmy.net [67.18.179.85]over a maximum of 30 hops:

  1   <10 ms   <10 ms   <10 ms  192.168.0.1

  2     7 ms     7 ms     7 ms  10.5.40.1

  3     6 ms     6 ms     6 ms  130.81.35.176

  4    11 ms    11 ms    18 ms  so-6-0-0-0.PEER-RTR1.NWK80.verizon-gni.net [130.81.17.157]

  5    11 ms    11 ms    11 ms  so-9-1.car2.Newark1.Level3.net [4.79.236.33]

  6    11 ms    11 ms    11 ms  ae-1-56.bbr2.Newark1.Level3.net [4.68.99.161]

  7    52 ms    51 ms    51 ms  as-0-0.bbr2.Dallas1.Level3.net [64.159.0.137]

  8    52 ms    51 ms    51 ms  ae-13-55.car3.Dallas1.Level3.net [4.68.122.143]

  9    49 ms    49 ms    48 ms  4.78.221.146

10    49 ms    49 ms    49 ms  vl32.dsr02.dllstx3.theplanet.com [70.85.127.62]

11    49 ms    49 ms    49 ms  vl42.dsr02.dllstx4.theplanet.com [70.85.127.91]

12    50 ms    49 ms    49 ms  gi1-0-2.car17.dllstx4.theplanet.com [67.18.116.85]

13    49 ms    50 ms    49 ms  85.67-18-179.reverse.theplanet.com [67.18.179.85]

Trace complete.

[trogers]

UCSC TEST:

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

Your RWIN is too low - Default Receive Window (RWIN) = 13068

Try my Cablenut setting on this thread:

http://www.testmy.net/forum/index.php?PHPSESSID=bc16d35c7501526590ad0ba48bed5f11&topic=11176.0

You will need to download the Cablenut program v 4.08 to run the ccs file.

[Jodokast96]

Nope, same results.

[trogers]

Here is my ccs file for bandwidth 1500kpbs. If your bandwidth is different, you may need to modify the RWIN and TCP values of this file.

[Jodokast96]

YGPM

[cholla]

This is for XP but if the registry key is in 2000 then you can probably change the MTU to where you want it this way.The PMTUDiscovery is in Cablenut.

I made some changes in this I think this is better information.

I find some conflicts of information on this .So I guess you need to try it both ways

if you are having problems setting the MTU.

EnablePMTUDiscovery

When set to 1 (True), TCP attempts to discover MTU automatically over the path to a remote host. Setting this parameter to

0 causes MTU to default to 576 which reduces overall performance over high speed connections.

Setting MTU overrides the default MTU for the network interface it is added to. Note that if

EnablePMTUDiscovery is set to 1, TCP will use the smaller value of this local MTU and the

"Discovered" MTU of the underlying network connection. If you'd rather use only the MTU value

specified here, you'd have to disable PMTUDiscovery, which would prevent your system from

detecting the network MTU.

HKLMSYSTEMCurrentControlSetServicesTcpipParameters

EnablePMTUDiscovery="1" (DWORD - boolean, valid settings are 0-->False and 1-->True. Many connections perform better with

this entry at 1, however, if you prefer to set your upstream to send fixed 1500 packets, you might want to use 0 instead).

When set at 1, establishing connections and initial transfer speed might slow down a bit, however you will get better

throughput if somewhere in the path large packets need to be fragmented.

To modify the PPPoE MTU size, create the following registry key:

HKEY_LOCAL_MACHINESystemCurrentControlSetServicesNdiswanParametersProtocols0

Then add the following registry entries.Entry name Data type Value data

ProtocolType REG_DWORD 0x00000800

PPPProtocolType REG_DWORD 0x00000021

ProtocolMTU REG_DWORD the appropriate MTU size (in decimal)

To do this: 1. Click Start, click Run, type regedit, and then click OK.

2. Locate and then click the following key in the registry:

HKEY_LOCAL_MACHINESystemCurrentControlSetServicesNdiswanParameters

3. On the Edit menu, point to New, and then click Key.

4. Type Protocols, and then press ENTER.

5. On the Edit menu, point to New, and then click Key.

6. Type 0, and then press ENTER.

7. On the Edit menu, point to New, and then click DWORD Value.

8. Type ProtocolType, and then press ENTER.

9. On the Edit menu, click Modify.

10. Type 800, and then click OK.

11. On the Edit menu, point to New, and then click DWORD Value.

12. Type PPPProtocolType, and then press ENTER.

13. On the Edit menu, click Modify.

14. Type 21, and then click OK.

15. On the Edit menu, point to New, and then click DWORD Value.

16. Type ProtocolMTU, and then press ENTER.

17. On the Edit menu, click Modify.

18. Type the appropriate MTU size (decimal value), and then click OK.

19. Quit Registry Editor.

Notes