Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 830
  • Last Modified:

Fedora Core 3 and vsftpd


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

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@
331 Password required for anonymous@
PASS ****
230 Login successful.
215 UNIX Type: L8
Host type (2): UNIX (standard)
211 End
257 "/"
200 Switching to ASCII mode.
227 Entering Passive Mode (192,168,0,1,12,254).
connecting data channel to
data channel connected to
425 Failed to establish connection.
PORT 192,168,0,50,7,178
200 PORT command successful. Consider using PASV.
150 Here comes the directory listing.
transferred 0 bytes in 65.531 seconds, 0.000 bps ( 0.000 Bps), transfer succeeded.
200 Switching to Binary mode.

  • 5
  • 4
1 Solution
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?
cossy74Author Commented:
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:

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

    Default: NO "

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

cossy74Author Commented:
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 ""
Sun Feb 27 22:53:45 2005 [pid 3727] FTP response: Client "", "220 Welcome to Serck controls FTP Server"
Sun Feb 27 22:53:45 2005 [pid 3727] FTP command: Client "", "USER anonymous"
Sun Feb 27 22:53:45 2005 [pid 3727] [anonymous] FTP response: Client "", "331 Please specify the password."
Sun Feb 27 22:53:45 2005 [pid 3727] [anonymous] FTP command: Client "", "PASS <password>"
Mon Feb 28 09:53:45 2005 [pid 3726] [ftp] OK LOGIN: Client "", anon password "wsftp76@"
Mon Feb 28 09:53:45 2005 [pid 3728] [ftp] FTP response: Client "", "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.
cossy74Author Commented:
Barthax: Hi
when i rang the tali -f /var/log/vsftpd.log and using another terminal i got a client[] blah blah messages comming through the terminal. WHen i went to the winxp client i got client[] blah blah messages coming through the terminal. I therefore asssume i am getting the messages from the winxp machine.
Yeah, you are in that case.  Good that it's ruled out the bindings. :)

OK, on the XP machine try telnetting to the ftp port on the other machine:

telnet <ipaddress> 21

See if you can log in that way.  You'll need to type in the commands in their entirety - just copy what you've seen for the working connection from the vsftp log...

USER anonymous

^^ example.

If your ls gets results this way, then I expect it will be down to the difference in user name - from what you've described, the wsftp client is sending "anonymous@" instead of "anonymous".  It's very likely the two are being treated differently.
cossy74Author Commented:
Barthax: I am giving the point to your. I have worked out the proxy sitting on our Windows Network is causing the problem.
Ah, yeah, that'll be problematic - if your client is redirecting the connection elsewhere first. :)

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now