Recently upgraded my connection from 2meg to 4meg with Nildram, I used to ping about 15-25 on a uk counter-strike server but for some reason with the upgrade my ping has increased to around 45-50 witch seems odd, Possibly becouse interleaving has been turned on? who knows!
These are my analyzer results:
TCP options string = 0204059e0103030201010402
MTU = 1478
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 = 1438
Maximum useful data in each packet = 1438, which equals MSS.
Default TCP Receive Window (RWIN) = 256960
RWIN Scaling (RFC1323) = 2 bits (scale factor: 2^2=4)
Unscaled TCP Receive Window = 64240
For optimum performance, consider changing RWIN to a multiple of MSS.
Other RWIN values that might work well with your current MTU/MSS:
63272 (up to 2 Mbit lines, depending on latency. MSS * 44)
126544 (1-5 Mbit lines, depending on latency. MSS * 44 * 2)
253088 (2-14 Mbit lines, depending on latency. MSS * 44 * 2^2)
506176 (8-30 Mbit lines, depending on latency. MSS * 44 * 2^3)
1012352 (25-60 Mbit lines depending on latency. MSS * 44 * 2^4)
bandwidth * delay product (Note this is not a speed test):
Your TCP Window limits you to: 10278 kbps (1285 KBytes/s) @ 200ms
Your TCP Window limits you to: 4111 kbps (514 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 45 hops
TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349) = 00000000 (0)
I was thinking maybe the right settings with TCP Optimizer could help
Thank you!
Help me please!
- Rollingstone
- Senior Member
- Posts: 3161
- Joined: Wed Jan 23, 2008 5:50 am
- Location: HoChiMinh, Vietnam
Try the following with TCP Optimizer:
General Settings tab:
Custom settings - check
Modify All Network Adapters - check
network adapter selection - your NIC
MTU - 1500
TTL - 64
Windows Scaling - uncheck
TCP Receive Window - leave blank
MTU Discovery - Yes
Black Hole Detect - No
Selective Acks - Yes
Max Duplicate ACKs - 2
TCP 1323 Options:
Timestamps - uncheck
Advanced Settings tab:
Max Connections per Server - 10
Max Connections per 1.0 Server - 10
LocalPriority - 5
Host Priority - 6
DNSPriority - 7
NetbtPriority - 8
Lan Browsing speedup - optimized
QoS: NonBestEffortLimit - 0
ToS: DisableUserTOSSetting - 0
ToS: DefaultTOSValue - 80
MaxNegativeCacheTtl - 0
NetFailureCacheTime - 0
NegativeSOACache Time - 0
LAN Request Buffer Size - 32768
Apply changes then reboot ! After reboot, post your new TCP Analyzer Report.
General Settings tab:
Custom settings - check
Modify All Network Adapters - check
network adapter selection - your NIC
MTU - 1500
TTL - 64
Windows Scaling - uncheck
TCP Receive Window - leave blank
MTU Discovery - Yes
Black Hole Detect - No
Selective Acks - Yes
Max Duplicate ACKs - 2
TCP 1323 Options:
Timestamps - uncheck
Advanced Settings tab:
Max Connections per Server - 10
Max Connections per 1.0 Server - 10
LocalPriority - 5
Host Priority - 6
DNSPriority - 7
NetbtPriority - 8
Lan Browsing speedup - optimized
QoS: NonBestEffortLimit - 0
ToS: DisableUserTOSSetting - 0
ToS: DefaultTOSValue - 80
MaxNegativeCacheTtl - 0
NetFailureCacheTime - 0
NegativeSOACache Time - 0
LAN Request Buffer Size - 32768
Apply changes then reboot ! After reboot, post your new TCP Analyzer Report.
What makes you: "...waking up in the morning so excited about & wanna FLY out of the door ?"
TCP options string = 0204059e0103030e01010402
MTU = 1478
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 = 1438
Maximum useful data in each packet = 1438, which equals MSS.
Default TCP Receive Window (RWIN) = 1073725440
RWIN Scaling (RFC1323) = 14 bits (scale factor: 2^14=16384)
Unscaled TCP Receive Window = 65535
RWIN seems to be an excessively large number. If you're on a line lower than 20 Mbps (that is not satellite), consider using a smaller value.
For optimum performance, consider changing RWIN to a multiple of MSS.
Other RWIN values that might work well with your current MTU/MSS:
63272 (up to 2 Mbit lines, depending on latency. MSS * 44)
126544 (1-5 Mbit lines, depending on latency. MSS * 44 * 2)
253088 (2-14 Mbit lines, depending on latency. MSS * 44 * 2^2)
506176 (8-30 Mbit lines, depending on latency. MSS * 44 * 2^3)
1012352 (25-60 Mbit lines depending on latency. MSS * 44 * 2^4)
bandwidth * delay product (Note this is not a speed test):
Your TCP Window limits you to: 42949018 kbps (5368627 KBytes/s) @ 200ms
Your TCP Window limits you to: 17179607 kbps (2147451 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 46 hops
TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349) = 00000000 (0)
MTU = 1478
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 = 1438
Maximum useful data in each packet = 1438, which equals MSS.
Default TCP Receive Window (RWIN) = 1073725440
RWIN Scaling (RFC1323) = 14 bits (scale factor: 2^14=16384)
Unscaled TCP Receive Window = 65535
RWIN seems to be an excessively large number. If you're on a line lower than 20 Mbps (that is not satellite), consider using a smaller value.
For optimum performance, consider changing RWIN to a multiple of MSS.
Other RWIN values that might work well with your current MTU/MSS:
63272 (up to 2 Mbit lines, depending on latency. MSS * 44)
126544 (1-5 Mbit lines, depending on latency. MSS * 44 * 2)
253088 (2-14 Mbit lines, depending on latency. MSS * 44 * 2^2)
506176 (8-30 Mbit lines, depending on latency. MSS * 44 * 2^3)
1012352 (25-60 Mbit lines depending on latency. MSS * 44 * 2^4)
bandwidth * delay product (Note this is not a speed test):
Your TCP Window limits you to: 42949018 kbps (5368627 KBytes/s) @ 200ms
Your TCP Window limits you to: 17179607 kbps (2147451 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 46 hops
TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349) = 00000000 (0)
- Rollingstone
- Senior Member
- Posts: 3161
- Joined: Wed Jan 23, 2008 5:50 am
- Location: HoChiMinh, Vietnam
Try the following with TCP Optimizer:
General Settings tab:
Custom settings - check
Modify All Network Adapters - check
network adapter selection - your NIC
MTU - 1478
TTL - 64
Windows Scaling - uncheck
TCP Receive Window - 63272
MTU Discovery - Yes
Black Hole Detect - No
Selective Acks - Yes
Max Duplicate ACKs - 2
TCP 1323 Options:
Timestamps - uncheck
Advanced Settings tab:
Max Connections per Server - 10
Max Connections per 1.0 Server - 10
LocalPriority - 5
Host Priority - 6
DNSPriority - 7
NetbtPriority - 8
Lan Browsing speedup - optimized
QoS: NonBestEffortLimit - 0
ToS: DisableUserTOSSetting - 0
ToS: DefaultTOSValue - 80
MaxNegativeCacheTtl - 0
NetFailureCacheTime - 0
NegativeSOACache Time - 0
LAN Request Buffer Size - 32768
General Settings tab:
Custom settings - check
Modify All Network Adapters - check
network adapter selection - your NIC
MTU - 1478
TTL - 64
Windows Scaling - uncheck
TCP Receive Window - 63272
MTU Discovery - Yes
Black Hole Detect - No
Selective Acks - Yes
Max Duplicate ACKs - 2
TCP 1323 Options:
Timestamps - uncheck
Advanced Settings tab:
Max Connections per Server - 10
Max Connections per 1.0 Server - 10
LocalPriority - 5
Host Priority - 6
DNSPriority - 7
NetbtPriority - 8
Lan Browsing speedup - optimized
QoS: NonBestEffortLimit - 0
ToS: DisableUserTOSSetting - 0
ToS: DefaultTOSValue - 80
MaxNegativeCacheTtl - 0
NetFailureCacheTime - 0
NegativeSOACache Time - 0
LAN Request Buffer Size - 32768
What makes you: "...waking up in the morning so excited about & wanna FLY out of the door ?"
TCP options string = 0204059e0103030001010402
MTU = 1478
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 = 1438
Maximum useful data in each packet = 1438, which equals MSS.
Default TCP Receive Window (RWIN) = 63272
RWIN Scaling (RFC1323) = 0 bits
Unscaled TCP Receive Window = 63272
RWIN is a multiple of MSS
Other RWIN values that might work well with your current MTU/MSS:
63272 (up to 2 Mbit lines, depending on latency. MSS * 44) <-- current value
126544 (1-5 Mbit lines, depending on latency. MSS * 44 * 2)
253088 (2-14 Mbit lines, depending on latency. MSS * 44 * 2^2)
506176 (8-30 Mbit lines, depending on latency. MSS * 44 * 2^3)
1012352 (25-60 Mbit lines depending on latency. MSS * 44 * 2^4)
bandwidth * delay product (Note this is not a speed test):
Your TCP Window limits you to: 2531 kbps (316 KBytes/s) @ 200ms
Your TCP Window limits you to: 1012 kbps (127 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 47 hops
TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349) = 00000000 (0)
MTU = 1478
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 = 1438
Maximum useful data in each packet = 1438, which equals MSS.
Default TCP Receive Window (RWIN) = 63272
RWIN Scaling (RFC1323) = 0 bits
Unscaled TCP Receive Window = 63272
RWIN is a multiple of MSS
Other RWIN values that might work well with your current MTU/MSS:
63272 (up to 2 Mbit lines, depending on latency. MSS * 44) <-- current value
126544 (1-5 Mbit lines, depending on latency. MSS * 44 * 2)
253088 (2-14 Mbit lines, depending on latency. MSS * 44 * 2^2)
506176 (8-30 Mbit lines, depending on latency. MSS * 44 * 2^3)
1012352 (25-60 Mbit lines depending on latency. MSS * 44 * 2^4)
bandwidth * delay product (Note this is not a speed test):
Your TCP Window limits you to: 2531 kbps (316 KBytes/s) @ 200ms
Your TCP Window limits you to: 1012 kbps (127 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 47 hops
TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349) = 00000000 (0)
- Rollingstone
- Senior Member
- Posts: 3161
- Joined: Wed Jan 23, 2008 5:50 am
- Location: HoChiMinh, Vietnam