Can't connect to local network ftp server

[TheBlueKingLP]

Can't connect to local network ftp server

- the port is open

- vsftpd service is running

- the ip i connecting is listed in "ifconfig"

but the ftp client FileZilla can't connect to the server

please help

[Remix]

What IP is the FTP server binding to within VSFTPD?

[TheBlueKingLP]

1 minute ago, Remix said:

What IP is the FTP server binding to within VSFTPD?

0.0.0.0

[Remix]

2 minutes ago, TheBlueKingLP said:

0.0.0.0

Can you confirm it's being bound to the correct port?

 

netstat --proto=inet,inet6 --pnl | grep ":21"

netstat --proto=inet,inet6 --pnl | grep ":21"

 

[TheBlueKingLP]

2 minutes ago, Remix said:

Can you confirm it's being bound to the correct port?

 

netstat --proto=inet,inet6 --pnl | grep ":21"

netstat --proto=inet,inet6 --pnl | grep ":21"

 

it give me this error

netstat: unrecognized option '--pnl'
usage: netstat [-vWeenNcCF] [<Af>] -r         netstat {-V|--version|-h|--help}
       netstat [-vWnNcaeol] [<Socket> ...]
       netstat { [-vWeenNac] -I[<Iface>] | [-veenNac] -i | [-cnNe] -M | -s [-6tuw] } [delay]

        -r, --route              display routing table
        -I, --interfaces=<Iface> display interface table for <Iface>
        -i, --interfaces         display interface table
        -g, --groups             display multicast group memberships
        -s, --statistics         display networking statistics (like SNMP)
        -M, --masquerade         display masqueraded connections

        -v, --verbose            be verbose
        -W, --wide               don't truncate IP addresses
        -n, --numeric            don't resolve names
        --numeric-hosts          don't resolve host names
        --numeric-ports          don't resolve port names
        --numeric-users          don't resolve user names
        -N, --symbolic           resolve hardware names
        -e, --extend             display other/more information
        -p, --programs           display PID/Program name for sockets
        -o, --timers             display timers
        -c, --continuous         continuous listing

        -l, --listening          display listening server sockets
        -a, --all                display all sockets (default: connected)
        -F, --fib                display Forwarding Information Base (default)
        -C, --cache              display routing cache instead of FIB
        -Z, --context            display SELinux security context for sockets

  <Socket>={-t|--tcp} {-u|--udp} {-U|--udplite} {-w|--raw} {-x|--unix}
           --ax25 --ipx --netrom
  <AF>=Use '-6|-4' or '-A <af>' or '--<af>'; default: inet
  List of possible address families (which support routing):
    inet (DARPA Internet) inet6 (IPv6) ax25 (AMPR AX.25)
    netrom (AMPR NET/ROM) ipx (Novell IPX) ddp (Appletalk DDP)
    x25 (CCITT X.25)

[Electronics Wizardy]

14 minutes ago, TheBlueKingLP said:

Can't connect to local network ftp server

- the port is open

- vsftpd service is running

- the ip i connecting is listed in "ifconfig"

but the ftp client FileZilla can't connect to the server

please help

If this is local, don't use ftp, use samba or nfs or iscsi

[TheBlueKingLP]

7 minutes ago, Electronics Wizardy said:

If this is local, don't use ftp, use samba or nfs or iscsi

why?

[Electronics Wizardy]

1 minute ago, TheBlueKingLP said:

why?

much faster and it works like a internal drive, so you can install programs on there like any other drive. Its a much better way to use network storage.

 

FTP should only be used for WAN's as its optimized for high latency networks.

[TheBlueKingLP]

1 minute ago, Electronics Wizardy said:

much faster and it works like a internal drive, so you can install programs on there like any other drive. Its a much better way to use network storage.

 

FTP should only be used for WAN's as its optimized for high latency networks.

but i can use ftp anywhere,so i still want to use ftp

[tt2468]

On 1/6/2017 at 7:43 PM, TheBlueKingLP said:

but i can use ftp anywhere,so i still want to use ftp

Your server. Just remember that the experience will not be as fun as with smb or nfs.

 

Try binding the server to the specific ip you are using. Also confirm that the host is not running any firewalls.