TIME_WAIT connection state

Hello rebol-list, is it ok that there is still connection in the TIME_WAIT state after opening and closing TCP port under win2000? Proto Local Address Foreign Address State TCP oldes-athlon:5000 oldes-athlon:0 LISTENING TCP oldes-athlon:1035 oldes-athlon:5000 TIME_WAIT if I reopen the same port, new connection on different port is established... TCP oldes-athlon:1036 oldes-athlon:5000 ESTABLISHED TCP oldes-athlon:5000 oldes-athlon:1036 ESTABLISHED I can see that these TIME_WAIT connections disappear after some time, but I'm just wondering that other apps are not leaving such a connections. -- Best regards, rebOldes mailto:[oliva--david--seznam--cz]

Hi rebOldes, On Wednesday, July 16, 2003, 11:19:02 AM, you wrote: r> I can see that these TIME_WAIT connections disappear after some r> time, but I'm just wondering that other apps are not leaving such a r> connections. AFAIK all applications do. The TCP/IP stack puts sockets in TIME_WAIT after they are closed to catch any out-of-order packets that are still floating around, IIRC. Regards, Gabriele. -- Gabriele Santilli <[g--santilli--tiscalinet--it]> -- REBOL Programmer Amigan -- AGI L'Aquila -- REB: http://web.tiscali.it/rebol/index.r