Error socket error in recv: 10057 with FTP transfer

Ask a Question
1

Hi,

Suddenly today, about 5 hours ago, I got the below error message.

The only thing on the WEB-site is the files with 0 KB.

I have searched the forum, but found to explanations.

What is happening.

It worked this morning, this evening it does not, and I have changed NOTHING.

This is the printout from the FTPUPD log.

Error socket error in recv: 10057 with FTP transfer
Error occured at:19:55:33 21-10-2005
Error socket error in recv: 10057 with FTP transfer
Error occured at:19:55:45 21-10-2005
Error socket error in recv: 10057 with FTP transfer
Error occured at:19:55:57 21-10-2005
list of files uploaded*
C:\wdisplay\webfiles\clientraw.txt

C:\wdisplay\webfiles\clientrawdaily.txt
C:\wdisplay\webfiles\clientrawextra.txt
C:\wdisplay\webfiles\clientraw.txt
C:\wdisplay\webfiles\clientrawdaily.txt
C:\wdisplay\webfiles\clientrawextra.txt
FTPUPD.EXE finished at 19:56:00 21-10-2005
Time taken = 0.65 minutes
Total bytes uploaded = 77 K
Total bytes uploaded for the day = 770 Mb
Total bytes uploaded for the month = 18727 Mb

Kind regards,

Esor

2

Hi
its not a bug in WD, its a problem with either your internet connection or your FTP server
first thing I would check is your firewall
and also check under view, ftp log, and click on view full log

3

It did not help to kill the Firewall.

I searched the Internet for the errorcode:

I found this:

WSAENOTCONN (10057) Socket is not connected.

Berkeley description: A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket) no address was supplied.

WinSock description: Same as Berkeley, and then some. An application attempted an input/output network function call before establishing an association with a remote socket (i.e. before calling connect() or accept()). It also has a specific meaning for setsockopt().

Detailed description:

setsockopt(): WinSock generates this error if you try to set SO_KEEPALIVE but the connection has already been aborted (e.g. a TCP reset received from remote host).

Developer suggestions: Chances are, that if you encounter this error, your application ignored the failure of some previous function. Although some WinSock implementations might not issue other errors if a connection fails, so you can handle this error as you would others that indicate connection failure.

WinSock functions: getpeername(), recv(), recvfrom(), send(), sendto(), setsockopt(), shutdown(), FD_CONNECT

See also: WSAECONNABORTED, WSAECONNRESET, WSAENETRESET, WSAETIMEDOUT

It looks to me that at some time FTPUPD did not close a connection correctly, and then keep the port open, and thus in trying reopening, it will not.

I logon to the FTP correctly, it changes the directory correctly, but when it starts communicating, it goes down the drain.

Any suggestions on how to rectify the problem?

Cheers
Per

4

try a pc reboot then to clear out the winsock connections to see if that helps at all

5

Brian,

I am getting closer and closer.

I have changed my WEB-hotel provider, and the new one gives me the path www/, in stead of the normal / - this means probably that somewhere in the system I am using wrong adresses, but there are so many places to change, and I do not seem to get it right.

Help

6

in the control panel, ftp/internet setup, connections, is the main FTP settings you need to set
set their the correct remote directory name

7

Hi Brian,

It looks like the FTP does not get the correct connection, look at the two images:

Somehow the WEB hotel provider have my path as oelstykkevejr/

And things to put in for the web must be in the WWW directory, but I do not get in tuch with that.

Any suggestions?

Kind regards,
Per

www.oelstykke-vejr.dk - which is not being update right now :frowning:

WD1.jpg
WD1.jpg381×122 18 KB

WD2.jpg
WD2.jpg595×404 54.2 KB

8

Remote directory on the FTP site does not appear correct to me… I would think, and for my host it would be “/www” not “www/”

-Bob

9

try just www :wink:

10

Brian,

Setup just before my last post was www/, nothing worked.

Late hours, going to bed, getting up this morning, everything works OK.

I HATE SELFREPAIRING problems, as the reason behind the problem is not found, and when will it occur again? :x

Anyhow thanks for your promt help.

Kind regards,

Per

www.oelstykke-vejr.dk

11

its possible your web server reset something duyring the wee small hours…?

12

Yeah maybe, it is a new provider, as the old one did not support XML, but changing WEB always sucks for at number of weeks.

Thanks again for your help, I will let you know if I find the reason behind the problem.

Kind regards,

Per

www.oelstykke-vejr.dk