Ipswitch Forums / File Transfer / WS_FTP Server / Cannot connect.... / Latest Posts

RE: Cannot connect....

Brandon Felger — Fri, 10 Sep 2004 11:01:09 GMT

This can also happen if you are trying to use 128-bit encryption using the 40-bit eval (limited due to export restrictions). Try making sure your client isn't trying to force a higher level of encryption than 40-bit.

RE: Cannot connect....

murugesan — Thu, 09 Sep 2004 13:51:17 GMT

I am also not able to connect through WS_FTP Server 5.0.2. I am using GlobalScape FTP Client for SSL and a home grown SSL client and with both, I get the same. I used openssl to create the cert and loaded the root cert in the trusted DB and the leaf in the certificate selection. Any clues?

SSL Negotiated cipher strength 0 cipher name (null)

RE: Cannot connect....

utica — Tue, 03 Aug 2004 12:21:39 GMT

Brandon,

Thanks for the reply. Yes, I created mycert.crt on the Server and added it to the trusted authority DB. Then used mycert.crt to sign the .csr from Pro to create the .crt for Pro and copy and register the new .crt in Pro.

I'm going to try to uninstall and re-install the Server and Pro, then try again.

Forgot to mention that I'll trying this all on one system.....

RE: Cannot connect....

Brandon Felger — Fri, 30 Jul 2004 11:34:47 GMT

Did you add the cert you created under Server (the signing cert, I assume) to the Server's Trusted Authority DB?

Cannot connect....

utica — Fri, 30 Jul 2004 09:56:43 GMT

Using WSFTP Server and WSFTP Pro client. Created new cert for Server, created a csr under Pro, Signed it with Server and added cert to Pro.

With the default evaluation version, I',m able to connect using SSL. With my certs, it goes all the way thru and asks me to sign in on Pro, but then does not connect.

On the Server side, I'm getting an error message on the log viewer stating:

SSL Negotiated cipher strength 0 cipher name (null)

Does anyone understand why this is happening?

Thanks.