 kobe08 join:2000-09-28 Vancouver, BC | reply to R2
Re: Enternet registry shot the "MaxFrameSize" key in the Net/000n entry is 1454 by default. Even if you change that key to 1492, it still won't set the MTU to 1492 since the "max" string in the 000n/ndi/params/MaxFrameSize directory is limiting it. -- "The Best Revenge Is Success" |
|
|
|
 smithPremium join:2000-07-13 | Are those shots of the Windows 98se OS Registry?
In the first window - your default "MaxFrameSize" key in the Net/000n entry shows "975", mine shows "1454"; should I change it to "975" with ME? Thanks. |
|
 kobe08 join:2000-09-28 Vancouver, BC | hey Smith,
1. Yes those are shots of the Windows 98SE Registry
2. No you should not change it to 975. My ISP uses an altered version of Enternet so that's why it is set like that. It's making me wonder if they did that on purpose to limit users to a certain speed. Anyways, that's specific to my system only so don't worry about it! -- "The Best Revenge Is Success" |
|
 smithPremium join:2000-07-13 | Thanks kobe08. |
|
 DrTCPYours trulyPremium,ExMod 1999-04 join:1999-11-09 Round Rock, TX
| reply to kobe08 kobe08:
Your interpretation of params keys are not right!
max, min, etc are just labels to be presented to the user when user goes to NIC properties to change. The value association with the label is written in MaxFrameSize value when user chooses it. In other words, those that are listed in the directory are just an enumeration of values. In fact you can create your own labels if you want and specify yet different values.
You can still keep the directory in original values but just change MaxFrameSize value. However, when you do this you should not go to NIC properties and change (and apply) again. Because that will overwrite what you've specified.
Similar think exists for IPMTU for Dial-up. DrTCP just changes the IPMTU not the associated labels in IPMTU directory. Hence, user must not change the value from Dial-up adapter advanced properties.
Tolunay
[text was edited by author 2000-12-09 02:05:36] |
|
 kobe08 join:2000-09-28 Vancouver, BC
| no no no Tolunay!
I'm not trying to interpret anything here. You know that NTS Enternet has a default MTU of 1454 right? Well that's the way to change it to 1492! Maybe I should of posted some shots of what it should look like before you tweak it. You also know that DrTCP doesn't affect the MTU for Enternet right? Well even if you go into your network properties and change the MaxFrameSize there (as in the second shot), you still won't be able to go over 1454 (if you press ok, it'll just revert back to 1454). So what you have to do is alter the max key, which is the thing that is limiting the MTU to 1454. The first pic is shot of where and where not to change it (A lot of people make the common mistake of changing the MaxFrameSize key in the 000n directory instead of the Max key in the 000n/ndi/params/ directory. You have to change it there before you set it in your network properties. Trust me on this one ... -- "The Best Revenge Is Success"
[text was edited by author 2000-12-09 07:56:53] |
|
 R2R NotPremium,MVM join:2000-09-18 Long Beach, CA kudos:1 | reply to DrTCP All I can say is that I have seen "kobe's tweak" work an awful lot of times. I don't have Enternet, but from what I have seen time and time again -- I have to believe what he says is right... |
|
 PinanPremium,ExMod 2000-03 join:2000-09-02 Murrieta, CA kudos:1 | Yup.:) |
|
 DrTCPYours trulyPremium,ExMod 1999-04 join:1999-11-09 Round Rock, TX | reply to kobe08 Sorry for the slow reply.
All I am saying that you don't need to change the max. Just set MaxFrameSize value in the registry and don't ever play with Network Properties afterwards (because if you do it will revert) back to whatever you've selected there.
Again, list of values defined in the MaxFrameSize key (not the value!) are what constitutes the choices. If you go to network properties and choose one of them than that value choosen will be written to MaxFrameSize value. But, if you don't modify it from Network properties whatever you've written in MaxFrameSize value in the registry will take effect.
You can verify this easily. Go to registry and set your max and MaxFrameSize different values. Reboot and logon with Enternet. Don't go the NIC properties to check. Do a ping test or tweak test.
You can see the same thing for dial-up adapters. There is IPMTU value and IPMTU key with a list of values defined there. Whatever you choose from NIC nic properties gets written to IPMTU value. However, you can still set IPMTU independent from IPMTU list of values. DrTCP does just that. It does not modify the list of possible values itself. Just the final value. Again, if you go the dial-up properties and select a different MTU there you'll override DrTCP specified IPMTU.
Tolunay |
|
 kobe08 join:2000-09-28 Vancouver, BC | hey Tolunay,
Trust me on this one buddy!!!! I know what i'm talking about.... I'm using the program. If you're right, then something is fishy with Enternet. The reason why Pinan asked to post a picture in the first place was because people where changing the MaxFrameSize value that you're referring to in the registry instead of the max value first. It doesn't work.... my guess is that the max value is the upper limit to whatever is set for MaxFrameSize and therefore overwrites it. People still ended up with that 1454 MTU. When I first discovered the tweak, I made the mistake of changing the MaxFrameSize key before the Max key was changed.... and I still ended up with a 1454 MTU. If you just change the MaxFrameSize key without altering the Max key first, then it will NOT hold. Do you have PPPoE Tolunay? Try downloading Enternet from somewhere (I've got it if you want it) and setting it up the way that you've said... you'll find that the tweak test will still say 1454.
-- "The Best Revenge Is Success" |
|