1. Forum
  2. FidoNet
  3. OS2PROG

  • FTPSERV resume?

    From Mike Luther@1:117/3001 to All on Monday, May 09, 2005 00:05:24
    I've looked in the documentation, but unless I missed it, nothing is said about
    the ability of FTPSERV to handle broken file uploads via a resume technique like ZMODEM can do in Bink etc.

    Can FTPSERV handle broken file transfers?

    Thanks!


    Sleep well; OS/2's still awake! ;)

    Mike @ 1:117/3001

    --- Maximus/2 3.01
    * Origin: Ziplog Public Port (1:117/3001)
  • From Sean Dennis@1:18/200 to Mike Luther on Monday, May 09, 2005 12:46:08
    Hello, Mike.

    On 08 May 05 at 23:05, Mike Luther wrote to All:

    Can FTPSERV handle broken file transfers?

    Yes, it can (at least in my experience).

    Later,
    Sean

    // hausmaus@darktech.org | http://midnightshour.net | ICQ: 19965647

    --- GoldED+/EMX 1.1.5-21020
    * Origin: Outpost BBS - Kennesaw, GA - outpostbbs.net (1:18/200)
  • From Mike Luther@1:117/3001 to Sean Dennis on Tuesday, May 10, 2005 01:25:52
    Thanks, Sean ..

    Can FTPSERV handle broken file transfers?
    Yes, it can (at least in my experience).

    OK, then if that is true, does the request for a resumed file transfer work for
    both UPLOADS and DOWNLOADS as you know it? And then, as I have learned, does it work if the requesting party that is to resume a broken transfer have to be from the same octed address, ###.###.###.### as well?

    Reason I'm probing this now is that for a party why nominally is needing to send 30-40MB of a file in uploads, even with a couple hours on a regular POTS line, is apparently being busted for re-work of their DHCP connection! What then happens, it seems, is the the file transfer gets busted in the re-up of the forced DHCP renewal. And the renewed address for the new DHCP issue by the
    IP comes back a different address than when the transfer was started.

    Thanks ..


    Sleep well; OS/2's still awake! ;)

    Mike @ 1:117/3001

    --- Maximus/2 3.01
    * Origin: Ziplog Public Port (1:117/3001)
  • From Sean Dennis@1:18/200 to Mike Luther on Thursday, May 12, 2005 17:15:51
    Hello, Mike.

    On 10 May 05 at 00:25, Mike Luther wrote to Sean Dennis:

    OK, then if that is true, does the request for a resumed file transfer work for both UPLOADS and DOWNLOADS as you know it? And then, as I
    have learned, does it work if the requesting party that is to resume a broken transfer have to be from the same octed address,
    ###.###.###.### as well?

    Answer: I'm not sure. :/ I think it has to be from the same octet address as well as within a certain time frame, IIRC. I have little experience with that,
    but AFAIK, that's correct.

    Reason I'm probing this now is that for a party why nominally is
    needing to send 30-40MB of a file in uploads, even with a couple hours
    on a regular POTS line, is apparently being busted for re-work of
    their DHCP connection! What then happens, it seems, is the the file transfer gets busted in the re-up of the forced DHCP renewal. And the renewed address for the new DHCP issue by the IP comes back a
    different address than when the transfer was started.

    Hmm, that's odd-are they running a router? Can they try to get the lease renewed only every 24 hours?

    My IP changes often, but I use a Windows program on my other machine to keep the domains straightened out.

    Later,
    Sean

    // hausmaus@darktech.org | http://midnightshour.net | ICQ: 19965647

    --- GoldED+/EMX 1.1.5-21020
    * Origin: Outpost BBS - Kennesaw, GA - outpostbbs.net (1:18/200)