Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
You can do a nmap to see if you have any listeners for these daemons on you system. Alternatively you can use YaST2 con check the status of the daemon and also activate them if they are not running. Try YaST2->Network Basic ->Strat Stop Service( Inetd). Her you can see what processers are active and also activate process.
i am trying to remember how i solved the problem. i believe that it was as simple as inetd was not scheduled to run at startup. i edited the runlevel editor to start inetd in runlevels 3 & 5. then i rebooted. it has been fine since then. for some reason in SuSE 8.0 inetd is not enabled by default on install. i had just installed 8.0 and i thought it would be.
[david@www david]$ cat /etc/xinetd.d/wu-ftpd
# default: on
# description: The wu-ftpd FTP server serves FTP connections. It uses \
# normal, unencrypted usernames and passwords for authentication.
disable = no
socket_type = stream
wait = no
user = root
server = /usr/sbin/in.ftpd
server_args = -l -a
log_on_success += DURATION USERID
log_on_failure += USERID
nice = 10
This post seems a little cluttered, so I would like to clarify.
On SuSE (8.0 and 8.1 at least), telnet is not enabled by default. First you need to make sure 'inetd' and 'telnet-server' are installed. Then you need to start 'inetd' using the runlevel editor in YaST2. Finally you need to edit your inetd.conf, the simplest way to do this is using the 'Start/stop services (inetd)' in YaST2.
You do not need to start a telnet server, inetd takes care of this.
One final point, you should really be using SSH rather than telnet. In addition to being more secure, it supports file copying (scp and sftp) and X11 forwarding.
>> inetd is started becuase i can ftp to my machine with no problem.
HCMK, FYI (just incase you have spotted it yet) ftp is an independant service (in SuSE), and is not started by inetd.