From: "Tom Bentley" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: RE: FTP to NT system appends two null bytes SOLVED
Date: Monday, November 25, 2002 12:12 PM
Thanks to everyone for their input--this has been solved. Frequent mention
of "ascii" and "b
> jesse jacobs said:
>
>
>> 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 can't speak to y
jesse jacobs said:
> 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 can't speak to your first po
> 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 rec
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 fil
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