Simply put, they suck. I previously had a 1.5MB service, and despite trying to follow mnosteele's tips for setting RWIN and TcpWindowSize settings am unable to get better than a 120KB/sec download speed, and even that's gone when I go back an hour or so later. Some tips I have implemented are:
ProtocolMTU=1480 (seems to work better than 1454)
Irq18buffer=7168
In addition I included my Analyzer results and my CableNut settings at the bottom of this thread (along with a link to my previous post):
My MTU is stuck at 1454...the NTT service I'm using doesn't go above that. In addition to changing the ProtocolMTU, are there other registry changes I need to make to match this setting? Also, if it's a help, the ping link in mnosteele's tips gives me a 200ms avg latency, while pinging my ISP gives my a 69ms average (TTL=253). Finally, the settings for my NetGear FA311 NIC are as follow, and wonder if they also need to be changed:
Network(MAC)Address: Not Present
Network Media: AutoSense
ReceiveBufferCount=40
I know this is a long post, but I'm at my wit's end to get speeds somewhat comparable to my 8MB service. I'm installing a high-speed internet cable tomorrow which I hope helps, but looking for any other suggestions to optimize this connection.
Thanks much in advance,
torataka
SpeedGuide.net TCP/IP Analyzer
TCP properties for IP = XXX.XXX.XXX.XXX (hcn-acs1.hi-net.ne.jp)
Browser/OS = Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Note: Read the FAQ if the above is not your IP address.
TCP options string = 0204058601010402
MTU = 1454
MTU is not fully optimized for broadband. Consider increasing your MTU to 1500 for better throughput.
MSS = 1414
Maximum useful data in each packet = 1414, which equals MSS.
MSS is not fully optimized for broadband (although it might work well for slower connections). Consider increasing your MTU value.
Default Receive Window (RWIN) = 65535 (actually a 520352 setting in CableNut)
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:
520352 (MSS x 46 * scale factor of 8)
260176 (MSS x 46 * scale factor of 4)
130088 (MSS x 46 * scale factor of 2)
65044 (MSS x 46)
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 = 48 hops
TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349)= 01011100
Precedence (priority) = 010 (immediate)
Delay = 1 (low delay)
Throughput = 1 (high throughput)
Reliability = 1 (high reliability)
Cost = 0 (normal cost)
DefaultReceiveWindow = 1024000
DefaultSendWindow = 16384
DisableAddressSharing = 1
InitialLargeBufferCount = 100
InitialMediumBufferCount = 240
InitialSmallBufferCount = 320
LargeBufferSize = 81920
MaxFastTransmit = 64000
MediumBufferSize = 15040
PriorityBoost = 0
SmallBufferSize = 1280
TransmitWorker = 32
FastSendDatagramThreshold = 4096
EnableFastRouteLookup = 1
EnablePMTUDiscovery = 1
IgnorePushBitsOnReceive = 0
GlobalMaxTcpWindowSize = 520352
MaxFreeTcbs = 8000
MaxHashTableSize = 16384
MaxNormLookupMemory = 5000000
SackOpts = 1
SynAttackProtect = 1
Tcp1323Opts = 0
TcpLogLevel = 1
TcpMaxDupAcks = 2
TcpMaxHalfOpen = 100
TcpMaxHalfRetried = 80
TcpRecvSegmentSize = 1414
TcpSendSegmentSize = 1414
TcpTimedWaitDelay = 30
TcpUseRFC1122UrgentPointer = 0
TcpWindowSize = 520352
MaxConnectionsPer1_0Server = 20
MaxConnectionsPerServer = 10
DefaultTTL = 64
DisableUserTOSSetting = 0
TcpMaxDataRetransmissions = 6
DefaultTOSValue = 92
http://forums.speedguide.net/showthread ... t=torataka
Please Help - Frustrating 8MB DSL Speeds
your data from yours posts: in italic
NetGear FA311 NIC
Network Media: AutoSense >> depends on your ISP in asdl check on your modem
ReceiveBufferCount=40 >> set to max
Irq18buffer=7168 >> so you have NIC on 18irq
Japan and use NTT's Flet ADSL service,
which seems to be limited to a 1454 MTU and 1414 MSS from all my research.
Other than that, I'm on WINXP using the built-in PPPoE connection software.
rwin 520352 >> =368*1414
check in RWIN Calculator http://www.dslnuts.com/bitsbytes.shtml
Tcp1323Opts = 0 >> but with RWIN > 65535 must be changed to =1
DefaultReceiveWindow = 1024000 >> (=1024*1000)~8000kbps dwl
DefaultSendWindow = 16384 >> (=1024*16)~128kbps upl
so yours MODYFICATIONS of
mnosteele's CableNut settings
is for CAPS 8000kbps/128kbps (exactly!!)
is it your CAPS correct?? upl is relatively v.v.v.low???
MaxConnectionsPer1_0Server = 20 >> can be =40
MaxConnectionsPerServer = 10 >> can be =40
pinging my ISP gives my a 69ms average (TTL=253)
BTW explained above ping to ISP (CPO??) is relatively hight
important is NOT pings to your ISP
but aver. maxPING to TARGET, other servers eg speed tests, www
for calculation of RWIN
summary
corect yours to Tcp1323Opts = 1
actualy rest of setings are less important without SpeedTests and TweakTests
as "training of sweaming without water"
return AFTER INSTALATION of new service
with results & exact information of yours:
hdw
& new: CAPS, MTU, PINGS
PSsee also mnosteele's
Download Cablenut and try the following settings
for CAPS 10Mbps/1Mbps
http://forums.speedguide.net/showthread ... post831590
NetGear FA311 NIC
Network Media: AutoSense >> depends on your ISP in asdl check on your modem
ReceiveBufferCount=40 >> set to max
Irq18buffer=7168 >> so you have NIC on 18irq
Japan and use NTT's Flet ADSL service,
which seems to be limited to a 1454 MTU and 1414 MSS from all my research.
Other than that, I'm on WINXP using the built-in PPPoE connection software.
rwin 520352 >> =368*1414
check in RWIN Calculator http://www.dslnuts.com/bitsbytes.shtml
Tcp1323Opts = 0 >> but with RWIN > 65535 must be changed to =1
DefaultReceiveWindow = 1024000 >> (=1024*1000)~8000kbps dwl
DefaultSendWindow = 16384 >> (=1024*16)~128kbps upl
so yours MODYFICATIONS of
mnosteele's CableNut settings
is for CAPS 8000kbps/128kbps (exactly!!)
is it your CAPS correct?? upl is relatively v.v.v.low???
MaxConnectionsPer1_0Server = 20 >> can be =40
MaxConnectionsPerServer = 10 >> can be =40
pinging my ISP gives my a 69ms average (TTL=253)
BTW explained above ping to ISP (CPO??) is relatively hight
important is NOT pings to your ISP
but aver. maxPING to TARGET, other servers eg speed tests, www
for calculation of RWIN
summary
corect yours to Tcp1323Opts = 1
actualy rest of setings are less important without SpeedTests and TweakTests
as "training of sweaming without water"
return AFTER INSTALATION of new service
with results & exact information of yours:
hdw
& new: CAPS, MTU, PINGS
PSsee also mnosteele's
Download Cablenut and try the following settings
for CAPS 10Mbps/1Mbps
http://forums.speedguide.net/showthread ... post831590
Thanks for the reply, Andrzej. I tried the settings in the post you suggested, and the only thing I have different is a DefaultReceiveWindow of 1024000, DefaultSendWindow of 256000, and you can see my current RWIN below. I've tried literally dozens of settings other than this today, and no joy. I would most gratefully appreciate any further help anyone has to offer.
On my knees,
torataka
Sun Oct 20 18:37:56 2002.
SpeedGuide.net TCP/IP Analyzer
TCP properties for IP = xxx.xxx.xxx.xxx (hcn-acs1.hi-net.ne.jp)
Browser/OS = Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Note: Read the FAQ if the above is not your IP address.
TCP options string = 02040586010303030101080a000000000000000001010402
MTU = 1454
MTU is not fully optimized for broadband. Consider increasing your MTU to 1500 for better throughput.
MSS = 1414
Maximum useful data in each packet = 1414, which equals MSS.
MSS is not fully optimized for broadband (although it might work well for slower connections). Consider increasing your MTU value.
Default Receive Window (RWIN) = 520352
RWIN Scaling (RFC1323) = 3 bits
Unscaled Receive Window = 65044
RWIN is a multiple of MSS
Other values for RWIN that might work well with your current MTU/MSS:
260176 (MSS x 46 * scale factor of 4)
130088 (MSS x 46 * scale factor of 2)
65044 (MSS x 46)
bandwidth * delay product:
Your RcvWindow limits you to: 20814.08 kbps (2601.76 KBytes/s) @ 200ms
Your RcvWindow limits you to: 8325.632 kbps (1040.704 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 112 hops
TTL value is ok.
Timestamps (RFC1323) = ON
Note: Timestamps add 12 bytes to the TCP header of each packet, reducing the space available for useful data.
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349)= 01011100
Precedence (priority) = 010 (immediate)
Delay = 1 (low delay)
Throughput = 1 (high throughput)
Reliability = 1 (high reliability)
Cost = 0 (normal cost)
4391575 connections tested since 03.10.2001.
Analyzer version: 1.02 - updated 09.20.2002.
On my knees,
torataka
Sun Oct 20 18:37:56 2002.
SpeedGuide.net TCP/IP Analyzer
TCP properties for IP = xxx.xxx.xxx.xxx (hcn-acs1.hi-net.ne.jp)
Browser/OS = Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Note: Read the FAQ if the above is not your IP address.
TCP options string = 02040586010303030101080a000000000000000001010402
MTU = 1454
MTU is not fully optimized for broadband. Consider increasing your MTU to 1500 for better throughput.
MSS = 1414
Maximum useful data in each packet = 1414, which equals MSS.
MSS is not fully optimized for broadband (although it might work well for slower connections). Consider increasing your MTU value.
Default Receive Window (RWIN) = 520352
RWIN Scaling (RFC1323) = 3 bits
Unscaled Receive Window = 65044
RWIN is a multiple of MSS
Other values for RWIN that might work well with your current MTU/MSS:
260176 (MSS x 46 * scale factor of 4)
130088 (MSS x 46 * scale factor of 2)
65044 (MSS x 46)
bandwidth * delay product:
Your RcvWindow limits you to: 20814.08 kbps (2601.76 KBytes/s) @ 200ms
Your RcvWindow limits you to: 8325.632 kbps (1040.704 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 112 hops
TTL value is ok.
Timestamps (RFC1323) = ON
Note: Timestamps add 12 bytes to the TCP header of each packet, reducing the space available for useful data.
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349)= 01011100
Precedence (priority) = 010 (immediate)
Delay = 1 (low delay)
Throughput = 1 (high throughput)
Reliability = 1 (high reliability)
Cost = 0 (normal cost)
4391575 connections tested since 03.10.2001.
Analyzer version: 1.02 - updated 09.20.2002.
Have you got the latest drivers for your NIC?
I ain't got time to bleed
Click here for the TCP/IP Analyzer Test
Please click here for Speedguide.net tweaking advice, programs, tools and links
Join Speedguide's Folding@Home team and save lives!
Click here for the TCP/IP Analyzer Test
Please click here for Speedguide.net tweaking advice, programs, tools and links
Join Speedguide's Folding@Home team and save lives!
Thanks for the reply. Yes, I have to think so, though I'm not 100 percent certain. I'm using WINXP SP1 which recognizes the card, and going to Windows update does not yield a different choice. I also searched the Internet, and couldn't find anything better for WINXP.
Thanks again for the help.
Randy
Thanks again for the help.
Randy
I did not follow your calculations.for me it is not such important
but
you pay for CAPS & have not reach 90% of it...
in the same time
have not check for NIC new driver for free??
if you have actualy CAPS 8M (yes or not)
your setting in NIC will be probably
rather 100Mbps FullDuplex
I ask you again: ASK your ISP
then previous setting auto (or 10 HalfDuplex)
also you did not explain
your actual
TweakTester II result link
BTW
PAY ATTENTIONS
SG TCP/IP Analizer exactly explain:
ONLY how was your internet connection seen by other server
your exact PC settings can be explain only by YOU
hdw= I mean PC: CPU, RAM, HDD (do you have any conflict in wXP?)
CAPS= I mean your payed speed (acctualy not in a future)
PINGS= your ping to your ISP in first post you explain
as 63ms on 1.5Mbps speed - but better is lower eg 7-10ms
PARTICULARY to your ISP server
stange I have 10-11ms even with lower CAPS
if you have big & unstabile pings to eg this FORUM
is probability that you have
problems with your:
a}line
b}wire
c}NIC
d)ISP
and any software can NOT solve the problems
PS that time do you have now
I have 1:50 PM Sunday 20'10'2002
below is link with MY advice
to person who can't reach effects after tweaking
see http://forums.speedguide.net/showthread ... post834284
-
AceFireball
- Posts: 2530
- Joined: Wed Aug 14, 2002 12:00 pm
- Location: Greenville, NC
-
mnosteele52
- Posts: 11913
- Joined: Tue Jul 24, 2001 12:00 pm
- Location: Chesapeake, VA
OK you didn't follow my instructions for configuring your TcpWindowSize, it is way too high for your connection. First you need to get your MTU straight, try the following fix from Bob:
1) Download this file http://www.carricksolutions.com/XP_MTU.reg
2) Right click the file and choose "Merge"
3) Click "Yes"
4) Go to "Start" -> Click on "Run" -> Type in "Regedt32.exe" -> Click "OK"
5) Go to this Reg Key "[HKEY_LOCAL_MACHINE\ SYSTEM\CurrentControlSet\ Services\NdisWan\ Parameters\Protocols\0]"
6) Double click on "Protocol MTU"
7) Click on "Decimal" -> Enter your desired value (I.E.: Anything less then 1480.) Use 1480
8) Click "OK"
9) Done!
If that doesn't work try the one's in my Help & Tips link. Once you get that straight we can work on the rest of your settings, what are your actual caps now?
1) Download this file http://www.carricksolutions.com/XP_MTU.reg
2) Right click the file and choose "Merge"
3) Click "Yes"
4) Go to "Start" -> Click on "Run" -> Type in "Regedt32.exe" -> Click "OK"
5) Go to this Reg Key "[HKEY_LOCAL_MACHINE\ SYSTEM\CurrentControlSet\ Services\NdisWan\ Parameters\Protocols\0]"
6) Double click on "Protocol MTU"
7) Click on "Decimal" -> Enter your desired value (I.E.: Anything less then 1480.) Use 1480
8) Click "OK"
9) Done!
If that doesn't work try the one's in my Help & Tips link. Once you get that straight we can work on the rest of your settings, what are your actual caps now?