Linux server will stop responding to telnet requests
Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Linux server will stop responding to telnet requests
I am using Linux server in my testing envoirnment. I am using Redhat 6.2 version and due to other apps, I am not able to upgrade to latest version.
My tests will telnet into the server several times, but after some time I see that the server will stop responding to the telnet requests. If I restart the inet services, problem will be solved for some time but I will eventually run in to again.
If I reboot the system, I don't see the problem for some time. When in that state, I do not see anything in the log messages. I also do not see telnet port in the listening mode.
Is there any file or secuirty feature that I have to disable to allow unlimited telnet requests on the server ??
You don't see anything listening because of inetd (or xinetd). Basically many services don't need to run all the time so inetd keeps track of the various ones available and only on a request for the specific service does it acually start it.
On my RH it is xinetd but I don't have anything as old as 6.2.
If its inetd you can look at /etc/inetd.conf.
If its xinetd you can look at /etc/xinetd.d/telnet.
Both will show you configuration options but I don't know of one that would do what you're talking about - it may become apparent if you look at the files. It also may not be telnetd itself that is the issue but rather some PAM or other authentication setup that is shutting you down because it thinks multiple logins at the same time are some sort of attack.
Your telnet entry look OK. Don't see anything there that would cause a timeout. It must be some other "feature" on your system.
FYI: Rather than rebooting doing a "kill -1 <PID>" on the Process ID of inetd (ps -ef |grep inetd" to find it) will cause inetd to reread inetd.conf - this may also reset whatever it is back to square one for you.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.