> Tom Bentley said: >> Hello, >> >> I've got a wierd situation with ftp. When transferring files to an NT >> server, two bytes get appended to the end of the file. These two >> bytes are empty (00 value). Ftp reports a number of bytes sent two >> bytes larger that the original file, and the received file is actually >> 2 bytes larger than the original. These are zipped files, so >> naturally the CRC is broken and they won't unzip at the other end. > > > what ftp server is the NT side using(server & version), there are > hundreds of ftp servers available for NT. did you check to be sure your > transferring in binary mode not ascii? Some older servers default to > ascii, and usually the standard ftp client isn't smart enough to change > to binary mode on it's own. If all else fails try another ftp client? I > highly reccomend ncftp, its a real good client.
I've read that ncftp is a broken client not properly shutting down the connection after "exit". I personally haven't noticed anything (as this has been my fav client for a few yrs.) but my ftp will logout u out after 5 min of inactivity. > > I've never heard of such a thing happening, only thing I can think of is > the client is sending the file in ascii mode which still shouldn't cause > this but it's been 6 or 7 years since I last mistakenly sent a binary > file as ascii so I don't remember if the file size changed. > > nate > > > > > > -- > redhat-list mailing list > unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe > https://listman.redhat.com/mailman/listinfo/redhat-list -- Jesse Jacobs, Supa' Noob :) -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
