Please Help

[DrKrabbe]

TCP options string = 0204056401010402

MTU = 1420
MTU is not fully optimized for broadband. Consider increasing your MTU to 1500 for better throughput.

MSS = 1380
Maximum useful data in each packet = 1380, which is equal to 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) = 8280
RWIN Scaling (RFC1323) = 0 bits
Unscaled Receive Window = 8280
RWIN is a multiple of MSS
Other values for RWIN that might work well with your current MTU/MSS:
507840 (MSS x 46 * scale factor of 8)
253920 (MSS x 46 * scale factor of 4)
126960 (MSS x 46 * scale factor of 2)
63480 (MSS x 46)

bandwidth * delay product:
Your RcvWindow limits you to: 331.2 kbps (41.4 KBytes/s) @ 200ms
Your RcvWindow limits you to: 132.48 kbps (16.56 KBytes/s) @ 500ms
Consider increasing your RWIN value to optimize TCP/IP for broadband.

MTU Discovery (RFC1191) = ON

Time to live left = 111 hops
TTL value is ok.

Timestamps (RFC1323) = OFF

Selective Acknowledgements (RFC2018) = ON

IP type of service field (RFC1349)= 00000000

Here is the info that I received from the speedguide page

Ok, here is the deal. I was with Cox@home and got sick of the email problems and went with Quest cable modem service. They set me up with a static address, Docsis nor DHCP is available where I live through them (though it mysteriously was with cox...). I am now using a Lancity modem (the thing looks like a tank) and no matter what I do I can not get rwin above 65535 even after applying the vtcp.386 patch to enable scaling. Furthermore, I can not change rwin through cablenut's adjuster 4.02, DrTCP from Dslreports, nor doing it manually in the registry.

My speeds are absolutely horrible now. The only saving grace is no cap on uploads, but my upload speed is usually posting higher than my download speeds.


Bandwidth Speed Test

Server Location :San Antonio, USA

Test Type :downstream

Data Size (each test) :100KBytes

test 1
complete
195.2

test 2
complete
570.6

test 3
complete
370.9

Server Location :San Antonio, USA

Test Type :upstream

Data Size (each test) :50KBytes
139.9 kilobits / sec
17.5 kilobytes / sec

These are my download/upload speeds respectively. In addition other places report just about the same. I have removed all tweaks from my computer, and am running a 3com etherlink 3c900b-tpo network card

Any assistance at all would be greatly appreciated.
Thanks in advance...
Dr. Jeff Krabbe

[Lobo]

Please follow directions on my help page below, should work :)

[DrKrabbe]

TCP options string = 020405640101010101010402

MTU = 1420
MTU is not fully optimized for broadband. Consider increasing your MTU to 1500 for better throughput.

MSS = 1380
Maximum useful data in each packet = 1380, which is equal to 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
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:
507840 (MSS x 46 * scale factor of 8)
253920 (MSS x 46 * scale factor of 4)
126960 (MSS x 46 * scale factor of 2)
63480 (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 = 47 hops
TTL value is ok.

Timestamps (RFC1323) = OFF

Selective Acknowledgements (RFC2018) = ON

IP type of service field (RFC1349)= 00000000

I followed the instructions on your page lobo to the letter and this is still what I am getting. I do not understand for the life of me why it will not change the mtu and the rwin above 65535. I am not a newbie at this, and quite familiar with the tweaks and the settings. I guess I am at a complete loss here, and am willing to just about try anything. Thanks for posting so quickly lobo I really appreciated that.

thanks again...
Dr. Jeff Krabbe

[Lobo]

What OS, CPU, are you using proxey server and who is your provider :)

[DrKrabbe]

800 mhz amd thunderbird
384 mb pc133 ram
win98 SE
MSI k7t pro 6330
Quest for cable modem provider
Lancity modem set up statically

[DrKrabbe]

no proxy server also
thanks,
Dr. Jeff Krabbe

[Lobo]

