One of my users has been using CuteFTP with no problem for years. All of the sudden, she started getting an error:
STATUS:> [12/31/2013 11:03:35 AM] Getting listing ""...
STATUS:> [12/31/2013 11:03:35 AM] Resolving host name servername.net...
STATUS:> [12/31/2013 11:03:35 AM] Host name servername.net resolved: ip = *.*.*.*.
STATUS:> [12/31/2013 11:03:35 AM] Connecting to FTP server... servername.net:990 (ip = *.*.*.*)...
STATUS:> [12/31/2013 11:03:35 AM] Socket connected. Waiting for welcome message...
STATUS:> [12/31/2013 11:03:35 AM] Connected. Exchanging encryption keys...
ERROR:> [12/31/2013 11:03:36 AM] SSL: Error in negotiating SSL connection. The server could be rejecting your certificate.
I checked the firewall and didn't see the port 990 listed anywhere:
[root@server ~]# nmap -sV -O 127.0.0.1
Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2013-12-31 10:25 EST
Interesting ports on localhost.localdomain (127.0.0.1):
Not shown: 1668 closed ports
PORT STATE SERVICE VERSION
22/tcp open ssh OpenSSH 4.3 (protocol 2.0)
53/tcp open domain ISC Bind dnsmasq-2.49
80/tcp open http Apache httpd 2.2.3 ((ClearOS))
81/tcp open ssl/http Apache httpd
82/tcp open http Apache httpd
389/tcp open ldap (Anonymous bind OK)
443/tcp open ssl/http Apache httpd 2.2.3 ((ClearOS))
898/tcp open sun-manageconsole?
3128/tcp open http-proxy Squid webproxy 2.6.STABLE21
6000/tcp open X11 (access denied)
8080/tcp open http-proxy DansGuardian HTTP proxy
9999/tcp open abyss?
I haven't made any changes to the firewall and the user has never used or imported any type of certificates in her global settings section of the CuteFTP.
Should I open the port 990 or the problem is caused by something on the server end?
Thanks in advance