Command Line Script does not use port assigned in Profile

weinerdr · Post by **weinerdr** » Mon Jan 16, 2012 4:27 pm

I have written a command line script for uploading/downloading files by calling a profile that works manually with a unique port (990). When I run the script, it always connects usning port 21, instead of 990.

Please advise how to fix this.

Post by **ForumAdmin** » Sat Jan 21, 2012 6:00 am

Make sure you're using a recent build (install over existing build).

Also include the log if you're still having issues.

weinerdr · Post by **weinerdr** » Mon Jan 23, 2012 6:02 pm

Usnig version 2.2 build 1718
Here is the log:

01/20/12 13:45

Started on Friday January 20, 2012 at 13:45:PMResolving ...

Connect socket #1640 to 10.1.100.243, port 21...Total uploaded files: 0

Total uploaded data: 0

Total downloaded files: 0

Total downloaded data: 0

01/23/12 11:56

Started on Monday January 23, 2012 at 11:56:AMResolving ...

Connect socket #1556 to 10.1.100.243, port 21...Can't establish connection --> :21 @ Mon Jan 23 11:56:59 2012
(0-5)ReconnectRetry #1, Connecting to ...Resolving ...

Connect socket #1556 to 10.1.100.243, port 21...

Profile has port 990.[/img]

Post by **ForumAdmin** » Thu Feb 02, 2012 3:10 pm

What's the actual command line being used?