Do this first:
Download lastest version of Dr. TCP to your desktop http://www.dslreports.com/front/drtcp.html
This is just a shortcut to your registry.
1.) To change RWIN or (DefaultRecieve Window) samething, do this, the number goes in box (afterselecting adapter: Tcp Receive Window.

2.) Window Scaling- Yes
3.) Time stamping - No
4.) Selective Acks - Yes
5.) Path MTU Discovery - Yes
6.) Max Duplicate ACKS - 3
7.) TTL - 32 -64 (Nothing to do with speed)
Click Apply button at botton and reboot for it to take affect.
8.) Blank boxes only mean default value is being used
9.) Do not change numbers in these boxes unless you know what you are doing.
(Play with it until apply button lites up, then click it) then reboot or it no workie
I would change RWIN to 513920, 522680 or 524176. Change IPMTU after selecting adapter to 1500 which will set MSS to 1460, which ever RWIN works best for you, have you applied the Vtcp386 Fix patch off patch page this site
:) :)

[DrKrabbe]

I tried all of that and still the same. As I mentioned before I installed the vtcp.386 update and verified that it was updated in my windows/system directory, and renamed the old and long time ago. Even still I went and double checked just to be sure. The mtu settings and the rwin just will not change. I am still at a complete loss. Thanks for all your help, and anymore recommendations you may be able to give me.

Dr. Jeff Krabbe

[Lobo]

Make sure there is a 1 in box on Cablenuts adjuster in box Tco1323Opts and leave GlobalmaxTcpwindosize-BLANK, try that :) :)
Click save to registry at bottom and reboot

[ 04-21-2001: Message edited by: Lobo ]

[DrKrabbe]

ok, tried that, and still the same result. This is starting to be the strangest thing I have ever seen. Thanks for all of you help so far.

Dr. Jeff Krabbe

[Lobo]

The only thing I can think of is to redownload Clablenut 4.0, you don't need 4xx to 4.02, this is supposed to wipe out all the TCP/IP stuff, don't load any ccs files, post what analyzer says after you do that :)

[DrKrabbe]

Still no luck. Do you suggest that I uninstall all network components on win98, aka my ethernet card, the tcp/ip, and microsoft client, and then restart. I just do not know what to do at this point, as I have never had these types of problems. It does not seem that anyone else with Lancity modems have this problem in particular either so I guess I will just keep looking and praying and hoping...

Dr. Jeff Krabbe

[Lobo]

Go to main page this site, and click on registry tweaks on left, this will tell you how to bring up registry and where to look for things that are giving you problems, you may have to change them yourself :) :)

[DrKrabbe]

As I explained before in the very first post I made, I have tried patches, DrTCP, cablenut 4.0 and 4.2, and manually entering in all the information in the registry and I still can not get the settings to stick. I am beginning to wonder if maybe (you would probably know more about this than I) the settings that are in the tcp/ip in network neighborhood are somehow incorrect.

Now just as an off chance, before this ever growing pain in the &^%#$ I was set up with Cox@home for DHCP. I have called and confirmed with the tech support of my current provider that all the settings for a static connection are correct, and I have checked their message board looking for any people experiencing the same problems as I am. I really do not know what to do, except to cancel the service because I have spent since 8 am this morning when it was installed trying to get this to work.

My system is not overclocked in any way, and it is always rock stable. Please, any suggestions you may have I will keep trying.

Thanks again,
Dr. Jeff Krabbe

[Lobo]

Are you home networked, any routers or hubs :)

[Buggyman]

Your MTU and Rwins are the tattle tellers.
Till you get the MTU up to 1500 all else mean nothing.
For some reason you update patch is not taking.
I would try to install the update patch again... I know this is a pain. But we gotta get the MTU up.
If all else fails .. for the heck of it.
Take and remove the Nic card property from the device manager(you must do this first).Shut down.. not reboot.. do a shut down. Remove the Nic card and reboot.
Then shut down again and install the nic card.
Reboot. see what happens. while loading up the software for the nic it will bring up the fact about the file being copied is older than the current. Keep the current file, it is your update.
I have a Lancity Modem as well and we are not DOCSIS ready either.
I hope they split the cable and ran a separate line to your modem.. no TV on that line at all. From the pole to your modem should only have One two way splitter in route.If you have cable TV too)

