Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to
LinuxQuestions.org , a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free.
Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please
contact us . If you need to reset your password,
click here .
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a
virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month.
Click here for more info.
01-20-2014, 05:34 AM
#1
Member
Registered: Jul 2008
Location: Ghent, Belgium
Distribution: Fedora, CentOS
Posts: 690
Rep:
vsftpd server unreachable
Hello,
I have installed the vsftpd ftp-server from yum on my Fedora 19.
But the ftp servive is only reachable on the client itself :
Code:
[root@jonashp ]# tail -f /var/log/vsftpd.log
Mon Jan 20 12:00:21 2014 [pid 5459] FTP response: Client "::ffff:192.168.1.101", "220 (vsFTPd 3.0.2)"
Mon Jan 20 12:00:24 2014 [pid 5459] FTP command: Client "::ffff:192.168.1.101", "USER polycom"
Mon Jan 20 12:00:24 2014 [pid 5459] [polycom] FTP response: Client "::ffff:192.168.1.101", "331 Please specify the password."
Mon Jan 20 12:00:25 2014 [pid 5459] [polycom] FTP command: Client "::ffff:192.168.1.101", "PASS <password>"
Mon Jan 20 12:00:25 2014 [pid 5458] [polycom] OK LOGIN: Client "::ffff:192.168.1.101"
Mon Jan 20 12:00:25 2014 [pid 5460] [polycom] FTP response: Client "::ffff:192.168.1.101", "230 Login successful."
Mon Jan 20 12:00:25 2014 [pid 5460] [polycom] FTP command: Client "::ffff:192.168.1.101", "SYST"
Mon Jan 20 12:00:25 2014 [pid 5460] [polycom] FTP response: Client "::ffff:192.168.1.101", "215 UNIX Type: L8"
Mon Jan 20 12:00:44 2014 [pid 5460] [polycom] FTP command: Client "::ffff:192.168.1.101", "QUIT"
Mon Jan 20 12:00:44 2014 [pid 5460] [polycom] FTP response: Client "::ffff:192.168.1.101", "221 Goodbye."
When I try to log on from another FTP-client in the same network, it does not work.
IPtables is stopped :
Code:
[root@jonashp ]# /sbin/service iptables status
Redirecting to /bin/systemctl status iptables.service
iptables.service - IPv4 firewall with iptables
Loaded: loaded (/usr/lib/systemd/system/iptables.service; disabled)
Active: inactive (dead)
nov 17 14:02:16 jonashp.jocan.local systemd[1]: Stopped IPv4 firewall with iptables.
SElinux is also disabled :
Code:
[root@jonashp ]# cat /etc/sysconfig/selinux
SELINUX=disabled
SELINUXTYPE=targeted
What am I missing ?
01-20-2014, 06:02 AM
#2
Member
Registered: Jul 2013
Posts: 213
Rep:
how do you know it is not working from another client?
01-20-2014, 06:13 AM
#3
Member
Registered: Jul 2008
Location: Ghent, Belgium
Distribution: Fedora, CentOS
Posts: 690
Original Poster
Rep:
I tried connecting from another pc and with my smartphone with a simple ftp client. Used the same user and password. There is no connection, and there is nothing logged in the ftp logfiles.
01-20-2014, 06:39 AM
#4
Member
Registered: Jul 2013
Posts: 213
Rep:
Quote:
Originally Posted by
jonaskellens
I tried connecting from another pc and with my smartphone with a simple ftp client. Used the same user and password. There is no connection, and there is nothing logged in the ftp logfiles.
please try to telnet on port no 23.
01-20-2014, 06:49 AM
#5
Member
Registered: Jul 2008
Location: Ghent, Belgium
Distribution: Fedora, CentOS
Posts: 690
Original Poster
Rep:
Hello,
It does not work. There is no connection at all.
Telnet client says : connecting to 192.168.1.101:23...
And it stays that way.
EDIT : seems I can not even ping to this host.
But there is no firewall or selinux on this host ??
Last edited by jonaskellens; 01-20-2014 at 06:56 AM .
01-20-2014, 07:17 AM
#6
Member
Registered: Jul 2008
Location: Ghent, Belgium
Distribution: Fedora, CentOS
Posts: 690
Original Poster
Rep:
Firewall completely off :
Code:
[root@jonashp ]# systemctl status firewalld.service
firewalld.service - firewalld - dynamic firewall daemon
Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled)
Active: inactive (dead) since ma 2014-01-20 14:08:32 CET; 1min 46s ago
Main PID: 639 (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/firewalld.service
jan 20 08:40:37 jonashp.jocan.local systemd[1]: Started firewalld - dynamic firewall daemon.
jan 20 14:08:31 jonashp.jocan.local systemd[1]: Stopping firewalld - dynamic firewall daemon...
jan 20 14:08:32 jonashp.jocan.local systemd[1]: Stopped firewalld - dynamic firewall daemon.
jan 20 14:10:15 jonashp.jocan.local systemd[1]: Stopped firewalld - dynamic firewall daemon.
[root@jonashp ]# systemctl status iptables.service
iptables.service - IPv4 firewall with iptables
Loaded: loaded (/usr/lib/systemd/system/iptables.service; disabled)
Active: inactive (dead)
nov 17 14:02:16 jonashp.jocan.local systemd[1]: Stopped IPv4 firewall with iptables.
jan 20 13:46:27 jonashp.jocan.local systemd[1]: Stopped IPv4 firewall with iptables.
jan 20 14:10:34 jonashp.jocan.local systemd[1]: Stopped IPv4 firewall with iptables.
[root@jonashp ]# systemctl stop ip6tables.service
[root@jonashp ]# systemctl status ip6tables.service
ip6tables.service - IPv6 firewall with ip6tables
Loaded: loaded (/usr/lib/systemd/system/ip6tables.service; disabled)
Active: inactive (dead)
jan 20 13:57:52 jonashp.jocan.local systemd[1]: Stopped IPv6 firewall with ip6tables.
jan 20 14:10:51 jonashp.jocan.local systemd[1]: Stopped IPv6 firewall with ip6tables.
[root@jonashp ]# firewall-cmd --state
not running
But can not even ping this host.
But I can post this message to this forum from this host.
01-20-2014, 07:50 AM
#7
LQ Newbie
Registered: Jan 2014
Location: Sweden
Distribution: Ubuntu / Linux mint / SUN / Debian
Posts: 10
Rep:
It could be a routing problem in your switches / routers, what is your network connection between the clients you are trying with?
01-20-2014, 07:52 AM
#8
Member
Registered: Jul 2013
Posts: 213
Rep:
First you will have to ping ftp server from client. only then try to access ftp from that client.
01-20-2014, 08:02 AM
#9
Member
Registered: Jul 2008
Location: Ghent, Belgium
Distribution: Fedora, CentOS
Posts: 690
Original Poster
Rep:
Sometimes I can ping the client, and then 10 seconds later I can no longer ping the client.
I have now switched to LAN in stead of WLAN on my Fedora 19, and now it seems I have more stability in ping and ftp logon results !
Problem thus is situated in the WLAN of Fedora 19.
01-20-2014, 08:04 AM
#10
Member
Registered: Jul 2013
Posts: 213
Rep:
Quote:
Originally Posted by
jonaskellens
Sometimes I can ping the client, and then 10 seconds later I can no longer ping the client.
I have now switched to LAN in stead of WLAN on my Fedora 19, and now it seems I have more stability in ping and ftp logon results !
Problem thus is situated in the WLAN of Fedora 19.
Now are you able to use ftp from client in LAN?
01-20-2014, 08:26 AM
#11
Senior Member
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979
Rep:
Hi,
you could use nmap and find out if the port for sftp is open:
Code:
nmap -p 115 192.168.1.101
should give you an answer. You can also scan all (wellknown) Ports with
Code:
nmap -sV 192.168.1.101
to check the server for open ports. Note that you can use the commands from both, server or client.
Markus
01-20-2014, 08:28 AM
#12
Member
Registered: Jul 2008
Location: Ghent, Belgium
Distribution: Fedora, CentOS
Posts: 690
Original Poster
Rep:
Quote:
Originally Posted by
sachin.davra
Now are you able to use ftp from client in LAN?
Yes, I can ping and use ftp.
Sometimes it still fails and then I switch from LAN to WLAN or from WLAN to LAN, and then it work again for some time.
I guess Fedora 19 is not very stable...
01-21-2014, 12:52 AM
#13
Member
Registered: Jul 2013
Posts: 213
Rep:
Quote:
Originally Posted by
jonaskellens
Yes, I can ping and use ftp.
Sometimes it still fails and then I switch from LAN to WLAN or from WLAN to LAN, and then it work again for some time.
I guess Fedora 19 is not very stable...
when you are not able to connect via ftp, try to ping server. if you are able to ping then you should be able to connect through ftp, if not then first you will have to troubleshoot ping problem.
01-21-2014, 02:10 AM
#14
Member
Registered: Aug 2009
Location: Bangaluru, India
Distribution: CentOS 6.5, SuSE SLED/ SLES 10.2 SP2 /11.2, Fedora 11/16
Posts: 665
Rep:
well i watched it all over and saw every time you wrote its not even pinging or not able to use ftp while it was before, did you checked the logs to see what they says about it ?
All times are GMT -5. The time now is 08:28 PM .
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know .
Latest Threads
LQ News