Slashdot Mirror

← Back to Stories (view on slashdot.org)

Unix TCP Equivalent Settings in Windows 2000?

Posted by Cliff on from the RWIN-SWIN-and-MTU dept.

sameerdesai asks: "While working on a project that required client-server functionality I was running into processes that wouldn't finish and eventually hang. While running packet tracing, I found out the tcp_fin_wait_2_timeout setting on the server side (UNIX) was too low for the Windows client, and after increasing that value it worked great. I am trying to apply a similar technique for a Windows server and was wondering what the equivalent registry key is for UNIX's tcp_fin_wait_2_timeout setting? Also, is there a guide out there that compares TCP setting in UNIX with Windows?"

3 of 65 comments (clear)

  1. The registry key for windows by esac17 · · Score: 5, Informative

    Is HKLM\System\CurrentControlSet\Services\Tcpip\Param eters
    REG_DWORD
    30

    Setting this to anything below 30 decimal will just set it to 30 anyway though.

    http://www.microsoft.com/windows2000/techinfo/re sk it/en-us/default.asp?url=/windows2000/techinfo/res kit/en-us/regentry/58811.asp

    1. Re:The registry key for windows by sporktoast · · Score: 5, Informative

      Looks like you forgot to mention one thing, and the slashed up URL made it slightly more difficult to discover.

      There are about a hundred different entries contained in HKLM\System\CurrentControlSet\Services\Tcpip\Param eters. The REG_DWORD in question is the one labeled "TcpTimedWaitDelay". Accepted values are between 30 and 300 (seconds).

      --
      In a related story, the IRS has recently ruled that the cost of Windows upgrades can NOT be deducted as a gambling loss.
  2. Did you look here? by cnvogel · · Score: 5, Informative

    Maybe this document is enlightening? http://www.microsoft.com/windows2000/techinfo/resk it/en-us/default.asp?url=/windows2000/techinfo/res kit/en-us/regentry/33563.asp