What settings?.

[gum digger]

Hi
Currently use WinXP Pro SP2.
Connected using D-Link 504G. V2

These are the TCP/IP Analyser results:-

TCP options string = 020405840103030201010402
 
MTU = 1452
MTU is not fully optimized for broadband. Consider increasing your MTU to 1500 for better throughput. If you are using a router, it could be limiting your MTU regardless of Registry settings.
 
MSS = 1412
MSS is not optimized for broadband. Consider increasing your MTU value.
 
Default TCP Receive Window (RWIN) = 256984 
RWIN Scaling (RFC1323) = 2 bits (scale factor of 4)
Unscaled TCP Receive Window = 64246 

RWIN is a multiple of MSS
Other RWIN values that might work well with your current MTU/MSS: 
519616 (MSS x 46 * scale factor of 8)
259808 (MSS x 46 * scale factor of 4)
129904 (MSS x 46 * scale factor of 2)
 64952 (MSS x 46)
 
bandwidth * delay product (Note this is not a speed test):

Your TCP Window limits you to: 10279.36 kbps (1284.92 KBytes/s) @ 200ms
Your TCP Window limits you to: 4111.744 kbps (513.968 KBytes/s) @ 500ms
 
MTU Discovery (RFC1191) = ON
 
Time to live left = 50 hops
TTL value is ok.
 
Timestamps (RFC1323) = OFF 
Selective Acknowledgements (RFC2018) = ON
 
IP type of service field (RFC1349) = 00000000 (0)

What should i put into TCPOptimizer So i get fast P2P, Web surfing, Online Videos etc.

Also iam finding it hard to decide which is my network adapter.

1] Intel PRO/1000 PL Network Connection --IP address 10.1.1.2
2] Intel PRO/1000 PM Network Connection --IP address 192.168.1.48

[trogers]

Which country are you in? What speed did you pay your ISP to give you?

[gum digger]

Which country are you in? What speed did you pay your ISP to give you?

I live in New Zealand. Here there are copper wires used for broadband and the speed i pay for is 7.6MBPs. which i never get.

[trogers]

Try the speedtest of our website. Choose the test server in New Zealand:

http://www.speedguide.net/speedtest/

[gum digger]

http://www.speedguide.net/speedtest/...st=S2S96XBGL61

[trogers]

Do this nitro test and post the results under the 'Statistics' button:

http://nitro.ucsc.edu/

[gum digger]

Hi
I have carried out these tests during night when only few people are using there net.

I have done it 4 times to be more accurate.

TCP/Web100 Network Diagnostic Tool v5.4.11
click START to begin
Connected to: nitro.ucsc.edu -- Using IPv4 address
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 133.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 684.61kb/s
Your PC is connected to a Cable/DSL modem
[S2C]: Excessive packet queuing detected

click START to re-test
Connected to: nitro.ucsc.edu -- Using IPv4 address
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 127.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 1.18Mb/s
Your PC is connected to a Cable/DSL modem
[S2C]: Excessive packet queuing detected

click START to re-test
Connected to: nitro.ucsc.edu -- Using IPv4 address
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 132.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 1.44Mb/s
Your PC is connected to a Cable/DSL modem
[S2C]: Excessive packet queuing detected

click START to re-test
Connected to: nitro.ucsc.edu -- Using IPv4 address
Another client is currently being served, your test will begin within 45 seconds
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 133.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 1.37Mb/s
Your PC is connected to a Cable/DSL modem
[S2C]: Excessive packet queuing detected

click START to re-test

[trogers]

No. What you have posted are the Summary reports. I need the report under the 'Staistics' button that shows your round trip time and the quality of your connection.

After the nitro test has been completed, click the 'Statistics' button and the report will pop-up.

[gum digger]

WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 95.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 634.23kb/s

------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_06

------ 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 = 1176.92 msec; the Packet size = 1412 Bytes; and
No packet loss - but packets arrived out-of-order 0.76% of the time
C2S throughput test: Excessive packet queuing detected: 10.99%
S2C throughput test: Excessive packet queuing detected: 20.62%
This connection is receiver limited 18.99% of the time.
This connection is network limited 80.84% 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: ON

Server 'nitro.ucsc.edu' is not behind a firewall. [Connection to the ephemeral port was successful]
Client is probably behind a firewall. [Connection to the ephemeral port failed]
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 [125.236.167.111] but Client says [10.1.1.2]

[trogers]

Web100 reports the Round trip time = 1176.92 msec; the Packet size = 1412 Bytes; and
No packet loss - but packets arrived out-of-order 0.76% of the time
C2S throughput test: Excessive packet queuing detected: 10.99%
S2C throughput test: Excessive packet queuing detected: 20.62%
This connection is receiver limited 18.99% of the time.
This connection is network limited 80.84% of the time.

Your round trip time (latency) is very high at 1177ms. Normal range from NZ to the US should be 280-350ms

Power off your router and connect your comp directly to the modem, reboot and do the nitro test again to see if this round trip time can fall to normal values.

[gum digger]

I have a peak & offpeak situation here in NZ.
SO iam posting results of during the peak hours.

WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 132.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 2.64Mb/s

------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_06

------ 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 = 587.18 msec; the Packet size = 1412 Bytes; and
No packet loss - but packets arrived out-of-order 0.16% of the time
C2S throughput test: Packet queuing detected: 4.73%
S2C throughput test: Packet queuing detected: 7.20%
This connection is receiver limited 69.8% of the time.
This connection is network limited 30.03% 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: ON

