I have a V6 FTP server running in an airport car park with a WLAN and two buses driving past it all day, calling home whenever they detect the WLAN. The buses don't always complete their FTP session before driving beyond WLAN range, leaving the FTP control connection open, seemingly for ever. Yesterday there were 19 open sessions, despite only two client PCs.
FTP Server: Client Connect from 192.168.16.19 [ClientWSocket527] (Total Clients: 19) It seems strange Windows (only XP on this particular server) does not timeout the TCP/IP with no keep alives, or is this something I have to set? Otherwise the FTP server really needs a time out for each client, triggered from a timer. Another server using IIS/5 for a different application has a similar problem with WLAN loss, but Microsoft seems to support a timeout in IIS. NT Event, source: MSFTPSVC, info: User metroline2 at host 192.168.31.23 has timed-out after 900 seconds of inactivity. Angus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be