Guaranteed Transmission Protocols For Windows? 536
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."
UDP. (Score:5, Funny)
Jesus protocol (Score:1, Funny)
Jesus is awesome.
That is to be expected (Score:2, Funny)
Re:Jesus protocol (Score:2, Funny)
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.
Re:Sneakernet (Score:2, Funny)
Re:Guaranteed? (Score:4, Funny)
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"
Re:Any encrypted transmission protocol actually (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.
Re:Jesus protocol (Score:3, Funny)
Not to mention the three day latency on refreshing the entropy pool.
Re:UDP. (Score:5, Funny)
Now I know the sound of packets being dropped. Thanks.
Re:UDP. (Score:5, Funny)
TCP is so horrible. I wish HTTP used UDP by default so I wouldn't have the pro
For everything else there's md5sum (Score:3, 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...
Re:Guaranteed? (Score:3, Funny)
Re:Jesus protocol (Score:4, Funny)
It must be open-source with such an odd name.
Close. It's open sores, especially around the wrists.
Cygwin + lpd (Score:3, 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.)
Re:UDP. (Score:1, Funny)
Ah, so you have a VOIP phone too
Re:UDP. (Score:2, Funny)