ftp connection failed

[WilliamSmith11]

HI
I have a custumer that seam to be that is experimenting a lot with the os.

Is calling because the ftp have stopped to work.

This the error that is sending .

# ftp 192.168.20.100
Connected to 192.168.20.100
220 Boston1 FTP server (Revision 1.1 Version wuftpd-2.6.1 Fri Jun 25 02:33:48 G
MT 2004) ready.
Name (192.168.20.100:root): root
331 Password required for root.
Password:
530 Login incorrect.
Login failed.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp>

The password is correct .

I can do rlogin from and to this machine.
I can do a telnet from and to this machine.

some idea about what is going on .

The customer say that he have not done any ,
That was working and that stop to work .

Thank

W.S

[A. Clay Stephenson]

The first thing that I would do is check the ftpaccess file on the remote machine. It's probably pretty dumb anyway to allow root to ftp.

If you are using a Microsoft ftp client then
there is a feature of which you should be aware. If the password contains a leading "-" the the ftp client "eats" the first "-" so that if the password were "-topsecret" you would actually enter "--topsecret".

[WilliamSmith11]

# cd /etc/ftpd
# ls
ftp-exec pids

There is not ftpaccess

W.S

[A. Clay Stephenson · Accepted solution]

Okay, it's also clear that you don't have an ftpusers file so that doesn't seem to be getting you. By any chance, has anyone changed root's shell to something other than /sbin/sh?

[Tom Ward_1]

Check for /etc/ftpaccess. I ran into the same thing the other day with a host that had moved to a new subnet. The new subnet had to be added before logins would work. Connections were okay, but logins failed until the subnet was added. The wu_ftp page was a big help.
http://www.wu-ftpd.org/

[WilliamSmith11]

Yes I check and the shell is

/sbin/sh

[A. Clay Stephenson]

What does the ftp line in /etc/inetd.conf look like. We need to find out what options ftpd is launched with.

[WilliamSmith11]

A.Clay

Thank you .

user change the shell after that I gave the machine.

[A. Clay Stephenson]

I have a feeling this is a bash fan. Tell your user to immediately change root's back shell to /sbin/sh. /sbin/sh is a full-blown POSIX shell and is every bit as powerful as /usr/bin/sh. The difference is that /sbin/sh like all the executables in /sbin is a statically linked version and /usr/bin/sh (ksh,bash, etal) are dynamically linked versions. /sbin/sh can execute before /usr is mounted to make shared libraries available. Have your user consider what will happen on a boot when /usr is not yet available.