Thanks for the overwhelming responses, summarized as below

How to enable root ftp to solaris 9 server ?

#vi /etc/services - uncomment
-> ftp 21/tcp
#vi /etc/inetd.conf - uncomment
-> ftp stream tcp nowail root /usr/sbin/in.ftpd in.ftpd
# vi /etc/ftpd/ftpuser - to uncomment "root" out
-> # root
#vi /etc/shells - put in all the shell as possible
-> /usr/sbin/ksh
#vi /etc/default/login - to uncomment
-> CONSOLE=/dev/console
check ftp.allow and ftp.deny files as well
#kill -HUP <inetd>pid - to restart #/usr/sbin/inetd -s
A lot of responses suggested using more secure ftp like
proftp/ssh/scp/sftp or normal user to ftp in then #sudo - root
> I have checked out all the related files, and have followed by the book.
However
> no luck. Has someone come across this problem before. Please let me.
The A's:
It may be related to the shells the user accounts are using. If a
user account is setup to use a "non-standard" shell, that shell must be listed
in the /etc/shells file or the login (or ftp connection) will fail. By default,
Solaris doesn't have an /etc/shells file. Instead Bourne shell, C shell, and
a couple of others are permitted. Note root is usually setup to use Borune
shell which is why it would work by default with FTP.
If you need to add additional shells as valid (e.g GNU bash or tsh) you
will need to create an /etc/shells file and include all valid shells in it. The
syntax of the file is to list one shell per line and each shell must be
specified as a full path. For example:
/usr/bin/sh
/usr/bin/csh
/opt/gnu/bin/bash
Also note that once an /etc/shells file has been created, only those shells
which are explicitly listed in it are considered valid by the system.
Another words you have to list all of the regular system shells you want to use
as well as any "non-standard" shells.

If your run nisplus on security level or 2 (=3D=3D> rpc.nisd -S 1 (or 2)) =

then
it means that your user, when loggin, match the password.org_dir file for
but that the credetials do not match. When this occurs, the user is warned
of that on his logging and he cannot use ftp ...
To correct that, log in, then issue the "keylogin" command with the
network passwd, then issue "chkey" command.
Assuming that all of the usual suspects (shell in /etc/shells?) have been
eliminated, does the user, by chance, have a password longer than 8 characters?
I have noticed that the Solaris ftp does not always allow login if you type more
than 8 characters for the password, but allows login if you truncate the
password to 8 characters.