ftp can not work

cwygl · 07-11-2007, 03:57 AM

hi, how are you

1, My ftp can not work, I check the vsftpd.conf, add ftp_username item, nothing changed. Also I check the service from the Desktop -> Management -> Service, ftp service is on, but netstat -a | grep ftp showed nothing, I tried to manually start vsftpd but failed

The following is on the debian console.
deb-bj:/etc/init.d# vsftpd start
500 OOPS: vsftpd: cannot open config file:start
deb-bj:/etc/init.d# vsftpd restart
500 OOPS: vsftpd: cannot open config file:restart

2, I know under redhat I can use "mount //10.56.0.158/share /mnt -o username= password= " to share a directory between windows OS and linux OS, but under debian the following information appeared

deb-bj:/etc/init.d# mount //10.56,0.158/share /mnt
mount: wrong fs type, bad option, bad superblock on //10.56,0.158/share,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

deb-bj:/etc/init.d#

what can I do

thanks a lot

best

lord-fu · 07-11-2007, 09:25 AM

Hello, you are seeing two separate errors unrelated to each other.

First, is there under /etc/init.d a file even name vsftpd?

Secondly, try putting a file system type on your mount command. When I mount windows shares I use cifs.

Code:

mount -t cifs //hostname/share /mnt/mountpoint -o optionshere

Hope it helps some.

cwygl · 07-12-2007, 03:45 AM

thanks for reply

1， deb-bj:~# find /etc/init.d/ -name "v*"
/etc/init.d/vbesave
/etc/init.d/vsftpd.conf
/etc/init.d/vsftpd

2，
deb-bj:~# mount -t cifs //10.56.0.158/software /mnt/test
mount: wrong fs type, bad option, bad superblock on //10.56.0.158/software,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

deb-bj:~# dmesg |tail
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
mtrr: your processor doesn't support write-combining
eth1: no IPv6 routers present
CIFS VFS: cifs_mount failed w/return code = -22
CIFS VFS: cifs_mount failed w/return code = -22
CIFS VFS: cifs_mount failed w/return code = -22

deb-bj:~# apt-cache search cifs
libjcifs-java - java library for the CIFS/SMB networking protocol
libjcifs-java-doc - Documentation for libjcifs-java (CIFS/SMB library for java)
smbget - Downloader for the SMB/CIFS protocol
xsmbrowser - X11 tool for navigating SMB Networks
libpam-smbpass - pluggable authentication module for SMB/CIFS password database
libsmbclient - shared library that allows applications to talk to SMB/CIFS servers
libsmbclient-dev - libsmbclient static libraries and headers
samba - a LanManager-like file and printer server for Unix
samba-common - Samba common files used by both the server and the client
samba-dbg - Samba debugging symbols
samba-doc - Samba documentation
samba-doc-pdf - Samba documentation (PDF format)
smbclient - a LanManager-like simple client for Unix
smbfs - mount and umount commands for the smbfs (for kernels >= than 2.2.x)
swat - Samba Web Administration Tool

lord-fu · 07-13-2007, 03:40 PM

Hello,

Try the mount command with smbfs.

Code:

mount -t smbfs //10.56.0.158/software /mnt/test

As well try full path to the vsftpd file and see if that works.

Code:

/etc/init.d/vsftpd start

Hope it helps some.

cwygl · 07-16-2007, 12:13 AM

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
deb-bj:~# mount -t smbfs //10.56.0.158/software /mnt/test
mount: wrong fs type, bad option, bad superblock on //10.56.0.158/software,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

deb-bj:~# mount -t smbfs //192.168.244.1/software /mnt/test
mount: wrong fs type, bad option, bad superblock on //192.168.244.1/software,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

deb-bj:/dev# dmesg | tail
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
mtrr: your processor doesn't support write-combining
eth1: no IPv6 routers present
smb_fill_super: missing data argument
smb_fill_super: missing data argument

the same error information, I wonder if debian can not support such sharing method

I just /etc/init.d/vsftpd start but failed, but under /etc/init.d I run /etc/init.d/vsftpd start succeed, why , what is the difference, because I have alread added the /etc/init.d to PATH

