Well I noticed the other day that my ftp was erroring out, didn't have time to mess with it but its still doing it so this morning I checked on it.
This is what it tells me if I click on the error light.
4/9/10 9:11:34 AM : FTP Connect Error, Error code = 10061
4/9/10 9:11:35 AM : FTP Connect Error, Error code = 10061
4/9/10 9:11:36 AM : FTP Connect Timeout
4/9/10 9:15:55 AM : FTP Connect Error, Error code = 10061
4/9/10 9:15:56 AM : FTP Connect Error, Error code = 10061
4/9/10 9:15:57 AM : FTP Connect Timeout
4/9/10 9:21:31 AM : FTP Connect Error, Error code = 10061
4/9/10 9:21:32 AM : FTP Connect Error, Error code = 10061
4/9/10 9:21:33 AM : FTP Connect Timeout
This is what the FTP log says when I enable logging.
09:06:44:343 ! HighLevelAsync 0
09:06:44:343 TWSocket will connect to 67.69.240.127:21
09:06:45:312 010A0E50 TCustomWSocket.Shutdown 1 836
09:06:45:312 ! HighLevelAsync 0
09:06:45:328 TWSocket will connect to 67.69.240.127:21
09:06:46:328 010A0E50 TCustomWSocket.Shutdown 1 868
09:06:46:328 ! HighLevelAsync 0
09:06:46:328 TWSocket will connect to 67.69.240.127:21
09:06:47:328 010A0E50 TCustomWSocket.Shutdown 1 872
try again
09:15:54:687 ! HighLevelAsync 0
09:15:54:687 TWSocket will connect to 67.69.240.127:21
09:15:55:718 010A0E50 TCustomWSocket.Shutdown 1 884
09:15:55:718 ! HighLevelAsync 0
09:15:55:718 TWSocket will connect to 67.69.240.127:21
09:15:56:734 010A0E50 TCustomWSocket.Shutdown 1 884
09:15:56:734 ! HighLevelAsync 0
09:15:56:734 TWSocket will connect to 67.69.240.127:21
09:15:57:734 010A0E50 TCustomWSocket.Shutdown 1 884
09:21:30:593 ! HighLevelAsync 0
09:21:30:593 TWSocket will connect to 67.69.240.127:21
09:21:31:578 010A0E50 TCustomWSocket.Shutdown 1 972
09:21:31:578 ! HighLevelAsync 0
09:21:31:578 TWSocket will connect to 67.69.240.127:21
09:21:32:687 010A0E50 TCustomWSocket.Shutdown 1 972
09:21:32:687 ! HighLevelAsync 0
09:21:32:687 TWSocket will connect to 67.69.240.127:21
09:21:33:687 010A0E50 TCustomWSocket.Shutdown 1 972
I have no idea.
Thanks for any and all help.
Welcome to the Cumulus Support forum.
Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080
Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080
FTP quit working
-
JabbaTHutt
- Posts: 13
- Joined: Mon 08 Feb 2010 5:30 am
- Weather Station: National Geographic 265NC
- Operating System: Windows XP
- steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: FTP quit working
Socket error 10061 means that the server rejected the connection request.
Steve
- steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: FTP quit working
I've just tried connecting to that IP address with FTP, and it connects OK. Given that it doesn't seem to be a problem at the server, the most likely cause is a firewall blocking the connection.
Steve
-
JabbaTHutt
- Posts: 13
- Joined: Mon 08 Feb 2010 5:30 am
- Weather Station: National Geographic 265NC
- Operating System: Windows XP
Re: FTP quit working
Thanks for the reply people. I had no access to it, I had rebooted the computer many times with no luck. The suddenly it started working again. If its the a computer problem then short of formating the drive and starting over there isn't much I can do.
I had been trying different AV programs and I imagine one of them has left something behind and is blocking ports as I have some other software having problems that another computer doesn't.
I had been trying different AV programs and I imagine one of them has left something behind and is blocking ports as I have some other software having problems that another computer doesn't.