Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
I think then something is wrong with your inetd.conf
Or you haven't done as suggested and restarted inetd?
Alternatively, you could notify us whether you can access other network-services such as ftp, ssh, telnet, http , so we'll know there is no network problem
I have restarted and killed inetd tons of times. i dont know what could be wrong with my inetd.conf file. i used mandrake 9.1 before and that pretty much set everything up for me. but this is very frustrating.
I am on the internet so i would think that it cant be a network problem
You won't get any output from the command line, that is normal.
What you need to do is, run "ps -ef | grep swat | grep -v grep", and look for the swat program running. The open a browser and navigate to the localhost:901 page and then run the ps command above again and see if it is there.
If not, then there is a problem with inetd running the program or you have a firewall blocking that port. You may want to run iptables or ipchains to see what is set up on your system.
If it is running and you are getting nothing on your browser, then there is probably a problem with the swat program itself.
after looking back, I believe the option you would have had to run would have been "--enable-swat", The "--with-swatdir" will default to a previously specified value. But you would have had to do the "--enable-swat" option in order to get this.
You could try and see if you can use any other inetd service. Did you try to ftp to your own machine (ftp localhost)? In case ftp is not an inetd service, try to telnet to your own machine. If that doesn't work, see if telnet is enabled in inetd.conf; and if it isn't, enabled it, restart inetd, and try to telnet again.
I hope this made sense.
If you are getting a bunch of output from iptables, then you probably do have a firewall set up. I know redhat gives you an option during install that will ask you if you want a firewall set up, the default is medium security settings, which pretty much only allows outbound connections to occur.
the fact that you are being refused connection also leans this way.
as root run, "iptables -L", and then post results. X out any identifiable IP's (i.e. 192.168.0.1 becomes xxx.xxx.x.x or <my IP>)
i went into the inetd.conf and relized that the #'s meant that the code was commented out. so i deleted the # next to the swat tcp/901 and restarted inetd and it worked. thanks a lot to everyone who helped me out. im sure i will have more questions along the way. thanks