Help my tweaking

_freelancer_ · Post by **_freelancer_** » Sat Jul 19, 2003 10:07 am

1. ADSL PPPoE Encapsulation
2. Sapo.ADSL 512/128 (Down/Up)
3. THIS IS WHERE I NEED HELP, the TCP Analyzer can't retrieve the correct IP how can i test my connection?
4. Is speakeasy still making connection tests?? Don't think so.
5. Windows XP.

Plz help me

Everything's as mnosteele asked

mnosteele52 · Post by **mnosteele52** » Sat Jul 19, 2003 12:29 pm

If the TCP/IP Analyzer doesn't show your correct IP then most likely you are behind a proxy. Please post an analyzer test.

_freelancer_ · Post by **_freelancer_** » Sat Jul 19, 2003 12:34 pm

SpeedGuide.net TCP/IP Analyzer

TCP properties for IP = 194.65.14.76 ()
Browser/OS = Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.0.3705; .NET CLR 1.1.4322)
Notes: Read the Analyzer FAQ if the above is not your IP address.

TCP options string = 020405ac01010402
MTU = 1492
MTU is optimized for PPoE DSL broadband. If not, consider raising MTU to 1500 for optimal throughput.
MSS = 1452
MSS is optimized for PPPoE DSL broadband. If not, consider raising MTU to 1500 for maximum throughput.

Default Receive Window (RWIN) = 65535
RWIN Scaling (RFC1323) = 0 bits
Unscaled Receive Window = 65535

Note: Under Windows 9x, if you have RWIN set to any other value, and the Analyzer reports 65535 you might need to install the MS Vtcp386 fix.
For optimum performance, consider changing RWIN to a multiple of MSS.
Other values for RWIN that might work well with your current MTU/MSS:
511104 (MSS x 44 * scale factor of 8)
255552 (MSS x 44 * scale factor of 4)
127776 (MSS x 44 * scale factor of 2)
63888 (MSS x 44)
bandwidth * delay product:

Your RcvWindow limits you to: 2621.4 kbps (327.675 KBytes/s) @ 200ms
Your RcvWindow limits you to: 1048.56 kbps (131.07 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 40 hops

TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349) = 00100000

Precedence (priority) = 000 (routine)
Delay = 0 (normal delay)
Throughput = 0 (normal throughput)
Reliability = 1 (high reliability)
Cost = 0 (normal cost)

if there is anyway of introducing the ip myself ill doit

mnosteele52 · Post by **mnosteele52** » Sat Jul 19, 2003 2:54 pm

I see you are using CableNut so use the following settings, after you do all of the following please post another analyzer test.

DefaultReceiveWindow = 65535
DefaultSendWindow = 16384
DisableAddressSharing = 1
InitialLargeBufferCount = 200
InitialMediumBufferCount = 480
InitialSmallBufferCount = 640
LargeBufferSize = 819200
MaxFastTransmit = 64000
MediumBufferSize = 150400
PriorityBoost = 0
SmallBufferSize = 12800
TransmitWorker = 32
FastSendDatagramThreshold = 1024
EnableFastRouteLookup = 1
EnablePMTUDiscovery = 1
IgnorePushBitsOnReceive = 0
GlobalMaxTcpWindowSize = 17424
MaxFreeTcbs = 8000
MaxHashTableSize = 16384
MaxNormLookupMemory = 5000000
SackOpts = 1
SynAttackProtect = 1
Tcp1323Opts = 0
TcpLogLevel = 1
TcpMaxDupAcks = 3
TcpMaxHalfOpen = 100
TcpMaxHalfRetried = 80
TcpRecvSegmentSize = 1452
TcpSendSegmentSize = 1452
TcpTimedWaitDelay = 30
TcpUseRFC1122UrgentPointer = 0
TcpWindowSize = 17424
MaxConnectionsPer1_0Server = 10
MaxConnectionsPerServer = 8
DefaultTTL = 64
DisableUserTOSSetting = 0
TcpMaxDataRetransmissions = 6
DefaultTOSValue = 90

VERY IMPORTANT TO DO THE FOLLOWING

1. Under your LAN connection - properties - general tab, uninstall all the protocols there that you do not need.

2. Open IE and select tools - internet options - connections - LAN settings, make sure NOTHING there is checked.

