Re: tcp/ip registry tweak not working

Hello

What had happpened was when the Nvidia Nforce network controller refreshed
it self by disconnecting then reconnecting the lan connection. It does this
if you change specific adapter characterisitics. After it disconnected the
lan connection, the OS froze..grrr... I had to reboot, thats when i noticed
the stack was loopy by not properly sending the correcting value.

I did try the drtcp works great..easy utility to use and yes it does the
interaction with the registry by adding the entries....i checked the registry
:)

It sure did trash the stack

Thanks Jack for the links and your quick responses.

cheers! have a good weekend



"Jack (MVP-Networking)." wrote:

Hi
Apparently your Registry change attempts with the TCP/IP Stack ended up
partially trashing the stack.
Nice that you found a solution.
Usually the whole process goes as follow,
http://www.ezlan.net/clean.html#refreshnet
Using the process above is safer since it is the software that interact with
the Registry rather then an individual using the registry Editor.
Jack (MVP-Networking).


"Marbles" <Marbles@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:80F0B521-E577-4307-9F3A-EDA8435B0BF2@xxxxxxxxxxxxxxxx
Jack I finally found & solved the problem. After sifting through number of
microsoft solution documents. Which none of the documents had a solution
for
this particular problem. I decided to use netsh again, since resetting the
tcp stack didnt work might as well try and reset the winsock...and it
worked/fixed it.

Here's what to do if you or anyone else reading this thread encounters
this
problem.

Problem:
You have entered these two registry values TcpWindowSize (entering a size
larger then 64240) & Tcp1323Opts (set to 1) in the registry key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters.
Then
when you verify the Tcp Receive Window by going to a website like
http://www.speedguide.net/analyzer.php to verify the tcp receive window
value
& the value still shows as the default 64240. Even tho you have entered a
different value then the default.

Solution:

1) open command prompt - start>run>cmd

2) from the command prompt enter the netsh utility by simply typing netsh

3) Type winsock this will put you at the level of netsh winsock>

4) type reset

5) reboot computer

6) This will fix the problem of the Tcp Receive window size always showing
incorrect value even tho you have entered a custom value in the registry.

7) To verify your tcp receive window size, one site to visit is
http://www.speedguide.net/analyzer.php



"Jack (MVP-Networking)." wrote:

Hi
I do not know how you tweak it and why you are choosing this value.
If you are using WinXP please look at this page.
Optimizing the TCP/IP Stack - http://www.ezlan.net/Internet_Speed.html
Jack (MVP-Networking).

"Marbles" <Marbles@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7F6250FA-C90E-4B94-A83D-EEFC1E7F3629@xxxxxxxxxxxxxxxx
Hello

I have used these 2 registry tweaks to improve the tcp throughput ,
Tcp1323Opts & TcpWindowSize. Both of them were working for a while
until
recently.

Now they dont work. Its defaulted back to 64240 for the receive window.

Changing the tcpwindows amount to any size will not work I have also
tried
swaping these 2 entries from \Tcpip\Parameters registry key to the
\Interfaces\######\ registry path. None seems to work. I have also
tried
resetting tcp/ip by using the netsh console and resetting tcp/ip to its
default setting ...still not functioning

Anyone know what could be causing it not to function correctly & how
does
one fix this ?

any & all help would be greatly appreciated




.

Relevant Pages

  • RE: RWIN (TCP Window Size) negotiates properly after upgrading to SP2
    ... Apparently SP2 uses a different registry setting than SP1: ... TCP window size. ... There are 3-4 places in the Windows Registry that affect the TCP Window. ...
    (microsoft.public.windowsxp.network_web)
  • Re: tcp/ip registry tweak not working
    ... I decided to use netsh again, ... tcp stack didnt work might as well try and reset the winsock...and it ... You have entered these two registry values TcpWindowSize (entering a size ... http://www.speedguide.net/analyzer.php to verify the tcp receive window value ...
    (microsoft.public.windowsxp.network_web)
  • Re: Setting size limit of data while reading or writing from sockets
    ... The receive buffer is not limited to application data. ... They apply to TCP as well. ... the stack may wait for the application, ... Since he has no idea what window TCP advertises to the other end ... ...
    (comp.unix.programmer)
  • Re: Setting size limit of data while reading or writing from sockets
    ... the stack may wait for the application, ... With TCP, the available room in the socket receive buffer is ... Since he has no idea what window TCP advertises to the other end ... ... existing implementations *DO* shrink their windows. ...
    (comp.unix.programmer)
  • Re: tcp/ip registry tweak not working
    ... Apparently your Registry change attempts with the TCP/IP Stack ended up partially trashing the stack. ... Using the process above is safer since it is the software that interact with the Registry rather then an individual using the registry Editor. ... tcp stack didnt work might as well try and reset the winsock...and it ... http://www.speedguide.net/analyzer.php to verify the tcp receive window value ...
    (microsoft.public.windowsxp.network_web)