can i gain more speed
-
djicemanfrankie
- Member
- Posts: 42
- Joined: Mon Jul 29, 2002 1:26 pm
can i gain more speed
i'm using the newly dsl installed in my house and here is the speed test result
2002-08-02 21:02:25 EST: 315 / 150
Your download speed : 315904 bps, or 315 kbps.
A 38.5 KB/sec transfer rate.
Your upload speed : 150178 bps, or 150 kbps.
my isp is msn.com
tel co. is ameritech
win 2000
TCP options string = 020405aa01010402
MTU = 1490
Unrecognized MTU, or MTU = 0.
MSS = 1450
Maximum useful data in each packet = 1450, which equals MSS.
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:
510400 (MSS x 44 * scale factor of 8)
255200 (MSS x 44 * scale factor of 4)
127600 (MSS x 44 * scale factor of 2)
63800 (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 = 55 hops
TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349)= 00101100
Precedence (priority) = 001 (priority)
Delay = 0 (normal delay)
Throughput = 1 (high throughput)
Reliability = 1 (high reliability)
Cost = 0 (normal cost)
2002-08-02 21:02:25 EST: 315 / 150
Your download speed : 315904 bps, or 315 kbps.
A 38.5 KB/sec transfer rate.
Your upload speed : 150178 bps, or 150 kbps.
my isp is msn.com
tel co. is ameritech
win 2000
TCP options string = 020405aa01010402
MTU = 1490
Unrecognized MTU, or MTU = 0.
MSS = 1450
Maximum useful data in each packet = 1450, which equals MSS.
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:
510400 (MSS x 44 * scale factor of 8)
255200 (MSS x 44 * scale factor of 4)
127600 (MSS x 44 * scale factor of 2)
63800 (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 = 55 hops
TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349)= 00101100
Precedence (priority) = 001 (priority)
Delay = 0 (normal delay)
Throughput = 1 (high throughput)
Reliability = 1 (high reliability)
Cost = 0 (normal cost)
-
djicemanfrankie
- Member
- Posts: 42
- Joined: Mon Jul 29, 2002 1:26 pm
- joecool169
- Posts: 805
- Joined: Fri Nov 16, 2001 10:52 pm
- Location: Ohio
-
djicemanfrankie
- Member
- Posts: 42
- Joined: Mon Jul 29, 2002 1:26 pm
- joecool169
- Posts: 805
- Joined: Fri Nov 16, 2001 10:52 pm
- Location: Ohio
-
djicemanfrankie
- Member
- Posts: 42
- Joined: Mon Jul 29, 2002 1:26 pm
here is the result
TCP options string = 020405aa0103030201010402
MTU = 1490
Unrecognized MTU, or MTU = 0.
MSS = 1450
Maximum useful data in each packet = 1450, which equals MSS.
Default Receive Window (RWIN) = 255552
RWIN Scaling (RFC1323) = 2 bits
Unscaled Receive Window = 63888
For optimum performance, consider changing RWIN to a multiple of MSS.
Other values for RWIN that might work well with your current MTU/MSS:
510400 (MSS x 44 * scale factor of 8)
255200 (MSS x 44 * scale factor of 4)
127600 (MSS x 44 * scale factor of 2)
63800 (MSS x 44)
bandwidth * delay product:
Your RcvWindow limits you to: 10222.08 kbps (1277.76 KBytes/s) @ 200ms
Your RcvWindow limits you to: 4088.832 kbps (511.104 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 55 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)
i won't change to 1492 at all. is there anyway in the registry to change it manually so the analyzer will recognize it
TCP options string = 020405aa0103030201010402
MTU = 1490
Unrecognized MTU, or MTU = 0.
MSS = 1450
Maximum useful data in each packet = 1450, which equals MSS.
Default Receive Window (RWIN) = 255552
RWIN Scaling (RFC1323) = 2 bits
Unscaled Receive Window = 63888
For optimum performance, consider changing RWIN to a multiple of MSS.
Other values for RWIN that might work well with your current MTU/MSS:
510400 (MSS x 44 * scale factor of 8)
255200 (MSS x 44 * scale factor of 4)
127600 (MSS x 44 * scale factor of 2)
63800 (MSS x 44)
bandwidth * delay product:
Your RcvWindow limits you to: 10222.08 kbps (1277.76 KBytes/s) @ 200ms
Your RcvWindow limits you to: 4088.832 kbps (511.104 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 55 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)
i won't change to 1492 at all. is there anyway in the registry to change it manually so the analyzer will recognize it
- joecool169
- Posts: 805
- Joined: Fri Nov 16, 2001 10:52 pm
- Location: Ohio
mnosteele52 suggests some MTU fixes in his help thread here
I would look at that, you need to get your MTU fixed
I would look at that, you need to get your MTU fixed
Joe
-
djicemanfrankie
- Member
- Posts: 42
- Joined: Mon Jul 29, 2002 1:26 pm
- joecool169
- Posts: 805
- Joined: Fri Nov 16, 2001 10:52 pm
- Location: Ohio
-
djicemanfrankie
- Member
- Posts: 42
- Joined: Mon Jul 29, 2002 1:26 pm
after apllying the no. still no change. here is the result tryied the other no. also no change
TCP options string = 020405aa0103030001010402
MTU = 1490
Unrecognized MTU, or MTU = 0.
MSS = 1450
Maximum useful data in each packet = 1450, which equals MSS.
Default Receive Window (RWIN) = 31944
RWIN Scaling (RFC1323) = 0 bits
Unscaled Receive Window = 31944
For optimum performance, consider changing RWIN to a multiple of MSS.
Other values for RWIN that might work well with your current MTU/MSS:
510400 (MSS x 44 * scale factor of 8)
255200 (MSS x 44 * scale factor of 4)
127600 (MSS x 44 * scale factor of 2)
63800 (MSS x 44)
bandwidth * delay product:
Your RcvWindow limits you to: 1277.76 kbps (159.72 KBytes/s) @ 200ms
Your RcvWindow limits you to: 511.104 kbps (63.888 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = OFF
Time to live left = 55 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)
TCP options string = 020405aa0103030001010402
MTU = 1490
Unrecognized MTU, or MTU = 0.
MSS = 1450
Maximum useful data in each packet = 1450, which equals MSS.
Default Receive Window (RWIN) = 31944
RWIN Scaling (RFC1323) = 0 bits
Unscaled Receive Window = 31944
For optimum performance, consider changing RWIN to a multiple of MSS.
Other values for RWIN that might work well with your current MTU/MSS:
510400 (MSS x 44 * scale factor of 8)
255200 (MSS x 44 * scale factor of 4)
127600 (MSS x 44 * scale factor of 2)
63800 (MSS x 44)
bandwidth * delay product:
Your RcvWindow limits you to: 1277.76 kbps (159.72 KBytes/s) @ 200ms
Your RcvWindow limits you to: 511.104 kbps (63.888 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = OFF
Time to live left = 55 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)
- mnosteele52
- Posts: 11913
- Joined: Tue Jul 24, 2001 12:00 pm
- Location: Chesapeake, VA
-
djicemanfrankie
- Member
- Posts: 42
- Joined: Mon Jul 29, 2002 1:26 pm
i'm on msn and my modem is arescom. nic card is 10/100 on ibm netvista( loww profile card) tried to change it still no change on mtu. tried it with optimizer and reboot completely no change. is there anotherway to change this mtu manually so that analyzer reads it correctly. thanks appreciate the help guys.....
- mnosteele52
- Posts: 11913
- Joined: Tue Jul 24, 2001 12:00 pm
- Location: Chesapeake, VA
I'm assuming agentbeast was inquiring if there was a firmware update for your modem (but I'm not sure), you might look here and see if there is. I asked about your NIC because Linksys NICs have a feature called "priority packet" that will lower you MTU when enabled. Also by chance do you using a router? If so maybe you need to update it's firmware. 
-
djicemanfrankie
- Member
- Posts: 42
- Joined: Mon Jul 29, 2002 1:26 pm
Originally posted by djicemanfrankie
i'm not using a router and it's a direct hooked up to the phoneline with dsl filter. tried to use with or with out filters still the same.
model of dsl modem is arescom netdsl 800. check with firmwareupdate no update is available![]()
You're wasting your time trying to change your MTU. It is never going to register with sg analyzer or any other test site. That modem you have actually acts as a NAT router/firewall. MSN sets everything inside of that modem. If you typed in ipconfig at a dos prompt I'm sure you'd have an IP address of 192.168.1.1. Which as we know is a private IP address not a public(internet) one. You're best bet is to change your NIC's MTU to 1490 same as what registers with speedguide's analyser change your RWin to a multiple of 1450 and be done with it. IMHO that modem is a piece of s*** and many others will agree with me. Most of your games won't work through it. One of my friends has MSN and has that modem I spent about an hour trying to change the MTU before I figured out what was going on.
Here is the website for that POS http://www.arescom.com/Arescom/Arescom_ ... DSunit.cfm
Respect it.
It's an internal setting of the modem configured remotely by msn, you can change the MTU of his NIC, but analyzer is always going to register 1490 since that is what the modem is using to talk to the gateway.Originally posted by Lobo
Why can't it be changed?![]()
This is directly from Arescom's site
(Question) I would like to receive the NetDSL manager software to configure my NetDSL unit. Anywhere I can download the software ?
Answer: The MSN NetDSL units are are pre-configured per stringent specifications from MSN. Because the units are pre-configured for MSN, we do not offer a software manager to the open public.
Respect it.
- mnosteele52
- Posts: 11913
- Joined: Tue Jul 24, 2001 12:00 pm
- Location: Chesapeake, VA
NP. I've been through all this before with my buddie. You can read about all the headaches with this modem on dlsreports. Arescom's site also states that these modems are preconfigured to MSN's specs. I say change your MTU to 1490 since that's what the modem is using. Change your RWIN to a multiple of 1450 that gives you the best speeds and be done with it.Originally posted by mnosteele52
Thanks for the info angentbeastthat's one to remember.
![]()
Here this is interesting too http://www.arescom.com/New/Trouble%20Sh ... faq.htm#q1
Most of the good stuff is down at the bottom
Respect it.
-
djicemanfrankie
- Member
- Posts: 42
- Joined: Mon Jul 29, 2002 1:26 pm
still no change. tried to clear all the setting on cablenut and reboot still no change on mtu. here is the result
TCP options string = 020405aa0103030001010402
MTU = 1490
Unrecognized MTU, or MTU = 0.
MSS = 1450
Maximum useful data in each packet = 1450, which equals MSS.
Default Receive Window (RWIN) = 31944
RWIN Scaling (RFC1323) = 0 bits
Unscaled Receive Window = 31944
For optimum performance, consider changing RWIN to a multiple of MSS.
Other values for RWIN that might work well with your current MTU/MSS:
510400 (MSS x 44 * scale factor of 8)
255200 (MSS x 44 * scale factor of 4)
127600 (MSS x 44 * scale factor of 2)
63800 (MSS x 44)
bandwidth * delay product:
Your RcvWindow limits you to: 1277.76 kbps (159.72 KBytes/s) @ 200ms
Your RcvWindow limits you to: 511.104 kbps (63.888 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = OFF
Time to live left = 55 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)
anybody knows the location of this mtu in the registry. my os is win2k
TCP options string = 020405aa0103030001010402
MTU = 1490
Unrecognized MTU, or MTU = 0.
MSS = 1450
Maximum useful data in each packet = 1450, which equals MSS.
Default Receive Window (RWIN) = 31944
RWIN Scaling (RFC1323) = 0 bits
Unscaled Receive Window = 31944
For optimum performance, consider changing RWIN to a multiple of MSS.
Other values for RWIN that might work well with your current MTU/MSS:
510400 (MSS x 44 * scale factor of 8)
255200 (MSS x 44 * scale factor of 4)
127600 (MSS x 44 * scale factor of 2)
63800 (MSS x 44)
bandwidth * delay product:
Your RcvWindow limits you to: 1277.76 kbps (159.72 KBytes/s) @ 200ms
Your RcvWindow limits you to: 511.104 kbps (63.888 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = OFF
Time to live left = 55 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)
anybody knows the location of this mtu in the registry. my os is win2k
- joecool169
- Posts: 805
- Joined: Fri Nov 16, 2001 10:52 pm
- Location: Ohio