Hello-

I'm new at linux. I just put it on a computer at work. I'd like to be able to telnet into the linux box. I have the network card working, I'm using redhat 6.2, and I can open a telnet session with the localhost. I think that there must be a file somewhere that you must be able to edit it to allow in different IP addresses. What do I need to do to make this work? Let me know.

Thanks-
Todd

Hey there
you should be able to Telnet to your Linux Box per deafault.

what you have to do is:
1 : add a new user
2 : give the user a password
then you should be able to telnet to you Linux box using that username and password

Perhaps it could be a network problem too.
see. you ip adress might look like this 192.10.0.23 (class C network)
so you have to be shure that all the computers have an Ip Adress within the same Ip range
furthermore they allso have to be on the same submask adress to talk over network
confussed???? I hope not (and sory my english is a bit rusty)

regards Torp

Hey there
you should be able to Telnet to your Linux Box per deafault.

what you have to do is:
1 : add a new user
2 : give the user a password
then you should be able to telnet to you Linux box using that username and password

Perhaps it could be a network problem too.
see. you ip adress might look like this 192.10.0.23 (class C network)
so you have to be shure that all the computers have an Ip Adress within the same Ip range
furthermore they allso have to be on the same submask adress to talk over network
confussed???? I hope not (and sory if my english is a bit rusty)

regards Torp

Hello Torp-

Those are good suggestions. Here's more info:
The linux box has a static ip of 10.100.1.127 with a subnet mask of 255.255.255.0, other computers on the network user dhcp and have an ip range of 10.100.1.2-10.100.1.252. The scope of 10.100.1.100-10.100.1.130 is reserved in our dhcp server as out of range.

I have a new user added. When I try to telnet to the linux box it says that the destination host is unreachable. I can ping the linux box from other computers on our network. The linux box can also see external web pages.

Using the KDE interface's kpackage, I added telnet server from the redhat linux 6.2 CD. I got and error message asking me to add another package before telnet server would install, so I did that and then loaded telnet server.

I tried rebooting and logging in as root because those things sometimes help in the nt world =) Let me know if you know of anything else to try.

thanks-
todd

Hello-

Don't worry about posting any suggestions to this reply. I got it figured out. I had to find a used book on linux commands to get it to work. I was using the wrong syntax to open the telnet session at the command prompt. Thanks to all who offered help.

-Todd

Glad you got everything working! For the sake of others who may make the same mistake - what were you typing? BTW the files that allow you to allow/deny requests by IP are /etc/hosts.deny and /etc/hosts.allow.

The wrong syntax I was using:

telnet open 10.100.1.127

What it should have been:

telnet 10.100.1.127

-todd

Hello-

I have another question. The reason that I want to telnet into this linux box is because it is at work. I want to be able to run command line queries from a telnet session at home because I'm trying to get better at security issues. In any case, here's what I'm running into.

When I try to run some commands like traceroute from the command line:

traceroute yahoo.com

it returns:
bash: traceroute: command not found

so then I change directories:

cd /usr/sbin/
./traceroute yahoo.com

when I do this linux know where the file is and traceroute works fine.

What I think that I need to do is to set a Path= statement into a file because the commands I need are in /usr/sbin and /usr/bin.

What file do I need to edit? What is the exact syntax that I need to use?

One more question, what's everybody's favorite place for documentation on linux?

Thanks-
Todd

The syntax for adding to your path depends on the shell you use. If you let me know your shell I'll post the proper syntax.

As for the last question, who needs docs when you have LinuxQuestions.org??

True, this site is a very good resource!

I feel like a newbie here. By shell I hope that you mean what flavor of linux am I running. If that's the case I'm using redhat 6.2 workstation with the KDE gui.

Let me know if you need more info.

thanks-
Todd

By shell I mean the login shell that you use. Some examples would be csh, tcsh, and bash. If you are not sure you can look in /etc/passwd or type $0 at a prompt.

OK, the shell I'm using is bash

I got this figured out too. Here's what I needed to do to make it work. The first this I did was to find out where all the commands were that I wanted to run. I used the find feature and found that the two directories paths that needed to be set were /usr/sbin and /usr/bin

From here, one of the developers that I work with saw me working on this and told me the following. If you go to /etc/profile this is the file that you need. The way that I understand is that profile is that whatever paths that you set in here will be inherited by all users that log onto the machine from a telnet session.

Note: (If you wanted the paths to be specific to the user, and not inherited by all users, then I think you'd have to edit /home/todd(my username in this example) .bash_profile )

The syntax that needs to be used was already in the file! It was:

PATH="$PATH:/usr/X11R6/bin"

So I kept that and added two lines of my own:

PATH="$PATH:/usr/bin"
PATH="$PATH:/usr/sbin"

After that I did a telnet session which I'm thinking ran a new logon which referenced the profile file and new lines, which made it so that I could run traceroute and whois queries without having to be in the directory where these file are located.

-Todd

Very good! I just have two suggestions. You should really try and use .bash_profile unless it is a sigle user machine. This way only you are effected. Second, you do not need multiple lines. You could just use:
PATH="$PATH:/usr/X11R6/bin:/usr/bin:/usr/sbin"
Glad to see you got things working.

One additional suggestion is the following. Whenever you make a change to your .bash_profile, one way to get the system to notice the change is to log out and log back in. A more convenient way is to force the system to reload your .bash_profile by issueing the command:

source .bash_profile