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.
OK kinda new at this. Just enought to be dangourous.
Fresh install of redhat 9
Have a SMB baricade hardware firewall.
Ports 80,20,21 open to the outside and ported to my linux box at 192.168.2.14
HTTP apache server works fine this way. Trying to get an FTP server up so other users can modify the website.
I can connect to the server from another client of this side of the firewall no problems. When I try to connect to the server using the real world IP it connects then I get the error from ws_ftp
227 Entering Passive Mode (192,168,2,14,21,52)
connecting data channel to 192.168.2.14:5428
Substituting connection address 24.XXX.XXX.XXX for private address 192.168.2.14 from PASV
connection refused; the server would not accept an FTP connection.
500 Illegal PORT command.
Port failed 500 Illegal PORT command.
Users from the internet get similar things. The client connects but then fails after it goes to passive mode.
OK... I have the same issue. I installed RH9 on one computer with
an up 2 date RH8 on my host. I persuaded the host to function using RH8 vsftpd and connected from the Windows XP box (which is actually a dual-boot system). This was successful.
Now I am attempting to connect from the RH9 client on the same box. So it is NOT a hardware issue, and it is not certainly a server issue, though it could be. It is most likely something on the client side. The connection succeeds through the login and then fails to handle the pasv mode connection for data.
It's definitely a problem in the iptables config, and I am working on that setup now. It appears that the client side iptables isn't accepting the connect from the server on the random-high port. I have found several sources of config info on the web which might work, but the lokkit on RH9 doesn't appear to allow for manual config of the tables. I have to find out how to do THAT properly before I can really use the tables. Annoying. I should be able to use vi to mod the config to be what it needs to be, but we are trying to automate this stuff and RH has it tied up with the automatic security config.
Turning off iptables on the server makes it work. I am trying to be certain that this is safe to do. The server is ONLY a server in the context of the zone behind a linksys nat installation.
I will continue to work on it a while, I need to know how to do this sort of thing. OTOH, it is hard to do and I have found that things that are really hard (as this appears to be) are likely to be things we shouldn't be doing. I don't NEED to serve ftp to the world, just to the private subnet 192.168.xxx.yyy. I can accomplish my tasks by configuring samba for that same region and by using sftp and scp and nfs locally. In other words. Perhaps I should rely on my translation router to do translation and maybe not be dealing with this. I almost know enough to evaluate the problem properly now.