3. Make sure you have the latest drivers for your NIC from the manufacturer. Set your NIC duplex mode to 10mb half duplex for Cable, for DSL it is ISP dependent unless you are using a router, if so then set it to 100mb full duplex for both Cable & DSL (the instructions are in my Help & Tips link). If you are using a router make sure you have the latest firmware.

4. Clear your temporary internet files.

5. Power cycle your modem, unplug it for atleast 15 seconds.

6. Download and update then do a scan with SpyBot 1.2 & Ad Aware 6.0 to remove any spyware then install and update SpywareBlaster to stay spyware FREE. YOU MUST USE BOTH AD AWARE & SPYBOT TO ENSURE YOU ARE SPYWARE FREE SINCE ONE FINDS WHAT THE OTHER MISSES.

7. Make sure you do the faster web page tweak in my Help & Tips link.

_freelancer_ · Post by **_freelancer_** » Sat Jul 19, 2003 3:29 pm

SpeedGuide.net TCP/IP Analyzer

TCP properties for IP = 194.65.14.76 ()
Browser/OS = Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.0.3705; .NET CLR 1.1.4322)
Notes: Read the Analyzer FAQ if the above is not your IP address.

TCP options string = 020405ac01010402
MTU = 1492
MTU is optimized for PPoE DSL broadband. If not, consider raising MTU to 1500 for optimal throughput.
MSS = 1452
MSS is optimized for PPPoE DSL broadband. If not, consider raising MTU to 1500 for maximum throughput.

Default Receive Window (RWIN) = 65535
RWIN Scaling (RFC1323) = 0 bits
Unscaled Receive Window = 65535

Note: Under Windows 9x, if you have RWIN set to any other value, and the Analyzer reports 65535 you might need to install the MS Vtcp386 fix.
For optimum performance, consider changing RWIN to a multiple of MSS.
Other values for RWIN that might work well with your current MTU/MSS:
511104 (MSS x 44 * scale factor of 8)
255552 (MSS x 44 * scale factor of 4)
127776 (MSS x 44 * scale factor of 2)
63888 (MSS x 44)
bandwidth * delay product:

Your RcvWindow limits you to: 2621.4 kbps (327.675 KBytes/s) @ 200ms
Your RcvWindow limits you to: 1048.56 kbps (131.07 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 40 hops

TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349) = 00100000

Precedence (priority) = 000 (routine)
Delay = 0 (normal delay)
Throughput = 0 (normal throughput)
Reliability = 1 (high reliability)
Cost = 0 (normal cost)

here it goes

mnosteele52 · Post by **mnosteele52** » Sat Jul 19, 2003 3:36 pm

OK if you did everything properly (including rebooting after changing all the settings) then your ISP is setting you behind a proxy and there is nothing you can do.

_freelancer_ · Post by **_freelancer_** » Sat Jul 19, 2003 3:48 pm

sry i hadnt reebooted:
SpeedGuide.net TCP/IP Analyzer

TCP properties for IP = 194.65.14.76 ()
Browser/OS = Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.0.3705; .NET CLR 1.1.4322)
Notes: Read the Analyzer FAQ if the above is not your IP address.

TCP options string = 020405ac01010402
MTU = 1492
MTU is optimized for PPoE DSL broadband. If not, consider raising MTU to 1500 for optimal throughput.
MSS = 1452
MSS is optimized for PPPoE DSL broadband. If not, consider raising MTU to 1500 for maximum throughput.

Default Receive Window (RWIN) = 17424
RWIN Scaling (RFC1323) = 0 bits
Unscaled Receive Window = 17424

RWIN is a multiple of MSS
Other values for RWIN that might work well with your current MTU/MSS:
511104 (MSS x 44 * scale factor of 8)
255552 (MSS x 44 * scale factor of 4)
127776 (MSS x 44 * scale factor of 2)
63888 (MSS x 44)
bandwidth * delay product:

Your RcvWindow limits you to: 696.96 kbps (87.12 KBytes/s) @ 200ms
Your RcvWindow limits you to: 278.784 kbps (34.848 KBytes/s) @ 500ms
Consider increasing your RWIN value to optimize TCP/IP for broadband.
MTU Discovery (RFC1191) = ON
Time to live left = 56 hops

TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349) = 00100000