deb-bj:/etc/init.d# echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/etc/init.d/
deb-bj:/etc/init.d# vsftpd start
500 OOPS: vsftpd: cannot open config file:start
deb-bj:/etc/init.d#

last, even "Starting FTP server: vsftpd.", but when I use ftp, always connection refused, all the relative configuration in vsftpd.conf were made ...

Wim Sturkenboom · 07-16-2007, 01:46 AM

No clou about the smaba part. With regards to vsftpd:

Code:

vsftpd start

This will probably run the real vsftp executable that is located in one of the other directories (on my slackware system it's in /usr/sbin). The executable interpretes 'start' as the name of a config file

Code:

# executed from a random directory
/etc/init.d/vsftpd start

Which error message? It will probably not be able to find a config file as that's located in /etc/init.d (and PATH only applies to 'executables'.

Code:

# executed from /etc/init.d
/etc/init.d/vsftpd start

That works if I understand you correctly, but you get 'connection refused'. If so, tcp_wrappers or firewall rules might block your connection.

What are the commands that you use to connect? Have you tried ftp localhost?

You can post the contents of /etc/hosts.allow and /etc/hosts.deny as well as the output of iptables -L -n (needs root privileges).

PS Is it normal to have /etc/init.d in the PATH on a debian system?

cwygl · 07-24-2007, 09:27 PM

went out on business for serveral days, just saw it,thanks a lot, as you can see, ftp itself cannot be done, just refused

deb-bj:/etc# ftp 10.56.0.177
ftp: connect: Connection refused
ftp> bye
deb-bj:/etc# iptables -L -n
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

*******************
deb-bj:/etc# ifconfig
eth1 Link encap:Ethernet HWaddr 00:0C:29:82:C8:39
inet addr:10.56.0.177 Bcast:10.56.0.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fe82:c839/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:638 errors:0 dropped:0 overruns:0 frame:0
TX packets:397 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:66646 (65.0 KiB) TX bytes:48946 (47.7 KiB)
Interrupt:177 Base address:0x1400

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:760 (760.0 b) TX bytes:760 (760.0 b)

********************

deb-bj:/etc# cat hosts.allow
# /etc/hosts.allow: list of hosts that are allowed to access the system.
# See the manual pages hosts_access(5), hosts_options(5)
# and /usr/doc/netbase/portmapper.txt.gz
#
# Example: ALL: LOCAL @some_netgroup
# ALL: .foobar.edu EXCEPT terminalserver.foobar.edu
#
# If you're going to protect the portmapper use the name "portmap" for the
# daemon name. Remember that you can only use the keyword "ALL" and IP
# addresses (NOT host or domain names) for the portmapper, as well as for
# rpc.mountd (the NFS mount daemon). See portmap(8), rpc.mountd(8) and
# /usr/share/doc/portmap/portmapper.txt.gz for further information.
#
all:10.56.0

deb-bj:/etc# cat hosts.deny
# /etc/hosts.deny: list of hosts that are _not_ allowed to access the system.
# See the manual pages hosts_access(5), hosts_options(5)
# and /usr/doc/netbase/portmapper.txt.gz
#
# Example: ALL: some.host.name, .some.domain
# ALL EXCEPT in.fingerd: other.host.name, .other.domain
#
# If you're going to protect the portmapper use the name "portmap" for the
# daemon name. Remember that you can only use the keyword "ALL" and IP
# addresses (NOT host or domain names) for the portmapper. See portmap(8)
# and /usr/doc/portmap/portmapper.txt.gz for further information.
#
# The PARANOID wildcard matches any host whose name does not match its
# address.

# You may wish to enable this to ensure any programs that don't
# validate looked up hostnames still leave understandable logs. In past
# versions of Debian this has been the default.
# ALL: PARANOID

**********************
deb-bj:/usr/sbin# inetd restart

deb-bj:/etc# chmod u+x networks
deb-bj:/etc# /etc/networks restart
/etc/networks: line 1: default: command not found
/etc/networks: line 2: loopback: command not found
/etc/networks: line 3: link-local: command not found
/etc/networks: line 4: localnet: command not found
deb-bj:/etc# cat networks
default 0.0.0.0
loopback 127.0.0.0
link-local 169.254.0.0
localnet 10.56.0.0
deb-bj:/etc#