Server 'nitro.ucsc.edu' is not behind a firewall. [Connection to the ephemeral port was successful]
Client is probably behind a firewall. [Connection to the ephemeral port failed]
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 [125.236.166.91] but Client says [10.1.1.2]



I will post offpeak results 2nite.

[trogers]

Do a speedtest here as well during peak and offpeak times. Choose the test server in Auckland and note your latency values. We can then compare your local latency and those to the US:

http://www.speedtest.net/

[gum digger]

These are 2 tests done during peak hours from auckland server

[trogers]

Try these settings to first increase your MTU value:

General Settings tab:
Custom settings - check
Modify All Network Adapters - check
network adapter selection - your NIC
MTU - 1500
TTL - 64
TCP Receive Window - leave blank
MTU Discovery - Yes
Black Hole Detect - No
Selective Acks - Yes
Max Duplicate ACKs - 2
TCP 1323 Options:
Windows Scaling - uncheck
Timestamps - uncheck
Advanced Settings tab:
Max Connections per Server - 10
Max Connections per 1.0 Server - 20
LocalPriority - 5
Host Priority - 6
DNSPriority - 7
NetbtPriority - 8
Lan Browsing speedup - optimized
QoS: NonBestEffortLimit - 0
ToS: DisableUserTOSSetting - 0
ToS: DefaultTOSValue - 136
MaxNegativeCacheTtl - 0
NetFailureCacheTime - 0
NegativeSOACache Time - 0
LAN Request Buffer Size - 32768
Then select "Apply Changes" and reboot to take effect

[trogers]

I live in New Zealand. Here there are copper wires used for broadband and the speed i pay for is 7.6MBPs. which i never get.

You will also need to know how far you are located from the central office(CO) of your ISP. You can give them a call to find out.

After a distance of 1.5km, the distance will affect speed inversely, with zero speed at about 6 km from the CO.

[gum digger]

this is During off peak


iam roughly 2-3km away from the exchange.

[trogers]

Do the TCP Analyzer again and post. Let's see if your MTU has increased. Also do the nitro test to check your round trip time for off peak time.

[gum digger]

Do the TCP Analyzer again and post. Let's see if your MTU has increased. Also do the nitro test to check your round trip time for off peak time.

« SpeedGuide.net TCP Analyzer Results »
Tested on: 11.25.2006 08:18
Partial IP: 125.236.xxx.xx

TCP options string: 020405840103030e01010402
MSS: 1412
MTU: 1452
TCP Window: 1073725440 (NOT multiple of MSS)
RWIN Scaling: 14
Unscaled RWIN : 65535
Reccomended RWINs: 64952, 129904, 259808, 519616
BDP limit (200ms): 42949018kbps (5368627KBytes/s)
BDP limit (500ms): 17179607kbps (2147451KBytes/s)
MTU Discovery: ON
TTL: 50
Timestamps: OFF
SACKs: ON
IP ToS: 00000000 (0)

======================================================




WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 127.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 3.39Mb/s

------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_06

------ 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 = 1138.12 msec; the Packet size = 1412 Bytes; and
There were 30 packets retransmitted, 139 duplicate acks received, and 148 SACK blocks received
The connection was idle 0 seconds (0%) of the time
C2S throughput test: Packet queuing detected: 4.26%
S2C throughput test: Excessive packet queuing detected: 16.35%
This connection is network limited 99.83% 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: ON

Server 'nitro.ucsc.edu' is not behind a firewall. [Connection to the ephemeral port was successful]
Client is probably behind a firewall. [Connection to the ephemeral port failed]
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 [125.236.166.71] but Client says [10.1.1.2]

[trogers]

Web100 reports the Round trip time = 1138.12 msec; the Packet size = 1412 Bytes; and
There were 30 packets retransmitted, 139 duplicate acks received, and 148 SACK blocks received
The connection was idle 0 seconds (0%) of the time
C2S throughput test: Packet queuing detected: 4.26%
S2C throughput test: Excessive packet queuing detected: 16.35%
This connection is network limited 99.83% of the time.

Your previous peak hour round trip time was 587ms. This test shows value almost double that. Your MTU is set at 1452, perhaps being fixed by your ISP.

Try these settings with TCP Optimizer:

General Settings tab:
Custom settings - check
Modify All Network Adapters - check
network adapter selection - your NIC
MTU - 1452
TTL - 64
TCP Receive Window - 519616
MTU Discovery - Yes
Black Hole Detect - No
Selective Acks - Yes
Max Duplicate ACKs - 2
TCP 1323 Options:
Windows Scaling - checked
Timestamps - uncheck
Advanced Settings tab:
Max Connections per Server - 10
Max Connections per 1.0 Server - 20
LocalPriority - 5
Host Priority - 6
DNSPriority - 7
NetbtPriority - 8
Lan Browsing speedup - optimized
QoS: NonBestEffortLimit - 0
ToS: DisableUserTOSSetting - 0
ToS: DefaultTOSValue - 136
MaxNegativeCacheTtl - 0
NetFailureCacheTime - 0
NegativeSOACache Time - 0
LAN Request Buffer Size - 32768
Then select "Apply Changes" and reboot to take effect

[gum digger]

Applied the settings. Any further tweaks i shuld try?. i do alot of p2p