telnet/ftp Service problem

HI,

I have setup a Linux 8.0 server with telnet & ftp service. But I can't ftp or telnet into the server. I have checked with the netstat and the service is listening.

When I telnet or ftp it shows the error:
Connecting To 192.168.1.93...Could not open a connection to host on port 23 : Connect failed

Within the server I can telnet or ftp itself, and from outside I can ping the server. I have gone through and search for any wrong setting, but I still do not know what is happening.

I load the ver 8.0 in text mode and I am still new in this OS.

Can someone help? Appreciate that.

Gad

Have you tried ssh instead of telnet? It's pretty much the same thing, just secure. The best clients to use from windows are putty (ssh client) and winscp. Winscp looks and acts like ftp but uses ssh on the back end for security.

I have tried ssh but it has connection reset by peer error.

Could it be some corruption in some files for the kernel?

Thanks

Do you have iptables or some other firewall preventing access to the machine?

there is no firewall or other security block. The server was installed and connected to a LAN and trying to ftp and telnet.

You probably have to open something in xinetd. Do a man on it.

I have the same problem with my Linux 8.0

Try this:
chkconfig telnet on
chkconfig wu-ftpd on
service xinetd restart

Or if you first want to check whether they are turned on:
chkconfig --list telnet
chkconfig --list wu-ftpd

Remember, xinetd only checks the configuration when it starts up, so you need to restart it before changes will take effect.

In the /etc/xinetd.d directory you will find files named telnet and wu-ftpd . You can modify these configuration files to limit access; eg (from our class notes):

vi telnet
add or modify lines:
only_from = ...
no_access = ...
service xinetd restart

examples:
only_from = 10.196.0.0
# all IP 10.196.x.x
only_from = 10.196.1.{1,2,3,4}
only_from = 10.196.{2,3,7}
only_from = 10.196.0.0/18

We found that the system interpreted multiple lines differently than we expected, so read the man page and play with it.

I do not know why I can not run the chkconfig command.

The file is into the /sbin I found it but when I exceute the command appears the next error:

[root@localhost sbin]# chkconfig telnet on
bash: chkconfig: command not found

Why !!!!!

If you're running as root after a su, you need to use the full path "/sbin/chkconfig" Otherwise, if you logged in as root, you should be able to simply run "chkconfig"

That's strange. You are root, which you need to be. And I just ran it via telnet, so it doesn't matter whether you are logged onto the machine locally or remotely.

Do a echo $PATH to see whether sbin is in the search path (it should be).

Linux never searches in the current directory unless it is in the search path (if you add it, put it very last -- this is important). So to run a program that is in the current directory, you have to tell Linux that it is there with the relative directory path ./, as in:
./chkconfig telnet on

PS
I think I found your problem. You had run su to become root, but you did it the wrong way.
You ran:
su
When I did an echo $PATH, /sbin was not in the search path.

When I ran su -, /sbin and a lot more directories appeared:

That - tells su to go through the entire login process, which includes loading root's environment. As you can see, without the - I still had wise's environment loaded.

So run su - and it should work.

Hi ,

Since u r able to ftp and telnet from local machine to local machine everyting is right with /etc/xinetd.conf and respective daemons

Check if /etc/hsosts.allow and /etc/hosts.denyb files are present . By default this files will be configured such as to deny access to everyone othr that localhost so take backup of these files and remove them.

Then try using telnet or ftp to ur machine from soome other machine using as non root user.

If u r able to do so then it is ok ..

Then try usinh elnet or ftp using root.
If u r not able to do so then u will require to modify /etc/securetty file refer to documentation for so.

I was having similar problem it got resolved after deleting /etc/hosts.allow and /etc/hosts.deny

Bye