Slashdot Mirror


Guaranteed Transmission Protocols For Windows?

Michael writes "Part of our business at my work involves transferring mission critical files across a 2 mbit microwave connection, into a government-run telecommunications center with a very dodgy internal network and then finally to our own server inside the center. The computers at both ends run Windows. What sort of protocols or tools are available to me that will guarantee to get the data transferred across better than a straight Windows file system copy? Since before I started working here, they've been using FTP to upload the files, but many times the copied files are a few kilobytes smaller than the originals."

16 of 536 comments (clear)

  1. UDP. by langelgjm · · Score: 5, Funny

    Clearly you're looking for UDP. Next question.

    --
    "Anyone who [rips a CD] is probably engaging in copyright infringement." - David O. Carson
    1. Re:UDP. by El+Torico · · Score: 4, Funny

      Now I know the sound of packets being dropped. Thanks.

      --
      In the land of the blind, the one-eyed man is usually crucified.
    2. Re:UDP. by sofar · · Score: 5, Funny

      TCP is so horrible. I wish HTTP used UDP by default so I wouldn't have the pro

    3. Re:UDP. by Anonymous Coward · · Score: 1, Funny

      Ah, so you have a VOIP phone too

    4. Re:UDP. by Chees0rz · · Score: 2, Funny

      OYu need tdownoadl hte fxofire lugin

  2. Jesus protocol by Anonymous Coward · · Score: 1, Funny

    Jesus is awesome.

    1. Re:Jesus protocol by Tablizer · · Score: 2, Funny

      Jesus is awesome.

      I've never heard of that product. Who makes it? Can it do binary transfers also? It must be open-source with such an odd name.

    2. Re:Jesus protocol by Loko+Draucarn · · Score: 3, Funny

      Not to mention the three day latency on refreshing the entropy pool.

    3. Re:Jesus protocol by melikamp · · Score: 3, Funny

      It must be open-source with such an odd name.

      Close. It's open sores, especially around the wrists.

  3. That is to be expected by kseise · · Score: 2, Funny

    Think of this transfer model like a car, the further it goes, the more bytes are burned up. they just need to be added back in with a network filling station. I would look to google for a government approved provider.

  4. Re:Sneakernet by nystire · · Score: 2, Funny

    Or a mine-field...

  5. Re:Guaranteed? by jeffmeden · · Score: 3, Funny

    You forgot a few:

    Windows at both ends... Used to use FTP... Considering windows file sharing...

    Is anyone else a little nervous? I hope by 'government' he means Department of Natural Resources or some equally uninteresting entity. I am picturing someone at the SEC going "You know, I swear this accounting data had a few more rows the last time I looked at it-- Oh well it's not like this Madoff guy is actually up to anything strange anyway"

  6. Re:Any encrypted transmission protocol actually by Anonymous Coward · · Score: 4, Funny

    I sincerely hope, for the asker's sake and possibly for the country's sake, that these files he works with are trivial.

    Well, let's see.

    transferring mission critical files across a 2 mbit microwave connection, into a government-run telecommunications center

    Pretty sure encryption isn't necessary.

  7. For everything else there's md5sum by Colin+Smith · · Score: 2, Funny

    The transmission system is irrelevant. All that matters is that you know you have received whatever was sent.

    Just make sure you send a checksum and that the received file matches.

    oh wait... Windows scripting...

    --
    Deleted
  8. Re:Guaranteed? by gandhi_2 · · Score: 2, Funny

    I worked on a system for the Utah DNR once. Data about sensitive species, species of concern, and endangered species have security requirements. If someone finds out how many Woundfin we are down to...the terrorist win.

  9. Cygwin + lpd by rlseaman · · Score: 2, Funny

    Set up a BSD lpd queue under Cygwin, something like:

    sendit:lp=/spool/null:sd=/spool:if=/spool/sendit.sh:sf:sh:mx#0:

    Have the sendit.sh script do whatever it is you want with the file. To send a file: lpr -Psendit filename

    Configuration of the network queue left as an exercise for the student. (Hint - queue pathnames locally.)