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?"

1 of 65 comments (clear)

  1. Re:I don't get it by the+last+username · · Score: 5, Funny
    Sure. All you have to do is...

    Convince IT management it's a good idea

    Reduce Windows IT support headcount (make people redundant)

    Hire Linux IT support/developers

    Obtain budget for new hardware (I assume you didn't really mean that all the other apps on that server have to be ported from Visual Basic, so we're actually talking about a new server here)

    Explain increased staff costs and new hardware to senior management

    Explain free, "unsupported" software to senior management (or did you want funding for a Redhat support contract too?)

    Convince senior management it's a good idea

    Then either...

    Install Linux

    Port app to Linux

    Test

    or...

    Update CV (called a resume in French)

    Hit the job websites

    Phew! Well, at least you didn't have to...

    Change a single registry setting on an otherwise working system

    I'm happy running Linux at home (actually I run BSD, but that's besides the point), but I'd need a damn good reason before I'd suggest "just installing Linux" in a Windows-only shop.