× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Tom,

There is a known bug in the Windows sockets implementation related to an out
of sequence FIN-ACK during an FTP session. Be sure you have all of the PTFs
applied on the AS/400 (IBM has a patch that provides a work-around). I don't
know if this is the cause of the problem, but is similar to one we saw
recently.

Patrick
----- Original Message -----
From: <tomh@simas.com>
To: <midrange-l@midrange.com>
Sent: Wednesday, December 12, 2001 4:36 PM
Subject: FTP problem


> This is a multipart message in MIME format.
> --
> [ Picked text/plain from multipart/alternative ]
> I have several users who ftp files to our system on a daily basis.  One of
> them is having, and I thought maybe you guys could help me diagnose it.
>
> Here is the entry from their log (ftp output redirected to a text file)
> 12/12/2001 2:56 PM CT
>
> 1212 13:51:26 (00000106) 172.138.50.153:1073 connected to
> 64.218.124.133:21
> 1212 13:51:27 (00000106) ftp.simas.com S(0) 172.138.50.153 netuser logon
> success (B1)
> 1212 14:14:38 (00000106) ftp.simas.com N(WSAEINTR) 172.138.50.153 netuser
> ERR:STOR ftpfile.zip (k:/ftpfiles/netuser/ftpfile.zip)(747064 bytes,
> 1029219 ms)
> 1212 14:14:38 (00000106) 172.138.50.153 connection reset
> 1212 14:14:38 (00000106) 172.138.50.153 connection closed
>
>
> And here is the relevent section from my ftp.log file:
> 1212 13:51:26 (00000106) 172.138.50.153:1073 connected to
> 64.218.124.133:21
> 1212 13:51:27 (00000106) ftp.simas.com S(0) 172.138.50.153 netuser logon
> success (B1)
> 1212 13:58:33 (000000b7) 216.102.56.130:45461 connected to
> 64.218.124.133:21
> 1212 14:14:38 (00000106) ftp.simas.com N(WSAEINTR) 172.138.50.153 netuser
> ERR:STOR ftpfile.zip (k:/ftpfiles/netuser/ftpfile.zip) (747064 bytes,
> 1029219 ms)
> 1212 14:14:38 (00000106) 172.138.50.153 connection reset
> 1212 14:14:38 (00000106) 172.138.50.153 connection closed
>
> It has something to do with the N(WSAEINTR) error, but I have no idea
> what.  We have other users who send files far larger than what this user
> is attempting, so I don't think it's a time-out issue on our end.  We've
> checked, and space doesn't appear to be an issue either.
>
> Tom Hightower
> Solutions, Inc
> http://www.simas.com
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.