The Solaris group is a forum where peers share technical expertise, solve problems, and discuss issues related to the Solaris operating system, including OS-related malfunctions, security issues, and network performance.

Not sure how to do it for "su" , but you can use secure shell and just
generate keys for root user and paste it in the ~/.ssh directory of the
target server
this way the root can use ssh w/o a password. This will surely work..

You didnt indicate if you are doing this within the same subnet or not. If
you are doing it from another UNIX box or not (I beleive from linux you
have to turn it on first in some cases)
First
ping the host name if no answer
ping the ip address of the host name if no answer
ping the router (usually same ip except last octet is 1)
if you can see the host you are hitting, make sure that those services are
turned on and active.

try ftp and telnet the ipaddress not the host name. if this works you have
a name service problem. Temp fix is to put the target in your local host
file

su is designed (for security purposes) to require a password when you
change users. The only exception if you are root and change to another
user. Then no password is required, except if you are root on another
machine...

and why not...well, let someone sit in the parking lot outside the
building with a wireless connection, or let me sit down at a conferance
table that is hard wired. He boots linux as root on HIS personal laptop
and now have complete and total control of ever damn server on your
network, and you would have no idea. One could easily copy all your
companies financial and marketing data. One could set rouge programs to
destroy the company

From a security standpoint what you are trying to do is the equivilant to
setting all users with no password, and no ability to change the password.
That would only serve a virus writer or kiddy hacker wanting to move up
from exploiting windows to exploiting UNIX. Or someone wishing to leave a
backdoor to a system the size of a barn door.

Someone mentioned SSH. There is a good alternative. Where the
administrator is using keys instead of passwords. That way the admin
controls who can get around without a password. But you have not
eliminated security, you just changed from passwords to keys. Now you can
write scripts, as a trusted admin, and not run into password issue.

First of all YOU CAN use su - to change to root without a password. Secondly, he doesn't need to give a justification. It's his system, let him do what he wants with it. If he toasts his box, that's his problem. I am sick of going to these forums and listening to parrots patronising people about security instead of providing them the answer that they need.