[DrKrabbe]

Buggyman,

I was hoping someone else would reply with this problem. Thanks I will try this when I get home, I had to leave and go to work, but this is what I suspected that I would have to do. Can I ask if you are happy with your Lancity tank of a modem? Oh, and yes they did run a seperate line for the cable modem.
Thanks for your reply.

Lobo,
Thanks for all the prompt responses and all the help. I am not running a network and therefore do not have a router.

One last question and hopefully the reinstall I do tonight will cut it....When I first got the modem my upload speeds were around 1500 kbps, now they just plain suck, and the provider confirmed that there are no upload or download caps at this time. Do you think I may be able to restore this upload speed once my system starts working like it is supposed to?

Thanks again,
Dr. Jeff Krabbe

[Lobo]

I don't see why not :) :)

[Buggyman]

The reason they have no cap is because they can't deliver! ;)
A non DOCSIS modem means good and bad... Good because of it's not regulated.
Bad because it doesn't meet the standards.
My Lancity doesn't give me any problems.. But then again I'd just a soon have High speeds.
:D

[Lobo]

Need larger CPU to break speed limit,lol :cool: :cool: :cool:

[DrKrabbe]

Ok, I uninstalled everything, and then reinstalled everything and guess what NO FREAKING CHANGE! What else can I do, the idiots at telechoice online (Quest), the level 2 tech support, did not know what MTU was? They also explained to me in a VERY condescending manner that speedguide's program that I am using to check TCP/IP settings is not reliable.

HELP PLEASE!
Dr. Krabbe

[flip]

I had the same problem with my MTU not changing. All patches manual tweaks, nothing worked. Searched for my reported MTU setting in the registry and found the numbers in my ISP entry and until I changed them there I was stuck with what they had set.

[DrKrabbe]

Hey you are on to something. I found something in this registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\Ndi\ATMDefaults

I am using a Lancity modem, but the problem is that the MTU is set in a binary fashion and I have no idea what to put that would equal 1500.

Thanks, Dr. Krabbe

[flip]

Thats not where I did the change it was
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Net\0006

and it was not bin. it was the actual number that had been displayed from the analyser on this site

MTU = 1492
MTU seems to be optimized for PPPoE... If you are not on a PPPoE connection, consider increasing your MTU to 1500 for optimal throughput.

MSS = 1452
Maximum useful data in each packet = 1452, which is equal to MSS.
MSS is optimized for PPPoE. If you are not on a PPPoE connection, consider increasing your MTU value.

Default Receive Window (RWIN) = 373760
RWIN Scaling (RFC1323) = 3 bits
Unscaled Receive Window = 46720
For optimum performance, consider changing RWIN to a multiple of MSS.
Other values for RWIN 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:
Your RcvWindow limits you to: 14950.4 kbps (1868.8 KBytes/s) @ 200ms
Your RcvWindow limits you to: 5980.16 kbps (747.52 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

[ 04-22-2001: Message edited by: flip ]

[DrKrabbe]

Thanks to all who responded!

I am still having the same problems but I am also beginning to think that it is a computer related issue vs. a provider issue as well. I really did not want to reinstall windows...with a clean hard drive format...but it may be the easiest way to solve this dilemna. I made sure the vtcp.386 file was for win98/98se and just went and rechecked the version number against the one recommended in microsoft's knowledge database and it is correct.

Once again, thanks to everyone who reponded
Dr. Jeff Krabbe

[Storm90]

Proubly would be the best. Sounds like there are to many different tweaks in the reg . That did not get removed. After reinstalling. Install the VTCP386 Patch first. Then Pick out the one tweak you wish to use. Either speed guides or Cablenuts. The advantage with cable nuts is you can use the adjuster to put the settings you want and work the best for you.. PLus also remember to back the reg up before doing any of this. This way you won't endup in the same boat. GoodLuck!You do not need a larger cpu just the right tweaks.
;)

