Unable to Connect via SSL
Unable to Connect via SSL
I am using Coreftp lite 1.3 and I cannot connect. I have windows xp and Mcafee. I have been trying unsuccessfully to transfer. Below is message that I get in the upper left hand corner. The message "SSL connection not established" is what I get when I try to reconnect again.
AUTH SSL
234 SSL enabled and waiting for negotiation
SSL Connection not established
Connect socket #468 to 68.21.158.100, port 1088...
220 outsideserver1.www.oncalltranscription.com X2 WS_FTP Server 4.0.0 (2491859919)
AUTH SSL
234 SSL enabled and waiting for negotiation
Thanks for your help!!
Elizabeth
AUTH SSL
234 SSL enabled and waiting for negotiation
SSL Connection not established
Connect socket #468 to 68.21.158.100, port 1088...
220 outsideserver1.www.oncalltranscription.com X2 WS_FTP Server 4.0.0 (2491859919)
AUTH SSL
234 SSL enabled and waiting for negotiation
Thanks for your help!!
Elizabeth
This is most likely a firewall issue with McAffee. You can run a quick test by disabling your firewall.
We'll have to set it up here though and find out if the McAfee firewall is blocking the outgoing connection or the actual SSL command. I'll try and get you an answer very soon. In the meantime, I would check the McAfee web site for more information ( http://forums.mcafeehelp.com ).
Jeff D
Core FTP Support
http://www.coreftp.com
We'll have to set it up here though and find out if the McAfee firewall is blocking the outgoing connection or the actual SSL command. I'll try and get you an answer very soon. In the meantime, I would check the McAfee web site for more information ( http://forums.mcafeehelp.com ).
Jeff D
Core FTP Support
http://www.coreftp.com
http://forums.mcafeehelp.com/viewtopic.php?t=26024
According to McAfee, XP SP1 has the internal XP firewall turned on by default. In XP SP2, it's turned off.
You can check your internet connection to see if the internal XP firewall is on by going to start, control panel, network connections, choose properties on your internet connection, advanced and make sure the firewall is unchecked. If that doesn't work, install XP SP2 and it should clear up the problem.
Jeff
According to McAfee, XP SP1 has the internal XP firewall turned on by default. In XP SP2, it's turned off.
You can check your internet connection to see if the internal XP firewall is on by going to start, control panel, network connections, choose properties on your internet connection, advanced and make sure the firewall is unchecked. If that doesn't work, install XP SP2 and it should clear up the problem.
Jeff
OK, the files transferred last night, but when I went to do it today, nothing happened. Nothing has happened through out the day. Is this normal? Can they transfer one time and not another? I thought that once they transferred they were in. I installed Microsoft Works and Word last night and that is when they transferred. Is this just a coincidence?
HELP!
Thank you!
Elizabeth
HELP!
Thank you!
Elizabeth

When you disabled the McAffee firewall, could you connect out? I think you have all the Microsoft updates you need but something else must be blocking the outgoing connections. I in the discussion (McAffee link posted above) that there might be a filter that needs to be turned off.
The only option left to try is unchecking OpenSSL and see if there is any difference using WinSSL.
-- Jeff
The only option left to try is unchecking OpenSSL and see if there is any difference using WinSSL.
-- Jeff
I meant connecting outside of your firewall (outside of your computer to another computer/internet).
If the XP firewall is turned off and the McAfee firewall is turned off, something has to be blocking it. If I had to bet on it, I would guess that McAfee firewall is still blocking it somehow or there is something blocking outgoing SSL connections. I say this because we install XP SP1 (w/MS updates) a lot and we don't see this problem here.
I'll run a few tests here and see if I can come up with anything else.
--jeff
If the XP firewall is turned off and the McAfee firewall is turned off, something has to be blocking it. If I had to bet on it, I would guess that McAfee firewall is still blocking it somehow or there is something blocking outgoing SSL connections. I say this because we install XP SP1 (w/MS updates) a lot and we don't see this problem here.
I'll run a few tests here and see if I can come up with anything else.
--jeff
We ran a few tests here (including other ftp clients with no success) and the conclusion is that for whatever reason this server you are trying to connect to has some issues with newer Winsock versions.
You can use the ansi version of Core FTP which should take care of it, it uses earlier versions of winsock. It's in the download section -- look for (ANSI only version).
-- jeff
You can use the ansi version of Core FTP which should take care of it, it uses earlier versions of winsock. It's in the download section -- look for (ANSI only version).
-- jeff
Hi Jeff,
I downloaded the ansi version without any luck.
Again, this is what I get:
UTH SSL
234 SSL enabled and waiting for negotiation
Connect socket #468 to 68.21.158.100, port 1088...
220 outsideserver1.www.oncalltranscription.com X2 WS_FTP Server 4.0.0 (3001274228)
AUTH SSL
234 SSL enabled and waiting for negotiation
I downloaded the ansi version without any luck.

UTH SSL
234 SSL enabled and waiting for negotiation
Connect socket #468 to 68.21.158.100, port 1088...
220 outsideserver1.www.oncalltranscription.com X2 WS_FTP Server 4.0.0 (3001274228)
AUTH SSL
234 SSL enabled and waiting for negotiation
OK, I downloaded the updates. I still can't transfer. I 'quickconnected' and didn't check AUTH SSL and got what appeared to be a couple of files, but could not open them and they didn't say what they were. The above left-hand information was this:
ASV
227 Entering Passive Mode (68,21,158,100,15,92).
LIST
Connect socket #556 to 68.21.158.100, port 3932...
150 Opening ASCII data connection for directory listing
226 transfer complete
Transferred 119 bytes in 0.016 seconds
ASV
227 Entering Passive Mode (68,21,158,100,15,92).
LIST
Connect socket #556 to 68.21.158.100, port 3932...
150 Opening ASCII data connection for directory listing
226 transfer complete
Transferred 119 bytes in 0.016 seconds
This update might provide more information into the problems.
http://support.microsoft.com/default.aspx?kbid=842242
http://support.microsoft.com/default.aspx?kbid=842242