Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

Guest

Loaded latest version of server-side software - no difference whatsoever.

Any other suggestions anyone?
TIA
Guest

Martin
Thanks for your generous offer, but there's no way this organisation would let you at it - they'd rather lose the service! My apologies.

We are using an old version of Globalscape Secure FTP server, which looking at their version history, had "stability issues" with Win Server 2003...
Our next plan of attack is to upgrade to the latest version - hopefully that may clear it.

Thanks for your support.
martin

Re: Size of file transferred is different from the original

Can I have a test account on your server?
Guest

Size of file transferred is different from the original

Well, I did it again, with compression on, this time.
Everything SEEMED to go smoothly, but:
The orginal file size was: 622,415,872
The received file size was: 404,340,736

Here is the log:

Sending null packet to keep session alive.
Sending special code: 15
Copying 1 files/directories to remote directory "/Updates/"
PrTime: Yes; PrRO: Yes; Rght: rw-r--r--; PrR: No; FnCs: N; RIC: Yes; Resume: N (102400); CalcS: Yes; Mask: *.*
TM: B; ClAr: No; ExclM:
AscM: *.*html; *.htm; *.txt; *.php*; *.cgi; *.c; *.cpp; *.h; *.pas; *.bas; *.tex; *.pl; .htaccess; *.xtml; *.css; *.cfg; *.ini; *.sh; *.xml
File: "C:\Documents and Settings\rmckenna\My Documents\ECMS_Data_V2-05 sent.mdb"
Copying "C:\Documents and Settings\rmckenna\My Documents\ECMS_Data_V2-05 sent.mdb" to remote directory started.
Binary transfer mode selected.
Opening remote file.
Type: SSH_FXP_OPEN, Size: 58, Number: 46926339
Server initiated key re-exchange
Doing Diffie-Hellman key exchange
Initialised Blowfish client->server encryption
Initialised Blowfish server->client encryption
Initialised HMAC-SHA1 client->server MAC algorithm
Initialised HMAC-SHA1 server->client MAC algorithm
Initialised zlib (RFC1950) compression
Initialised zlib (RFC1950) decompression
Type: SSH_FXP_HANDLE, Size: 10, Number: 46926339
Type: SSH_FXP_WRITE, Size: 4118, Number: 46926598
303913 skipped SSH_FXP_WRITE, SSH_FXP_READ, SSH_FXP_DATA and SSH_FXP_STATUS packets.
Type: SSH_FXP_CLOSE, Size: 10, Number: 85827588
Type: SSH_FXP_STATUS, Size: 21, Number: 85827588
Status/error code: 0
Type: SSH_FXP_SETSTAT, Size: 54, Number: 85827849
Type: SSH_FXP_STATUS, Size: 21, Number: 85827849
Status/error code: 0
Listing directory "/Updates".
Type: SSH_FXP_OPENDIR, Size: 17, Number: 85828107
Type: SSH_FXP_HANDLE, Size: 10, Number: 85828107
Type: SSH_FXP_READDIR, Size: 10, Number: 85828364
Type: SSH_FXP_NAME, Size: 765, Number: 85828364
Type: SSH_FXP_READDIR, Size: 10, Number: 85828620
Type: SSH_FXP_STATUS, Size: 22, Number: 85828620
Status/error code: 1
Type: SSH_FXP_CLOSE, Size: 10, Number: 85828868
Type: SSH_FXP_STATUS, Size: 21, Number: 85828868
Status/error code: 0


Finally, I downloaded the previously uploaded file, and the filesize was knocked down to 64Mb this time!

Any further suggestions?
TIA
martin

Anonymous wrote:

Thanks
1. The Transfer Mode: Automatic
The files are all of type MDB, so force Text as Transfer Mode should not apply (MDB is not in the list).

You will see actually used mode on transfer progress dialog.

The main difference is with the networks....
The traffic at the server end is going through:
(a) a PIX firewall
- this happens on both installations
(b) a Content Server Switch (ie a Load Balancer)
- this does NOT occur on the working installation.....

Possibly this last factor is a big clue, but I would welcome your guidance.

I do not think it is the reason of the problem.
Guest

Thanks
1. The Transfer Mode: Automatic
The files are all of type MDB, so force Text as Transfer Mode should not apply (MDB is not in the list).

2. However your response triggered more analyis:
We already have another set-up which successfully handles the transfer of the same files!

Both set-ups use the following:
Client: WinSCP
Ver 3.7.1 (Build 257)
Server: Globalscape Secure FTP server
Ver 2.0.7 (Build 12.20.2004.3)
I appreciate the Server version is is a bit old, but as I said above, it performs fine on another installation with exactly the same files.

The main difference is with the networks....
The traffic at the server end is going through:
(a) a PIX firewall
- this happens on both installations
(b) a Content Server Switch (ie a Load Balancer)
- this does NOT occur on the working installation.....

Possibly this last factor is a big clue, but I would welcome your guidance.

Thanks in advance
martin

Re: File Size incorrect - supporting info

Are you sure you are using binary transfer mode? Also can you try more recent version?
Guest

File Size incorrect - supporting info

Just read the sticky!.

Using SFTP (V3) and SSH Ver 2.

Thanks in advance
Guest

Incorrect File Size - help please!

Using WinSCP 3.7.1
- transferring from WinXP to Windows Server 2003.
- file size 500Mb approx.
Problem: the transfer seems to go ahead ok, but the reported filesize on the server is:
- always wrong
- not consistent, over several attempts.

If info on config settings required, please advise, and I will post the required info.

Much appreciated