Marc wrote: > With what I have see with the time, one port is skip for each transaction. > so with the range you have, only 2 transactions can be done. > Windows keep the port open for some time, so you come at the end with no > more port to do transaction.
Well, a closed socket remains in TIME_WAIT state for a while until it is destroyed by Windows, this discussion is not new. But I don't think that those sockets use/block a port while in that state. You can do a simple test, set PortRange to 1 and run the tool TCPView from Sysinternals (it updates the view of open sockets dynamically). Now connect and RETR or NLST to open a data connection in passive mode several times. In TCPView you will see sockets in TIMW_WAIT state however it's no problem to establish a new data connection. I checked that yesterday on W2K. --- Arno Garrels [TeamICS] > Even with a bigger range like 100 ports, you > can easily come to with no free port just by checking some directory just > because this will use a port for each send. > > The PasvPortRangeStart set the start > the max set the max and when the server can't use any port, this give you > the No available PASV ports. > > HTH > > > Marc > TYPSoft > http://www.typsoft.com > > At 03:50 2005-11-09 +0000, you wrote: >> There is only one client, this client connects to >> server checks some files and disconnects at some >> specified intervals(polling). So In this case the >> number 5 must be sufficient. PasvPortRangeStart is >> default 16384. Does this means that the application >> use 16384..16388.. If any port in this range is in >> use, then application fails or it is exceeds this >> 16388 limit... >> >>>> I ran ftpserver program, and the clients in passive >>>> mode but after a while constantly I am getting No >>>> available PASV ports error. -- 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
