> > > > > > > Hi. > > > I'm a linux newbie and I'm trying to set up an ftp server on a > > > LAN. The server is up and running on redhat 9.0. > > > The server is conected to a LAN with other Linux and windows > > > computers through a wireless gateway attached to a cable modem. > > > I have a static IP asigned by my ISP so I can access the gateway > > > (and therefore the ftp server) from anywhere over the internet. > > > > > > The problem is that when I log into the server from any box > > > within the LAN using the external IP address (going outside the > > > LAN to the internet and then coming inside again) I get this error: > > > > > > ftp> ls > > > 500 Unknown command. > > > 227 Entering Passive Mode (192,168,1,19,229,168) > > > 500 Illegal PORT command. > > > ftp: bind: Address already in use > > > > > > But if I log into it using the internal IP address or from > > > anywhere outside the LAN using the external IP address (over the > > > internet) the ftp server works just fine. I thought that maybe > > > either the server or the gateway where blocking the access with a > > > firewall but if that where the case, I wouldn't be able to even > > > log into the server right? > > > I hope I was clear, english isn't my first languaje but please do > > > write if you have any idea. Any help is greatly apreciated > > > > > > > Even though this flag is said to have no effect anymore, try > starting the > > ftp sessoin anyway with the -p flag on and see if it works > > ftp -p > > It's meant to start the ftp session as passive right off the bat. > > > > Thanks Ben. > I tried it out but it didn't work. > Thanks anyway > > Is this an academic exercise by the way? YOu are just wondering why it does that? Since internal clients should access your ftp site internally as a good rule of thumb. Anyway, I have a feeling it's just something that happens with the firewall since you are natting out and then coming back in again. The ftp server responds back to client telling client to use port XXX. This response goes back out the firewall and in again to the client. The client then attempts to open on that port back out through the firewal but it's already in use on the firewall by the server so you get that "Address already in use" error. So it supposed to happen that way. My best guess. Ben -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
