There is a way around this. I used to run into the same problem, but I
found a setting that changed the default behavior. Unfortunately I can't
remember for sure which setting it was, but I seem to remember that the
problem was that when I got a 500 error, CuteFTP asked for a new username
and password, so I shut off the prompt in the settings that says prompt
user when login/pass fails. This is from the help screen on that page:
Prompt for user and pass when login fails:
CuteFTP will prompt for a user and password if your login sequence fails.
This can be turned off if you are sure you have entered the correct user
and pass and are being rejected by the server due to other reasons, such as
there being to many users.
Here's a quick dump of the log file of how it looks for me when I get a 500
error:
STATUS:> Connected. Authenticating...
COMMAND:> USER <deleted>
331 Password required
COMMAND:> PASS <deleted>
530 Already logged in
ERROR:> Password not accepted
ERROR:> Can't login. Still trying...
STATUS:> Disconnect: Wednesday 13:11:15 01-30-2002
STATUS:> Waiting to try again...
Hope this helps.
Dave
At 09:54 AM 1/30/02 -0800, Seth Manheim wrote:
>I'm curious to know if anyone uses this app? From what I've seen, if a site
>is busy and it can't connect, generating a 500 error, the Pro app does not
>try to reconnect. If it's a 400 error, it will try to reconnect within the
>specified interval (120 seconds, for example). However, many etree sites do
>give a 500 error when the site is busy.
_______________________________________________
etree mailing list <[EMAIL PROTECTED]>
http://mail.etree.org/mailman/listinfo/etree
