Click to See Complete Forum and Search --> : 3 basic FTP server problems


Ace_Armstrong
01-13-2003, 09:39 AM
Long message. I apologize in advance. I've only been using Linux for about three days (and I don't have any programming or scripting background to speak of), so I'm a complete newb. I anticipate that these will be easy questions for youse all to answer.

First, let me tell you what I'm trying to do: I am working on setting up a Xoops (which is what I think this board runs on) site, but it's slightly more complex to set up than anything I've done before (requires mySQL, there's some PHP scripting involved, and so on). So, having this old P200 that someone gave me and I never even powered up, I decided that it might be wise to install linux (something I've been meaning to learn more about, anyway), set it up as a small internet-type server that just works over my local network, get the webserver and mySQL running, install Xoops, and experiment before I try to put the thing up in public and make a fool of myself.

After much trial and tribulation (mostly involving an entire box of bad floppy disks and a scratched CD-ROM), I finally got my box up and running using Slackware 8, and I had the FTP kinda working on Friday night using ProFTP; I could connect to it and download files, but I couldn't upload. Also, I couldn't get the symbolic link to the \www\ directory to work on the FTP. After dinking with the config files and file permissions and not finding anything to indicate the problem, I gave up for the moment and turned to Samba, basically editing the main config file in an attempt to allow my Windows machines access it. After a few minutes of this, I still couldn't connect to the Linux machine using Windows and my FTP stopped working entirely.

I can TELNET in from other computers on the network and Apache seems to serve up HTLM just peachy. (I have yet to attempt working with mySQL.) But now what I have is a network connection (via Samba) that says "No permission to access resources" and an FTP that gives me the error "The FTP session was terminated." (It appears to be a 421 error.)

I think I'm going to cry. :mad:

The first problem, of course, is that I can't get an FTP connection. I've done everything from setting file permissions to RWE for everyone to changing the owner/group of the default FTP folders (to the point that I can no longer remember what they are supposed to be) to checking the file that lists denied users to.... *pulls hair out* None of the changes I made previous to the SAMBA configuration seemed to make any difference with the FTP, but after I made changes to the Samba config files it seemed that FTP no longer worked. Is it possible that Samba is conflicting somehow with the FTP server? Or did I inadvertantly do some stupid minor thing along the way that screwed me up and would have been easy to fix at the time if I had known about it?

The second problem: I wasn't able to upload when I did connect. (The goal is really just to be able to use FTP to transfer files to the \www\ directories, just as I would on a public server.) I made sure that all of the folders had WRITE access, but that didn't help. I even tried giving all of the folders RWE access thinking that something in there would allow uploads, but that didn't help, either.

The third problem was (back when I could actually get a connection to the FTP server) that I couldn't get to the \www\ directory using a symbolic link. This may be an easy fix; I was using the anonymous account at the time, and my understanding now is that anonymous accounts can't follow symbolic links, but honest-to-gosh user accounts can. Is this true? If so, problem solved. (I think...once I can get a real connection...)

If Samba is causing these problems, it's no big to disable it; I don't really need Samba; I was just trying to get it to work as an alternative to transfering the files over via FTP (plus, it would be good to get the experience in setting it up). But, if it's possible to run both, I'd kinda like to do so for purposes of flexibility. Is there a simple fix to the lack of a Samba connection, or is this something I should put off until I have everything else running and have a big chunk of time available to donate to it?

Thanks in advance for the help!

HighOrbit
01-13-2003, 03:40 PM
Wow.. that's alot. I can't offer a solution, but I have a tool that might help you find a solution.

Webmin is a browser-based gui that helps adminster various services like Samba and FTP. Webmin makes administering and setting up ProFTP a snap. If you install Webmin, you might be able to see what's wrong with your FTP server and Samba and change it to where it needs to be.

You can find webmin at www.webmin.com

Ace_Armstrong
01-13-2003, 08:46 PM
Originally posted by HighOrbit
Wow.. that's alot. I can't offer a solution, but I have a tool that might help you find a solution.

Webmin is a browser-based gui that helps adminster various services like Samba and FTP. Webmin makes administering and setting up ProFTP a snap. If you install Webmin, you might be able to see what's wrong with your FTP server and Samba and change it to where it needs to be.

You can find webmin at www.webmin.com

That helped somewhat....now instead of a big old bunch of nothing I get a "Connected to 192.168.0.100" followed instantly by "Connection closed by remote host."

I'm going crazy trying to figure this out!