1832780 Members
3027 Online
110045 Solutions
New Discussion

configuring network

 
Pierre_6
Occasional Contributor

configuring network

Hello Linux community,

I installed redhat 7.2 and got the same Problem like many others with the telnet connection which didn't work, but I installed then inetd rpm and the telnet was working.
Well just to say how I got running telnet... but, know my question.
When I telnet to my server I can only login with my user and then su to root, o.k it works but is this the normal way?
And I am not able to configuring see my lansetings, like with lanscan or linuxconf or ifconfig, all these commands he say command not found.
thks for help,
cya Pierre

3 REPLIES 3
oiram
Regular Advisor

Re: configuring network

Hi,

For the login question see man securetty.
For the comand question I think it should be a problem with the PATH variable. If you want to execute a command like ifconfig first you should know where it is:
find / -name ifconfig
after that add the path of the command to your PATH variable
export PATH=$PATH:/directory_ifconfig
after that you can execute it without typing the full path of the command.

Regards.
Nico van Royen
Frequent Advisor

Re: configuring network

Default root is not allowed to login via network (only console).. thats for security.
If you do want to have root be able to login, edit, or move your /etc/securetty file. That file hold the tty ports that should is allowed to login.

As root you should be able to start the ifconfig programs (not lanscan, this is not default on redhat 7.2, it is on HP-UX etc).. if not, add the path to your default path (ifconfig should be in /sbin).

If you don't know where a particular program is, you can try to find them on any of these methods:
root# whereis program_name
root# which program_name
root# find / -name program_name


If all else fails, try reading the manual...
Jeffrey Wong
Advisor

Re: configuring network

The main reason why administrative commands do not show up if you use su to gain root access is that, by default, su retains the enviroment settings of the initial login. Since the administrative commands are normally located in /sbin and /usr/sbin, which are not generally in the standard users path, these commands won't work without explicitly stating the path to it. If you use 'su -l' then su will open a full login shell with the enviroment settings of the account you are switching to.