SSL errors in Command Line

Report client bugs
Post Reply
martinbiz
Posts: 3
Joined: Wed Sep 06, 2006 11:27 pm

SSL errors in Command Line

Post by martinbiz »

I am able to setup profile in the gui and connect properly but when I try to run from the command line it gives me SSL errors:

SSL/TSL Errors - 0, SSL Error - 1
550 No Data Sets Found ...

I stripped the command line command down to "coreftp.exe -site wic" and it still happens.

I then can enter the gui app and connect to profile wic and it works perfect. Any help would be great.

I have tried both Windows SSl and OPen SSL and it works the same way.
martinbiz
Posts: 3
Joined: Wed Sep 06, 2006 11:27 pm

ssl command line vs gui

Post by martinbiz »

This is log from GUI:

Welcome to Core FTP, release ver 1.3c, build 1447.6 (U) -- © 2003-2006
WinSock 2.0
Mem -- 785,908 KB, Virt -- 2,097,024 KB
Started on Thursday September 14, 2006 at 22:14:PM
Resolving vwix.dhs.ca.gov...
Connect socket #1440 to 134.186.44.120, port 21...
220-FTPSECRE IBM FTP CS V1R4 at MVSSY1.TEALE.CA.GOV, 05:14:39 on 2006-09-15.
220-FTPSECRE IBM FTP CS V1R4 at MVSSY1.TEALE.CA.GOV, 05:14:39 on 2006-09-15.
AUTH SSL
234 Security environment established - ready for negotiation
SSLv3 (RC4/SHA), 128 bits
USER HD02982A
331 Send password please.
PASS **********
230 HD02982A is logged on. Working directory is "HD02982A.".
SYST
215 MVS is the operating system of this server. FTP Server is running on z/OS.
SITE LRECL=11 BLOCKSIZE=4400 RECFM=FB
200 SITE command was accepted
Keep alive off...
CWD 'HD.WIX8140.HDVWIXP'
250 "HD.WIX8140.HDVWIXP." is the working directory name prefix.
PBSZ 0
200 Protection buffer size accepted
PROT P
200 Data connection protection set to private
PASV
227 Entering Passive Mode (134,187,51,1,196,188)
LIST
Connect socket #940 to 134.187.51.1, port 50364...
SSLv3 (RC4/SHA), 128 bits
125 List started OK
250 List completed successfully.
Transferred 208 bytes in 0.047 seconds

Here is the command line:
c:”\program files\coreftp\coreftp.exe” -O -u c:\path\file.dat -site mysite -output output.log -log log.log

Here is the command line log:
Started on Thursday September 14, 2006 at 22:11:PMResolving vwix.dhs.ca.gov...

Connect socket #1472 to 134.186.44.120, port 21...220-FTPSECRE IBM FTP CS V1R4 at MVSSY1.TEALE.CA.GOV, 05:11:41 on 2006-09-15.

220-FTPSECRE IBM FTP CS V1R4 at MVSSY1.TEALE.CA.GOV, 05:11:41 on 2006-09-15.

AUTH SSL

234 Security environment established - ready for negotiation

SSLv3 (RC4/SHA), 128 bitsUSER HD02982A

331 Send password please.

PASS **********

230 HD02982A is logged on. Working directory is "HD02982A.".

SYST

215 MVS is the operating system of this server. FTP Server is running on z/OS.

SITE LRECL=11 BLOCKSIZE=4400 RECFM=FB

200 SITE command was accepted

PWD

257 "'HD02982A.'" is working directory.

PBSZ 0

200 Protection buffer size accepted

PROT P

200 Data connection protection set to private

PASV

227 Entering Passive Mode (134,187,51,1,196,178)

LIST

Connect socket #1484 to 134.187.51.1, port 50354...Error reading secure data from the server.Error loading directory...550 No data sets found.
PWD

257 "'HD02982A.'" is working directory.

CWD 'HD02982A.'

250 "HD02982A." is the working directory name prefix.

PASV

227 Entering Passive Mode (134,187,51,1,196,31)

LIST

Connect socket #1484 to 134.187.51.1, port 50207...Error reading secure data from the server.Error loading directory...MKD wic

550 No data sets found.

PWD

550 error allocating HD02982A.WIC

CWD D02982AA.'wic

257 "'HD02982A.'" is working directory.

PASV

501 A qualifier in "D02982AA.'wic" begins with an invalid character

CWD D02982AA.'wic

227 Entering Passive Mode (134,187,51,1,196,117)

TYPE I

501 A qualifier in "D02982AA.'wic" begins with an invalid character

PASV

200 Representation type is Image

D090606.T162211.R123456 - 0 bytes transferred

CWD D02982AA.'wic

227 Entering Passive Mode (134,187,51,1,196,117)

PASV

501 A qualifier in "D02982AA.'wic" begins with an invalid character

CWD D02982AA.'wic

227 Entering Passive Mode (134,187,51,1,196,117)

TYPE I

501 A qualifier in "D02982AA.'wic" begins with an invalid character

PASV

200 Representation type is Image

D090606.T163556.R123456 - 0 bytes transferred

CWD D02982AA.'wic

227 Entering Passive Mode (134,187,51,1,196,117)

PASV

501 A qualifier in "D02982AA.'wic" begins with an invalid character

CWD D02982AA.'wic

227 Entering Passive Mode (134,187,51,1,196,117)

TYPE I

501 A qualifier in "D02982AA.'wic" begins with an invalid character

PASV

200 Representation type is Image

D090606.T163849.R123456 - 0 bytes transferred

CWD D02982AA.'wic

227 Entering Passive Mode (134,187,51,1,196,128)

PASV

501 A qualifier in "D02982AA.'wic" begins with an invalid character

CWD D02982AA.'wic

227 Entering Passive Mode (134,187,51,1,196,128)

TYPE I

501 A qualifier in "D02982AA.'wic" begins with an invalid character

PASV

200 Representation type is Image

D090606.T164133.R123456 - 0 bytes transferred

CWD D02982AA.'wic

227 Entering Passive Mode (134,187,51,1,196,128)

PASV

501 A qualifier in "D02982AA.'wic" begins with an invalid character

CWD D02982AA.'wic

227 Entering Passive Mode (134,187,51,1,196,128)

TYPE A

501 A qualifier in "D02982AA.'wic" begins with an invalid character

PASV

200 Representation type is Ascii NonPrint

wic1.txt - 0 bytes transferred

Total uploaded files: 0

Total uploaded data: 0

Total downloaded files: 0

Total downloaded data: 0




mike
Posts: 47
Joined: Fri Jul 28, 2006 4:36 pm

Post by mike »

try adding this to your command line:

-p HD.WIX8140.HDVWIXP
Post Reply