Unix TCP Equivalent Settings in Windows 2000?
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?"
Is HKLM\System\CurrentControlSet\Services\Tcpip\Param eters
e sk it/en-us/default.asp?url=/windows2000/techinfo/res kit/en-us/regentry/58811.asp
REG_DWORD
30
Setting this to anything below 30 decimal will just set it to 30 anyway though.
http://www.microsoft.com/windows2000/techinfo/r
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
Ubscure interface?
.REG file, but does not want the user to be confused by any dialog boxes that are displayed.
t p://support.microsoft.com:80/support/kb/articles/Q 82/8/21.ASP&NoWebContent=1
REGEDIT [/v|-v] [/s|-s] <FILENAME>
[/s|-s]
When a filename is specified on the command line, this switch is used to suppress any informational dialog boxes that would normally be displayed. This is useful when the Setup program for an application wants to execute REGEDIT.EXE with a
Put what you need in the file you wish to import.
http://support.microsoft.com/default.aspx?scid=ht
"REGEDIT " isn't the obscure part. Just IMHO everything about the bits and handles after that is about equally obscure between regedit and /proc. Both are equally unfriendly. But you can do /proc without a special GUID program, so also IMHO it wins the toss.
The living have better things to do than to continue hating the dead.