[ 04-22-2001: Message edited by: Storm90 ]

[Lobo]

Larger CPU was a joke to Buggyman, not Doc :)

[Buggyman]

DrKrabbe,
I have to be honest with you... I'm at lost as to what is happening.
There are several People posting who are having trouble with MTU settings. Nothing seems to work for them either.
But I did want to point out that The Problem is in your PC... not your provider.
So don't worry about the Lancity (Tank) modem.
MTU is a setting that your windows uses to transmit online. So you could uplug your Cat-5 cable and play with it all day.
All we have to hope for is One of the Guru's can offer some suggestions.
I know Cablenut has been working with the other guy. If you read up on the "Lance" post you can see his problem is similar to yours. Only he can't get his MTU down to 56K modem settings.
Don't give up... I know All the Guru's have been Extremly Busy these last couple weeks.
Maybe one will find a few minutes to pick up where we left off.
Keep in Touch. :)

PS ... just to be on the safe side...
there are differance version of the Vtcp.386 Update.. I doubt you did but just to be safe. you did get the one for your Version of windows didn't you? They have two.. one for win/95 and a separate one of win/98se.
Sorry if I offend you in this. :(

[ 04-22-2001: Message edited by: Buggyman ]

[DrKrabbe]

Ok, I completely reformatted my hard drive and reinstalled windows. Added no tweaks, just installed my network card, and configured network neighborhood. When and checked it and Guess what, still the same problem. So I downloaded DrTCP and correctly entered the settings in (I hit apply)but still can not change rwin, and can not move mtu above 1420.


Us West Telechoice (who has been getting calls from me every 2 hours for another tech support fellow) emphatically denies any use of proxies, or messing with my signal and resetting mtu and so forth. I am really starting to NOT believe them anymore, and I find it harder and harder to believe that it is now my system and not theirs.

There has to be someone out there (Cablenut...Dannjr?) that can help, or refer me to someone who can.

Disgruntled, Frustrated, and just plain confused...

Dr. Jeff Krabbe

[DrKrabbe]

R2 over at Dslreports nailed this one right on the head. It appears one of the routers was not set correctly and that is why mss was 1380, and mtu 1420. After I used WinpCap with the analyzer program and sent it off to R2 to dissect he discovered this. I also send this to the Network Administrator for Qwest and he finally saw the light and changed the settings. So I now have normal mtu and mss, but still no windows scaling. The windows scaling is also a problem on Qwest's end, and I sent them another email in detail with the results showing specifically that rfc1323 was not on. Hopefully they will change this as well, only time will tell.

This was just an update in case anyone wanted to put this annoyance into memory in case it happens to someone else.

Dr. Jeff Krabbe

[Lobo]

Thanks for letting us know Doc as I know you spent alot of time waiting for help but we did not know what to do, or let me rephase that, I did not know what to do, but please come back anyway and glad your making some progress. :)

[DrKrabbe]

No problem, I just really appreciated the fact that you took the time to help me, so I thought the most courteous thing to do would be to let everyone know how everything worked out.

Thanks to all...

Dr. Jeff Krabbe

[rmrucker]

Jeff, now to see if we can nail them on the Window Scale! Cheers.
~~~~~~~~~~~

Lobo, this was a killer problem. The ISP was truly modifying his packets to lower the MSS. They are now STILL modifying his packets to turn OFF scaling. Quite amazing.

[Lobo]

Sorry I not there guys but I just got my XP and am reformatting and all that, man is the world going to be shocked when they see this, nothing is the same, and I mean nothing,
have not had any problems yet, it is fast, have fun I got work to do, Dannjr help out please :) :) :)