SmartFTP transfers .gz in ASCII mode and ignores Properties.

When transfering a file between two Solaris 8 servers it transfers in passive mode and ASCII. e.g.

227 Entering Passive Mode (192,168,235,75,128,38)
STOR sbe-1.0-b12.tar.gz
150 ASCII data connection for sbe-1.0-b12.tar.gz (192.168.235.30,17).
226 Transfer complete.
13333977 bytes received successfully. (4340.49 KB/s) (00:00:03).

I have set the default and both servers to Active & Binary only, but it tranfers the file via ascii anyway. I have another server with the same patch level of the OS which transfers fine.
e.g.
227 Entering Passive Mode (10,128,84,47,130,191)
STOR sbe-1.0-b12.tar.gz
150 Binary data connection for sbe-1.0-b12.tar.gz (10.128.84.42,20).
226 Transfer complete.
13333977 bytes received successfully. (6510.73 KB/s) (00:00:02).

The problem is very likely with your Ascii/Binary settings or the transfer mode you have choosen.

-Mat

The modes make a difference but I don't understand how they work. From trial and error I have tried:




FROM          TO            Transfer



BIN,no PASV   BIN,no PASV   ASCII, PASV



BIN,PASV      BIN,no PASV   ASCII, PASV



BIN,no PASV   BIN,PASV      BIN, PASV  <= will use this from now on.



BIN,PASV      BIN,PASV      ASCII, PASV

It is unclear to why setting the source to disabled PASV on the source allows BINARY when the others are ASCII. :?: It is also unclear why disabling PASV still results in a PASV transfer. :?:
Lastly, If I transfer from this server or use another server with the same OS rev and patch level, the default settings transfer fine.

BTW: SmartFTP is a cool tool. [/code]

Sorry. It doesnt make sense to me.

We tried to reproduce it but there was no problems we could find.

Please provide more information otherwise we cannot fix the possible bug.

For FXP transfers PASV mode is always required on one side.

Thanks.

-Mat