Precedence (priority) = 000 (routine)
Delay = 0 (normal delay)
Throughput = 0 (normal throughput)
Reliability = 1 (high reliability)
Cost = 0 (normal cost)

mnosteele52 · Post by **mnosteele52** » Sat Jul 19, 2003 8:15 pm

Well your settings look great, has your speed improved any?

pino · Post by **pino** » Thu Jul 24, 2003 10:16 am

hi steele52 ,

how you can said if the last analyzer more better than before ?
if i see the diff only on ttl and rcv @200+@500

the last analyzer result get bigger for ttl and smaller for rcv @200+@500

so how you read the result ?

mnosteele52 · Post by **mnosteele52** » Thu Jul 24, 2003 10:52 am

Originally posted by pino
hi steele52 ,

how you can said if the last analyzer more better than before ?
if i see the diff only on ttl and rcv @200+@500

the last analyzer result get bigger for ttl and smaller for rcv @200+@500

so how you read the result ?

You need to understand the analyzer, ALL it does is tell you your current TCP/IP registry parameters....... that is ALL. You also need to understand how the RWIN value works, too large and you retransmit too many packets thereby slowing your connection down. His caps are 512 kilobits download, I gave him a value based on his caps and a latency of about 300ms which should be as high as ever gets. TTL is irrelevant to anything.

pino · Post by **pino** » Fri Jul 25, 2003 10:05 am

so , why you don't gave him 20440 for tcp windowsize ?
also maybe you can explain the relevantie of cablenut items ,
because ussualy the different only rcvwindow,sentwindow and the tcpwindowsize

tnx

mnosteele52 · Post by **mnosteele52** » Fri Jul 25, 2003 5:06 pm

Originally posted by pino
so , why you don't gave him 20440 for tcp windowsize ?
also maybe you can explain the relevantie of cablenut items ,
because ussualy the different only rcvwindow,sentwindow and the tcpwindowsize

tnx

I don't understand your first question, why would I give the value you suggested? As for the CableNut values, there is a link to the definitions to all the values in my help & tips link.

pino · Post by **pino** » Fri Jul 25, 2003 7:25 pm

if use j79zlr formula get tcpwindowsize 20440
and your formula get tcpwindowsize 19200

here you give him 17520

about cablenut i mean ,
for reduce retransmited packet i must change eg largebuffer size or default rcvwindow or similar like that

mnosteele52 · Post by **mnosteele52** » Fri Jul 25, 2003 7:36 pm

Nowhere in this thread has he said what his latency is so how did you find the value 20440? Your TcpWindowSize is based on your max latency and caps, the value I gave him is an average value that should work well with his caps, since I don't know his max latency I can't give him an exact value.

pino · Post by **pino** » Sat Jul 26, 2003 2:52 am

from help&tips

TcpReceiveWindow (RWIN) Formula

(Maximum Bandwidth x Maximum Anticipated Latency) / 8

Example of my connection with a 3000 download cap with a maximum latency of 100 ms:

(3000 x 100) / 8 = 37500 To make it a multiple of MSS divide by 1460:

37500 / 1460 = 25.68 Then round up to the nearest even whole number:

26 x 1460 = 37960 - my RWIN

If you would like an easy way to find your optimum settings in CableNut try the "CableNut Live" webpage. (A BIG thanks to our member here j79zlr for this)

from your post

His caps are 512 kilobits download, I gave him a value based on his caps and a latency of about 300ms which should be as high as ever gets. TTL is irrelevant to anything

mnosteele52 · Post by **mnosteele52** » Sat Jul 26, 2003 10:39 am

Pino you aren't making ANY sense? What is it you don't understand or are trying to prove?

pino · Post by **pino** » Sat Jul 26, 2003 11:06 am

only want to know how to read the result from tcp/ip analyzer
because with rwin 65000 get limit rcvwindow more bigger than if with rwin 17500 , but with rwin 17500 look better for dl speed

that's all

mnosteele52 · Post by **mnosteele52** » Sat Jul 26, 2003 4:41 pm

As I stated before, all the analyzer does is tell you your current TCP/IP registry values, that is all. When it says that your RWIN is limited to theat means that IF your latency is 200ms then your current RWIN would limit your bandwidth to what it says. You have to know what your max latency is in order to know what RWIN value is best for you. I think you are reading too much into what the analyzer says.