Somebody will take a look at it. I did manage to get the same server
response error which I think is generated if the server times out
before REBOL does and closes the connection. REBOL expects to hear
something back and does not so it fails to parse the empty response.
Thanks for the info Larry, Nigel.
Sterling
> Hi Nigel, Sterling
>
> There does appear to be some kind of problem with the REBOL ftp is this
> instance. I was able to get the dir listing with WS-FTP although the server
> was slow (took about 150 seconds).
>
> With REBOL I got (don't need the user e-mail if set-net has e-mail
> configured):
>
> >> system/schemes/default/timeout: 5000
> == 5000
> >> list-dir ftp://ftp.europe.ibm.com/aix/fixes/cad/other/catia_oem_v4/IRIX/
> connecting to: ftp.europe.ibm.com
> ** User Error: Server error: tcp 421 Timeout (1800 seconds): closing control
> connection..
> ** Where: list-dir
> ftp://ftp.europe.ibm.com/aix/fixes/cad/other/catia_oem_v4/IRIX/
>
> I had no problem getting the dir lists for each of the parent directories
> using REBOL, so I am inclined to agree with your speculation that the number
> of files or the time required for the server to send them is part of the
> problem. Based on the tests with WS-FTP, the server should have sent back
> the dir-list in about 180 seconds, REBOL apparently was unable to receive or
> acknowledge this, leading to the server timeout at 1800 seconds.
>
> The results of using 'trace/net are shown below. I have CC'd this to
> feedback, perhaps Sterling or someone else at Rebol tech can diagnose the
> problem? (I see Sterling has already replied:-)
>
> I just tried WS-FTP a seond time. It took 120 seconds for the dir-list to
> start downloading. The dir-list was fine.
>
> Hope this helps
>
> Larry
