Hello, On Mon, 07 Jul 2003 20:27:28 -0400, Glenn McCorkle wrote:
> Oops.... I missed a step. :( > Add "QUIT" as the last step for each of the above cases. > (the last one becomes) > 1) USER (anonymous) > 2) PASS (your email address) > 3) TYPE I (set transfer type to BINARY) > 4) RETR (to download the ISO CDROM image) > 5) QUIT I remember that quite long time ago I had a problem with one of FTP servers. It looked like the QUIT command wasn't sent at all: the server was always showing the number of actually connected users and their limit. With every click in Arachne (to change directory or get a file) the number of connected users increased by one until it reached the limit (which was quite small). Then I was unable to do anything more, I had to wait some time (until I got automatically disconnected?). This behavior was reproducible, but only with this particular server. Unfortunately, I don't remember what kind of software was running on this server; its OS was some kind of Un*x, so it wasn't Micros**t IIS ;-) I don't even remeber what version of Arachne I was using at that time. It cannot be reproduced with current Arachne and current configuration of the server (the only user-visible changes are the greeting messages and user number limit, which is now quite big: 90). Do you have any idea what caused such a strange behavior? An idea: could QUIT be intelligently avoided between subsequent FTP transactions? Re-logging in often takes quite long time (looking at the status line messages), even when download speeds are very good. Michal
