I'm running a ftp server (FileZilla server).
I'm getting 500 Winsock Error 10053 on various FTP operations... on a FtpPutFile for example, but the server log show all A-Ok... and the file is on the server...
passive mode seems to have no effect.
any ideas?
FTP errors winsock 10053
Moderators: JRL, Dorian (MJT support)
-
- Junior Coder
- Posts: 35
- Joined: Thu Jan 12, 2006 9:20 pm
- Contact:
-
- Junior Coder
- Posts: 35
- Joined: Thu Jan 12, 2006 9:20 pm
- Contact:
I don't think I can help you, I have no FTP servers to play with, but I still have a question.
In your first post you said the file exists on the server even though you get an error message.
In your second post you say that it works if you "hammer at it".
Are you putting the file on the server by looping repeatedly or are you not getting the error message by looping repeatedly?
Good luck,
Dick
In your first post you said the file exists on the server even though you get an error message.
In your second post you say that it works if you "hammer at it".
Are you putting the file on the server by looping repeatedly or are you not getting the error message by looping repeatedly?
Good luck,
Dick
-
- Junior Coder
- Posts: 35
- Joined: Thu Jan 12, 2006 9:20 pm
- Contact:
-
- Automation Wizard
- Posts: 1101
- Joined: Fri Jan 07, 2005 5:55 pm
- Location: Somewhere else on the planet
I also have a filezilla server and have no problem with the combination of mjt's ftp and filezilla ftp server. As a test I just ran an n=200 loop using passive/ftpputfile to send a 400K file to that server, I wrote FTP_RESULT to a file and have zero errors.
Are you saying to are seeing fewer success FTP_RESULTS than the fileserver is saying it got files?
If you are not seeing errors in the filezilla log it's most likely because the failed attempts were really something like network failures to establish any connection to filezilla. FTP_RESULT isn't very informative, if you search the forum for "proxy" you'll see a recent thread where Marcus posted a suggestion for getting a full ftp log, or you could try using a regular ftp scripting approach that would enable you to get a full log of the event.
Are you saying to are seeing fewer success FTP_RESULTS than the fileserver is saying it got files?
If you are not seeing errors in the filezilla log it's most likely because the failed attempts were really something like network failures to establish any connection to filezilla. FTP_RESULT isn't very informative, if you search the forum for "proxy" you'll see a recent thread where Marcus posted a suggestion for getting a full ftp log, or you could try using a regular ftp scripting approach that would enable you to get a full log of the event.
-
- Junior Coder
- Posts: 35
- Joined: Thu Jan 12, 2006 9:20 pm
- Contact:
... further testing reveals that Windows Firewall is partly (completely) to blame. Turn it off, everything works flawlessly. Turn it on, and almost everytime macro ftp commands yield "500 Control connection closed"instead of "Success" (the command did seems to perform successfully despite the error message in the FTP_RESULT)
So I give in...
I'm gonna add a
"netsh firewall set opmode disable" to turn off the windows firewall and
"netsh firewall set opmode enable" when done...
-thanks y'all.
So I give in...
I'm gonna add a
"netsh firewall set opmode disable" to turn off the windows firewall and
"netsh firewall set opmode enable" when done...
-thanks y'all.