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

Thank you for the advice to use "explicit" with port 990. It solved my similar issue.
martin

Re: TLS connect: error in SSLv2/v3 read server hello A

While you connect to implicit TLS port 990 with Ipswitch too, the protocol used is explicit TLS. It seem like a misconfigured FTP server.

Try forcing WinSCP using explicit TLS, while still using implicit TLS port 990.
spidermayin_40

Re: TLS connect: error in SSLv2/v3 read server hello A

martin wrote:

What version of WinSCP are you using?
Show us IpSwitch log file too.


Thanks for the response. I am using 5.9, but I upgraded to the latest version and got the same error. Here is the IpSwitch log. I connected in IpSwitch and navigated to one of the folders, so the log below is showing that.



Finding Host ftp.hpac-portal.com ...
Connecting to 107.23.205.124:990
Connected to 107.23.205.124:990 in 0.173500 seconds, Waiting for Server Response
Initializing SSL Session ...
220 FTP Server ready.
AUTH TLS
234 AUTH TLS successful
SSL session NOT set for reuse
SSL Session Started.
Host type (1): AUTO
USER ????
331 Password required for ?????
PASS (hidden)
230 User ???? logged in.
SYST
215 UNIX Type: L8
Host type (2): Unix (Standard)
PBSZ 0
200 PBSZ 0 successful
PROT P
200 Protection set to Private
Sending "FEAT" command to determine what features this server supports.
FEAT
211-Features:
MDTM
MFMT
TVFS
AUTH TLS
MFF modify;UNIX.group;UNIX.mode;
MLST modify*;perm*;size*;type*;unique*;UNIX.group*;UNIX.mode*;UNIX.owner*;
PBSZ
PROT
REST STREAM
SIZE
211 End
Finished interpreting "FEAT" response.
Sending the FEAT command is optional. You can disable it in the site options of the profile.
PWD
257 "/" is the current directory
TYPE A
200 Type set to A
PASV
227 Entering Passive Mode (107,23,205,124,195,84).
connecting data channel to 107.23.205.124:195,84(50004)
data channel connected to 107.23.205.124:195,84(50004)
LIST
150 Opening ASCII mode data connection for file list
# transferred 260 bytes in 0.021 seconds, 98.780 kbps ( 12.347 kBps), transfer succeeded.
226 Transfer complete
CWD pre-processing
250 CWD command successful
PWD
257 "/pre-processing" is the current directory
TYPE A
200 Type set to A
PASV
227 Entering Passive Mode (107,23,205,124,195,107).
connecting data channel to 107.23.205.124:195,107(50027)
data channel connected to 107.23.205.124:195,107(50027)
LIST
150 Opening ASCII mode data connection for file list
# transferred 117 bytes in 0.007 seconds, 137.008 kbps ( 17.126 kBps), transfer succeeded.
226 Transfer complete
QUIT
221 Goodbye.
Connection closed. Ready for next connection.
martin

Re: TLS connect: error in SSLv2/v3 read server hello A

What version of WinSCP are you using?
Show us IpSwitch log file too.
spidermayin_40

TLS connect: error in SSLv2/v3 read server hello A

Getting the error in the subject line when trying to connect to a server. They specified to use explicit FTP over TLS. I can get connected in IpSwitch, but not WinSCP. I attached a log showing the error.


Thanks