Link to home
Create AccountLog in
Avatar of cossy74
cossy74

asked on

Fedora Core 3 and vsftpd

Hi,

i have set up the vsftpd service on the fedora core 3 giving anonymous user access rights

i can type >ftp localhost
give userid >anonymous
give pwd   > 

type  >ls
and i get a directory listing


Problem:
on a winxp machine i am trying tp use wsftppro and i cannot get a listing( there should be a file shown.
 
here what i get in the event box at bottom of wsftppro

USER anonymous@192.168.2.2
331 Password required for anonymous@192.168.2.2
PASS ****
230 Login successful.
SYST
215 UNIX Type: L8
Host type (2): UNIX (standard)
FEAT
211-Features:
 EPRT
 EPSV
 MDTM
 PASV
 REST STREAM
 SIZE
 TVFS
211 End
PWD
257 "/"
TYPE A
200 Switching to ASCII mode.
PASV
227 Entering Passive Mode (192,168,0,1,12,254).
connecting data channel to 192.168.0.1:3326
data channel connected to 192.168.0.1:3326
LIST
425 Failed to establish connection.
PORT 192,168,0,50,7,178
200 PORT command successful. Consider using PASV.
LIST
150 Here comes the directory listing.
transferred 0 bytes in 65.531 seconds, 0.000 bps ( 0.000 Bps), transfer succeeded.
TYPE I
200 Switching to Binary mode.
PASV



Avatar of Barthax
Barthax
Flag of United Kingdom of Great Britain and Northern Ireland image

It sounds like vsftpd is configured to only bind to localhost and you have some other ftp daemon running on the lan device.  Can you confirm that the vsftpd logs are showing the connections from the XP machine?
Avatar of cossy74
cossy74

ASKER

Barthax: THe log file vsftpd.log in the var/logs directory is blank(empty) am i looking in the wrong place?
Again that depends on the configuration of vsftpd - the configuration may be set to no logging.  From the man page, the default is not to log:

"log_ftp_protocol
    When enabled, all FTP requests and responses are logged, providing the option xferlog_std_format is not enabled. Useful for debugging.

    Default: NO "

http://vsftpd.beasts.org/vsftpd_conf.html
Avatar of cossy74

ASKER

Barthax: Here is an extract from the vsftpsd.log file. I assume that the connection is ok.

Mon Feb 28 09:53:45 2005 [pid 3727] CONNECT: Client "192.168.1.2"
Sun Feb 27 22:53:45 2005 [pid 3727] FTP response: Client "192.168.1.2", "220 Welcome to Serck controls FTP Server"
Sun Feb 27 22:53:45 2005 [pid 3727] FTP command: Client "192.168.1.2", "USER anonymous"
Sun Feb 27 22:53:45 2005 [pid 3727] [anonymous] FTP response: Client "192.168.1.2", "331 Please specify the password."
Sun Feb 27 22:53:45 2005 [pid 3727] [anonymous] FTP command: Client "192.168.1.2", "PASS <password>"
Mon Feb 28 09:53:45 2005 [pid 3726] [ftp] OK LOGIN: Client "192.168.1.2", anon password "wsftp76@"
Mon Feb 28 09:53:45 2005 [pid 3728] [ftp] FTP response: Client "192.168.1.2", "230 Login successful."
OK, I'm a little confused over which machine has which IP address, but I'm fairly certain that the log you're showing is only (from what I can see) showing the connection from the localhost.  Get a terminal up on the linux box with "tail -f /var/log/vsftpsd.log" (presuming I've got the correct path) running.  Now make a connection from localhost using a different terminal - you'll see the connection come through the log.  Attempt the same from the XP machine - see if you get the connection in the log at all.
Avatar of cossy74

ASKER

Barthax: Hi
when i rang the tali -f /var/log/vsftpd.log and using another terminal i got a client[127.0.0.1] blah blah messages comming through the terminal. WHen i went to the winxp client i got client[192.168.1.2] blah blah messages coming through the terminal. I therefore asssume i am getting the messages from the winxp machine.
ASKER CERTIFIED SOLUTION
Avatar of Barthax
Barthax
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
Avatar of cossy74

ASKER

Barthax: I am giving the point to your. I have worked out the proxy sitting on our Windows Network is causing the problem.
Thanks
Ah, yeah, that'll be problematic - if your client is redirecting the connection elsewhere first. :)