PDA

View Full Version : n00b help please


Dakotakid44
09-25-06, 10:29 AM
I just need a little help tweaking my cable modem. I'm running Windows XP.
These are the results I got from the TCP/IP analyzer:
TCP options string = 020405ac0103030101010402
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 your MTU value.
Default TCP Receive Window (RWIN) = 129228
RWIN Scaling (RFC1323) = 1 bits (scale factor of 2)
Unscaled TCP Receive Window = 64614

RWIN is a multiple of MSS
Other RWIN values 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 (Note this is not a speed test):

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


I hope this is enough info. If not let me know. Thanks

trogers
09-25-06, 10:33 AM
Is your ISP giving you ADSL or Cable? What is your subscribed speed? Which country are you in?

Dakotakid44
09-25-06, 10:41 AM
its cable, i think it's 3-5 mb/sec., USA

trogers
09-25-06, 10:50 AM
Do the test in this link and post your results under the Statistics' button:

http://nitro.ucsc.edu/

Dakotakid44
09-25-06, 10:54 AM
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client to server) . . . . . 247.50Kb/s
running 10s inbound test (server to client) . . . . . . 764.88kb/s
Your PC is connected to a Cable/DSL modem
Information: Other network traffic is congesting the link

click START to re-test

trogers
09-25-06, 11:00 AM
This is just the Summary. After finishing the test, click the 'Statistics' button and a report will pop up. Copy and post the report.

Dakotakid44
09-25-06, 11:11 AM
WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client to server) . . . . . 218.38Kb/s
running 10s inbound test (server to client) . . . . . . 751.37kb/s

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

------ 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 = 98.46 msec; the Packet size = 1452 Bytes; and
There were 25 packets retransmitted, 128 duplicate acks received, and 146 SACK blocks received
The connection was idle 0 seconds (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: ON
Information: Network Middlebox is modifying MSS variable
Server IP addresses are preserved End-to-End
Client IP addresses are preserved End-to-End

trogers
09-25-06, 11:19 AM
Use the TCP Optimizer with these custom settings and then do the TCP Analyzer again and post:

General Settings tab:
Custom settings - check
Modify All Network Adapters - check
network adapter selection - your NIC
MTU - 1500
TTL - 64
TCP Receive Window - leave this 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 - 80
MaxNegativeCacheTtl - 0
NetFailureCacheTime - 0
NegativeSOACache Time - 0
LAN Request Buffer Size - 32768
Then select "Apply Changes" and reboot to take effect

Dakotakid44
09-25-06, 11:23 AM
thank you very much trogers

trogers
09-25-06, 11:26 AM
Your comp has not yet been optimized. What I am trying to do is to see if your MTU can be made to 1500 for Cable.

Use the custom setting, reboot comp, do the TCP Analyzer and post the results.

Dakotakid44
09-25-06, 11:37 AM
after optimizing:


WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client to server) . . . . . 246.71Kb/s
running 10s inbound test (server to client) . . . . . . 844.88kb/s

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

------ 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 = 95.8 msec; the Packet size = 1460 Bytes; and
There were 17 packets retransmitted, 82 duplicate acks received, and 93 SACK blocks received
The connection was idle 0 seconds (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: ON
Packet size is preserved End-to-End
Server IP addresses are preserved End-to-End
Client IP addresses are preserved End-to-End

trogers
09-25-06, 11:40 AM
Use the TCP Optimizer with these custom settings for optimizing:

General Settings tab:
Custom settings - check
Modify All Network Adapters - check
network adapter selection - your NIC
MTU - 1500
TTL - 64
TCP Receive Window - 128480
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 - 80
MaxNegativeCacheTtl - 0
NetFailureCacheTime - 0
NegativeSOACache Time - 0
LAN Request Buffer Size - 32768
Then select "Apply Changes" and reboot to take effect

Make sure your modem is not placed near to any electrical device, eg. speakers, cordless phone, router, etc.

Dakotakid44
09-25-06, 11:42 AM
i have to go. i'll be back later. thanks.

Dakotakid44
09-25-06, 04:29 PM
after new optimizing:


WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client to server) . . . . . 248.24Kb/s
running 10s inbound test (server to client) . . . . . . 2.63Mb/s

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

------ Web100 Detailed Analysis ------
Cable modem/DSL/T1 link found.
Link set to Half Duplex mode
No network congestion discovered.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 102.34 msec; the Packet size = 1460 Bytes; and
There were 13 packets retransmitted, 231 duplicate acks received, and 240 SACK blocks received
The connection was idle 0 seconds (0%) of the time
This connection is receiver limited 8.52% of the time.
This connection is network limited 91.45% 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
Packet size is preserved End-to-End
Server IP addresses are preserved End-to-End
Client IP addresses are preserved End-to-End

.thanks again

trogers
09-25-06, 04:40 PM
------ Web100 Detailed Analysis ------
Cable modem/DSL/T1 link found.
Link set to Half Duplex mode
No network congestion discovered.
Good network cable(s) found
Normal duplex operation found.



I think your NIC is either faulty or has a wrong setting. Your first 2 network tests showed Link set to Full Duplex but this last test shows Link set to Half Duplex.

Go to Control Panel=>System=>Hardware=>Device Manager

Click right on Network Adapter and select 'Properties'

In the pop up menu, check your setting for 'Speed & Duplex'

Setting should either be autosensing or 10 mbps full duplex.

Dakotakid44
09-25-06, 05:33 PM
it says "autodetect"

trogers
09-25-06, 10:19 PM
Download this test file and check your file transfer speed after 50% has been downloaded:

ftp://ftp1.optonline.net/pub/test64

Dakotakid44
09-26-06, 11:08 AM
it was about 975 KB/sec.