CentOS - Jun 2008 - vsftp 553 Could not create file

HI,

  I am facing problem in connecting ftp from the windows client.


CENTOS5U1 Running vsftp daemon. From linux client i am able to upload and
download. When i do an ftp upload of any files or folders from  windows
command line i am getting below error .

*vsftp 553 Could not create file*

*NOTE: SELINUX IS DISABLED AND THERE IS NO FIREWALL RUNNING*

See my user permission and ownership details

User i am using is paps

ll -ld /home/paps/
drwxr-xr-x 2 paps dba 4096 Jun 10 23:09 /home/paps/

My vsftp configuration

cat /etc/vsftpd/vsftpd.conf  |grep -v \#
anonymous_enable=YES
local_enable=YES
write_enable=YES
local_umask=022
dirmessage_enable=YES
xferlog_enable=YES
connect_from_port_20=YES
xferlog_file=/var/log/vsftpd.log
xferlog_std_format=YES
listen=YES

pam_service_name=vsftpd
userlist_enable=YES
tcp_wrappers=YES


Regards

lingu
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos/attachments/20080610/778e650d/attachment-0002.html>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
Hi lingu,
| *vsftp 553 Could not create file***
I think this means you have a file with the same name already there, and 
you don't have permission to replace it.  I connected from Windows to my 
CentOS 5.1 server using the same vsftpd.conf settings, and here's the 
transcript:-

C:\Users\Ian>ftp 192.168.3.2
Connected to 192.168.3.2.
220 (vsFTPd 2.0.5)
User (192.168.3.2:(none)): ian
331 Please specify the password.
Password:
230 Login successful.
ftp> send winscp.RND
200 PORT command successful. Consider using PASV.
150 Ok to send data.
226 File receive OK.
ftp: 600 bytes sent in 0.00Seconds 300.00Kbytes/sec.
ftp> send winscp.RND
200 PORT command successful. Consider using PASV.
150 Ok to send data.
226 File receive OK.
ftp: 600 bytes sent in 0.00Seconds 200.00Kbytes/sec.
ftp> send winscp.RND
200 PORT command successful. Consider using PASV.
553 Could not create file.
ftp>

All worked well until the last send, when I had changed the file 
permissions for winscp.RND from rw-r--r-- to r--r--r--.  This was all 
with iptables and SELinux running at the time.

Hope that helps :)

Ian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
iD8DBQFITkNKLwWMnKQTL2sRAlk9AJ4iCpB2nDNmpUSLW0nbWOHlEdI60QCePtRw
h8nhAQyXZbiNtI+pq3FETiA=m+rf
-----END PGP SIGNATURE-----