[SOLVED] running vsftpd on a different port other than default 21? unable to get it working?

cyberdome · 04-07-2014, 09:49 PM

Quote:

Originally Posted by michaelk

As unSpawn noticed the server appears to be only listening on ipv6. However according to the documentation it should listen on both since listen_ipv6=YES option is enabled.

However I just checked and with IPV6 enabled I could not connect from a remote PC. So try disabling listen_ipv6 and enable ipv4 i.e. listen=yes.

I did change the

Code:

Listen=NO  to Listen=YES,   also, I uncommented the listen_ipv6=YES.

after making the change I restarted

Code:

systemctl restart vsftpd.service.

for some reason, I am still unable to connect from my windows machine. changing to ipv4 should have worked. But, when I change back to default port 21, it works fine using the LAN IP 192.168.1.2.

Code:

netstat -pnl | grep vsftpd
tcp        0      0 0.0.0.0:1980            0.0.0.0:*               LISTEN      20934/vsftpd

Code:

iptables -L

Chain IN_public_allow (1 references)
target     prot opt source               destination         
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:ftp ctstate NEW
ACCEPT     udp  --  anywhere             224.0.0.251          udp dpt:mdns ctstate NEW
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:http ctstate NEW
ACCEPT     tcp  --  anywhere             anywhere             tcp dpts:rfb:5903 ctstate NEW
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:smtp ctstate NEW
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:https ctstate NEW
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:mysql ctstate NEW
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:urd ctstate NEW
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:p2pq ctstate NEW
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:submission ctstate NEW
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:estamp ctstate NEW
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:pearldoc-xact ctstate NEW

cyberdome · 04-08-2014, 05:06 AM

I was able to connect on my windows machine using FTP via port 1980 using IP local LAN IP. On the FileZilla Cleint I had to choose ACTIVE mode instead of PASSIVE mode. Choosing ACTIVE mode works perfectly with the LAN IP on port 1980.

But when I try the same above settings using hostname/domain name. for example, mydomainname.com , It does not work.

I get error message,

Quote:

could not retrieve directory listing

illegal port command.

kirukan · 04-08-2014, 09:54 PM

Can you resolve the IP for your domainname from your windows PC?

Quote:

nslookup mydomainname.com

check this is return the FTP server LAN IP.

cyberdome · 04-09-2014, 05:32 AM

nslookup in my windows machine shows my google DNS and my WAN IP.

cyberdome · 04-09-2014, 01:57 PM

Thanks to everyone for posting and for all the help. Apparently, the port I was using was already assigned by IANA. my mistake. Just change the port to a very high number that is uassigned. I have actually using port that was already assigned. Now everything works using LAN IP and WAN IP. thanks for the reply.

http://www.adminsub.net/tcp-udp-port-finder/