Re: problems with Apache, FTP, SAMBA | Apache solved.
I tried to send this mail as HTML, but the list rejected it... :-( that's why the lines are cutted [SNIP] --- the whole part about the Apache. Can whatever directory and file gets accessed via the URL you are using be executed (the directory) and read (the file) by the userid that apache runs as? Of course. All files and the DocumentRoot are RWX for all users, and belong to user:group alan:alan That was the problem... aparently the user was not properly created... I changed it now to an existing user and everything seems to work fine... THANKS A LOT!! FTP: I can't have access to anyone of the machines trough FTP. I am having some troubles with the config... what should I configuree again... what are the files that I should edit. When trying to connect it just says conection refused.. nothing else. I'm having troubles with this. I use xinet.d's pro-ftpd. Connection Refused most likely means that nothing is listening on the ftp port. Or it could mean that the particular IP addresses you are connecting from are disallowed. Or, just barely possible, you could have a firewall rule in place that blocks access. But the daemon is running (at least it should) I'll check when I get home. I surmise that you run ftp the usual way, through inetd (in your case, xinetd). Yes. I do. Use netstat -l to verify that something is listening on port 21. I'm not at home right now. But I will ASAP. It does not show it. I see the problem now... but how do I solve it??? Thanks. Check the xinetd configuration file to make sure it is listening on that port. HOW? I have in /etc/xinetd.d/pro-ftpd.conf the line disable=no. That should be enough... right? Check hosts.allow and hosts.deny to see if they interfere with access. Nothing wrong there. In fact NOTHING there at all. They are blank. Check your firewall ruleset (probably with iptables -nvL, if you run a 2.4.x kernel) to see if there are any rules that DENY access. I tried #service iptables stop and still didn't work. Ok... this is going to be long... here is the output of iptables -nvL [EMAIL PROTECTED] /etc]# iptables -nvL Chain INPUT (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 0 0 DROP all -- * * 0.0.0.0/0 0.0.0.0/0 state INVALID 4 176 ACCEPT all -- * * 192.168.23.114 0.0.0.0/0 18034 2264K ACCEPT all -- * * 192.168.23.0/24 0.0.0.0/0 0 0 ACCEPT all -- * * 10.129.2.155 0.0.0.0/0 3 232 ICMPACCEPT icmp -- eth1 * 0.0.0.0/0 0.0.0.0/0 10 600 REJECT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:113 reject-with tcp-reset 0 0 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:22 0 0 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:25 0 0 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:53 0 0 ACCEPT udp -- eth1 * 0.0.0.0/0 0.0.0.0/0 udp dpt:53 17 4597 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:80 0 0 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:443 0 0 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:110 334K 501M ACCEPT all -- eth1 * 0.0.0.0/0 0.0.0.0/0 state ESTABLISHED 0 0 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpts:1024:65535 state RELATED 0 0 ACCEPT udp -- eth1 * 0.0.0.0/0 0.0.0.0/0 udp dpts:1024:65535 state RELATED 0 0 DROP all -- * * 0.0.0.0/0 0.0.0.0/0 state INVALID 0 0 ACCEPT all -- * * 192.168.23.114 0.0.0.0/0 0 0 ACCEPT all -- * * 192.168.23.0/24 0.0.0.0/0 0 0 ACCEPT all -- * * 10.129.2.155 0.0.0.0/0 0 0 ICMPACCEPT icmp -- eth1 * 0.0.0.0/0 0.0.0.0/0 0 0 REJECT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:113 reject-with tcp-reset 0 0 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:20 0 0 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:21 0 0 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:22 0 0 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:25 0 0 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:53 0 0 ACCEPT udp -- eth1 * 0.0.0.0/0 0.0.0.0/0 udp
Re: problems with Apache, FTP, SAMBA | Apache solved.
At 03:35 PM 6/20/2003 -0400, Alan Bort wrote: I tried to send this mail as HTML, but the list rejected it... :-( Actually, this is a :-) . Many of us find the clutter of html formatting burdensome ... you'll encounter a lot of this as you get more familiar with linux ... so you will see that many Linux-related lists reject html-formatted mail. And even on ones that do not reject it, experienced members (that is, the people who *answer* questions) will often complain about it. [apache stuff deleted] FTP: I can't have access to anyone of the machines trough FTP. I am having some troubles with the config... what should I configuree again... what are the files that I should edit. When trying to connect it just says conection refused.. nothing else. I'm having troubles with this. I use xinet.d's pro-ftpd. Connection Refused most likely means that nothing is listening on the ftp port. Or it could mean that the particular IP addresses you are connecting from are disallowed. Or, just barely possible, you could have a firewall rule in place that blocks access. But the daemon is running (at least it should) I'll check when I get home. I surmise that you run ftp the usual way, through inetd (in your case, xinetd). Yes. I do. Use netstat -l to verify that something is listening on port 21. I'm not at home right now. But I will ASAP. It does not show it. I see the problem now... but how do I solve it??? Unfortunately (for this purpose, anyway), I do not use xinetd here. I use inetd, so I cannot tell you how to configure xinetd to listen for incoming ftp requests. Possibly someone else here will jump in with the solution If not, or while you are waiting, I'd suggest reading over the man page for xinetd (and any other docs ... they are usually in /usr/share/doc) to see what you missed. Thanks. Check the xinetd configuration file to make sure it is listening on that port. HOW? I have in /etc/xinetd.d/pro-ftpd.conf the line disable=no. That should be enough... right? As I said above, I have no idea. But since nothing is listening on port 21, this is surely your problem. The queries about hosts_access and iptables are irrelevant to this problem. Check hosts.allow and hosts.deny to see if they interfere with access. Nothing wrong there. In fact NOTHING there at all. They are blank. Check your firewall ruleset (probably with iptables -nvL, if you run a 2.4.x kernel) to see if there are any rules that DENY access. I tried #service iptables stop and still didn't work. Ok... this is going to be long... here is the output of iptables -nvL [EMAIL PROTECTED] /etc]# iptables -nvL Chain INPUT (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 0 0 DROP all -- * * 0.0.0.0/0 0.0.0.0/0 state INVALID 4 176 ACCEPT all -- * * 192.168.23.114 0.0.0.0/0 18034 2264K ACCEPT all -- * * 192.168.23.0/24 0.0.0.0/0 0 0 ACCEPT all -- * * 10.129.2.155 0.0.0.0/0 3 232 ICMPACCEPT icmp -- eth1 * 0.0.0.0/0 0.0.0.0/0 10 600 REJECT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:113 reject-with tcp-reset 0 0 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:22 0 0 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:25 0 0 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:53 0 0 ACCEPT udp -- eth1 * 0.0.0.0/0 0.0.0.0/0 udp dpt:53 17 4597 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:80 0 0 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:443 0 0 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:110 334K 501M ACCEPT all -- eth1 * 0.0.0.0/0 0.0.0.0/0 state ESTABLISHED 0 0 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpts:1024:65535 state RELATED 0 0 ACCEPT udp -- eth1 * 0.0.0.0/0 0.0.0.0/0 udp dpts:1024:65535 state RELATED 0 0 DROP all -- * * 0.0.0.0/0 0.0.0.0/0 state INVALID 0 0 ACCEPT all -- * * 192.168.23.114 0.0.0.0/0 0 0 ACCEPT all -- * * 192.168.23.0/24 0.0.0.0/0 0 0 ACCEPT all -- * * 10.129.2.155 0.0.0.0/0 0 0 ICMPACCEPT icmp -- eth1 * 0.0.0.0/0 0.0.0.0/0 0 0 REJECT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:113 reject-with tcp-reset 0 0 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:20 0 0 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:21 0 0 TCPACCEPT tcp -- eth1 * 0.0.0.0/0
Re: problems with Apache, FTP, SAMBA | Apache solved.
El vie, 20-06-2003 a las 16:46, Ray Olszewski escribió: At 03:35 PM 6/20/2003 -0400, Alan Bort wrote: I tried to send this mail as HTML, but the list rejected it... :-( Actually, this is a :-) . Many of us find the clutter of html formatting burdensome ... you'll encounter a lot of this as you get more familiar with linux ... so you will see that many Linux-related lists reject html-formatted mail. And even on ones that do not reject it, experienced members (that is, the people who *answer* questions) will often complain about it. I know. In fact I usually complain about the use of HTML.but in this case it was kind of usefull. You see... I wanted to make some differences between the quoted and the actual text I wrote. (quoted from my stdout) [apache stuff deleted] FTP: I can't have access to anyone of the machines trough FTP. I am having some troubles with the config... what should I configuree again... what are the files that I should edit. When trying to connect it just says conection refused.. nothing else. I'm having troubles with this. I use xinet.d's pro-ftpd. Connection Refused most likely means that nothing is listening on the ftp port. Or it could mean that the particular IP addresses you are connecting from are disallowed. Or, just barely possible, you could have a firewall rule in place that blocks access. But the daemon is running (at least it should) I'll check when I get home. I surmise that you run ftp the usual way, through inetd (in your case, xinetd). Yes. I do. Use netstat -l to verify that something is listening on port 21. I'm not at home right now. But I will ASAP. It does not show it. I see the problem now... but how do I solve it??? Unfortunately (for this purpose, anyway), I do not use xinetd here. I use inetd, so I cannot tell you how to configure xinetd to listen for incoming ftp requests. Possibly someone else here will jump in with the solution If not, or while you are waiting, I'd suggest reading over the man page for xinetd (and any other docs ... they are usually in /usr/share/doc) to see what you missed. I will. Though it worked before with wu-ftpd... when I changed something in my server it stopped working... and so I thought of trying proftpd. Thanks. Check the xinetd configuration file to make sure it is listening on that port. HOW? I have in /etc/xinetd.d/pro-ftpd.conf the line disable=no. That should be enough... right? As I said above, I have no idea. But since nothing is listening on port 21, this is surely your problem. The queries about hosts_access and iptables are irrelevant to this problem. I see. However iptables has port 20 and 21 open. and it sure has other ports open as well. Check hosts.allow and hosts.deny to see if they interfere with access. Nothing wrong there. In fact NOTHING there at all. They are blank. Check your firewall ruleset (probably with iptables -nvL, if you run a 2.4.x kernel) to see if there are any rules that DENY access. I tried #service iptables stop and still didn't work. Ok... this is going to be long... here is the output of iptables -nvL [EMAIL PROTECTED] /etc]# iptables -nvL Chain INPUT (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 0 0 DROP all -- * * 0.0.0.0/0 0.0.0.0/0 state INVALID 4 176 ACCEPT all -- * * 192.168.23.114 0.0.0.0/0 18034 2264K ACCEPT all -- * * 192.168.23.0/24 0.0.0.0/0 0 0 ACCEPT all -- * * 10.129.2.155 0.0.0.0/0 3 232 ICMPACCEPT icmp -- eth1 * 0.0.0.0/0 0.0.0.0/0 10 600 REJECT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:113 reject-with tcp-reset 0 0 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:22 0 0 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:25 0 0 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:53 0 0 ACCEPT udp -- eth1 * 0.0.0.0/0 0.0.0.0/0 udp dpt:53 17 4597 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:80 0 0 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:443 0 0 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:110 334K 501M ACCEPT all -- eth1 * 0.0.0.0/0 0.0.0.0/0 state ESTABLISHED 0 0 TCPACCEPT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpts:1024:65535 state RELATED 0 0 ACCEPT udp -- eth1 * 0.0.0.0/0 0.0.0.0/0 udp dpts:1024:65535 state RELATED 0 0 DROP all -- * * 0.0.0.0/0 0.0.0.0/0 state INVALID 0 0
problems with Apache, FTP, SAMBA
Ok... her is my problem: I have apache2, proftpd and samba on two machines. Though I have them configured correctly (at least I think so) I have the fopllowing problem. Machine A has access to internet trough machine B. From A I can see and use B's apache perfectly. BUT from B to A I can't... I keep getting 403 Forbidden. What am I missconfiguring on A?. FTP: I can't have access to anyone of the machines trough FTP. I am having some troubles with the config... what should I configuree again... what are the files that I should edit. When trying to connect it just says conection refused.. nothing else. I'm having troubles with this. I use xinet.d's pro-ftpd. SAMBA: while on A samba works perfectly, on B it doesn't seem to work... whenever I try to connecto (from C, with windows) the server goes down. I am using a standalone SAMBA, I think it's the latest. Again... I think there might be some incompatibility problem with the config file... and I'm not sure it installed correctly. I would appreciate ANY help you can provide me. Thanks a lot. Oh, BTW: how does ssh file transfer work??? Thanks. PS: what CVS server do you recomend??? and webdav? thanks a lot... yet again. -- Alan Bort Linux Registered User 298277 -Country Manager- [http://counter.li.org] [ http://www.linuxquestions.org ] Username: Ciccio [ http://es.tldp.org ] Ciccio.- - To unsubscribe from this list: send the line unsubscribe linux-newbie in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs
Re: problems with Apache, FTP, SAMBA
At 02:37 PM 6/19/2003 -0400, Alan Bort wrote: Ok... her is my problem: I have apache2, proftpd and samba on two machines. Though I have them configured correctly (at least I think so) I have the fopllowing problem. Machine A has access to internet trough machine B. From A I can see and use B's apache perfectly. BUT from B to A I can't... I keep getting 403 Forbidden. What am I missconfiguring on A?. Hard to say. Can A see and use its own apache server successfully? What about the Windows machine (C) that you refer to later? Are there any access restriction on A's apache (in access.conf, usually)? Can whatever directory and file gets accessed via the URL you are using be executed (the directory) and read (the file) by the userid that apache runs as? FTP: I can't have access to anyone of the machines trough FTP. I am having some troubles with the config... what should I configuree again... what are the files that I should edit. When trying to connect it just says conection refused.. nothing else. I'm having troubles with this. I use xinet.d's pro-ftpd. Connection Refused most likely means that nothing is listening on the ftp port. Or it could mean that the particular IP addresses you are connecting from are disallowed. Or, just barely possible, you could have a firewall rule in place that blocks access. I surmise that you run ftp the usual way, through inetd (in your case, xinetd). Use netstat -l to verify that something is listening on port 21. Check the xinetd configuration file to make sure it is listening on that port. Check hosts.allow and hosts.deny to see if they interfere with access. Check your firewall ruleset (probably with iptables -nvL, if you run a 2.4.x kernel) to see if there are any rules that DENY access. SAMBA: while on A samba works perfectly, on B it doesn't seem to work... whenever I try to connecto (from C, with windows) the server goes down. I am using a standalone SAMBA, I think it's the latest. Again... I think there might be some incompatibility problem with the config file... and I'm not sure it installed correctly. This is too vague even to allow guessing ... I can't tell for sure if the problem is on A or B, and if the server goes down means the samba daemon process dies or the machine itself crashes. Check your logs and see what samba thinks happens. Run top while you are trying to connect and look for oddities. I would appreciate ANY help you can provide me. Thanks a lot. As a general matter, to get good advice, you have to provide good information. That means including both basic background details -- what Linux distro and version? what kernel? what versions of apps? (I think it's the latest is meaningless, unless you do daily, sometimes hourly, reinstalls of all your apps from their CVS trees) -- and relevant specifics -- what URL you try to use, what IP addresses are involved, what the exact commands you send are, what the exact error messages are, and so forth. If you have a hard failure (goes down), information about the hardware involved might be relevant. Depending on the answers to some of the questions I posed, it might be useful to know the basic networking information for the two machines ... the output of ifconfig -a netstat -nr or equivalents (e.g., ip addr show and ip route show) if you don't have those commands. Oh, BTW: how does ssh file transfer work??? You use the scp command to transfer files over an ssh link. Its man page will provide the details. Thanks. PS: what CVS server do you recomend??? and webdav? No recommendation on the first. On the second ... what's a webdav? - To unsubscribe from this list: send the line unsubscribe linux-newbie in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs
Re: problems with Apache, FTP, SAMBA
I didn't mean to do a HUGE mail about this... so I made as short as possible. - Original Message - From: Ray Olszewski [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, June 19, 2003 3:27 PM Subject: Re: problems with Apache, FTP, SAMBA At 02:37 PM 6/19/2003 -0400, Alan Bort wrote: Ok... her is my problem: I have apache2, proftpd and samba on two machines. Though I have them configured correctly (at least I think so) I have the fopllowing problem. Machine A has access to internet trough machine B. From A I can see and use B's apache perfectly. BUT from B to A I can't... I keep getting 403 Forbidden. What am I missconfiguring on A?. Hard to say. Can A see and use its own apache server successfully? What about the Windows machine (C) that you refer to later? A... well. I didn't try... perhaps it would be a good idea. But that's not really the problem. I need access from other machines, not local access. I'll make sure when I get home. C doesn't work very well. when I tried to close the FTP client it crashed. and whenever I try to open Internet Explorer it opens infinite IEs. I'm getting a copy of windows to re-install. Are there any access restriction on A's apache (in access.conf, usually)? No unless the default install comes with any sort of restritions there. But i will check it when I get home. Can whatever directory and file gets accessed via the URL you are using be executed (the directory) and read (the file) by the userid that apache runs as? Of course. All files and the DocumentRoot are RWX for all users, and belong to user:group alan:alan FTP: I can't have access to anyone of the machines trough FTP. I am having some troubles with the config... what should I configuree again... what are the files that I should edit. When trying to connect it just says conection refused.. nothing else. I'm having troubles with this. I use xinet.d's pro-ftpd. Connection Refused most likely means that nothing is listening on the ftp port. Or it could mean that the particular IP addresses you are connecting from are disallowed. Or, just barely possible, you could have a firewall rule in place that blocks access. But the daemon is running (at least it should) I'll check when I get home. I surmise that you run ftp the usual way, through inetd (in your case, xinetd). Yes. I do. Use netstat -l to verify that something is listening on port 21. I'm not at home right now. But I will ASAP. Check the xinetd configuration file to make sure it is listening on that port. HOW? I have in /etc/xinetd.d/pro-ftpd.conf the line disable=no. That should be enough... right? Check hosts.allow and hosts.deny to see if they interfere with access. Nothing wrong there. Check your firewall ruleset (probably with iptables -nvL, if you run a 2.4.x kernel) to see if there are any rules that DENY access. I tried #service iptables stop and still didn't work. SAMBA: while on A samba works perfectly, on B it doesn't seem to work... whenever I try to connecto (from C, with windows) the server goes down. I am using a standalone SAMBA, I think it's the latest. Again... I think there might be some incompatibility problem with the config file... and I'm not sure it installed correctly. This is too vague even to allow guessing ... I can't tell for sure if the problem is on A or B, and if the server goes down means the samba daemon process dies or the machine itself crashes. Check your logs and see what samba thinks happens. Run top while you are trying to connect and look for oddities. Problem Solved. There was a version incompatibility. and I installed the new samba wrong. I'm downloading the latest tarball and installing it today. The problem, as usual, was the config File. I would appreciate ANY help you can provide me. Thanks a lot. As a general matter, to get good advice, you have to provide good information. That means including both basic background details -- what Linux distro and version? what kernel? what versions of apps? (I think it's the latest is meaningless, unless you do daily, sometimes hourly, reinstalls of all your apps from their CVS trees) -- and relevant specifics -- what URL you try to use, what IP addresses are involved, what the exact commands you send are, what the exact error messages are, and so forth. I know... but I am a little newbie on linux, and I have troubles finding logs sometimes. If you have a hard failure (goes down), information about the hardware involved might be relevant. Depending on the answers to some of the questions I posed, it might be useful to know the basic networking information for the two machines ... the output of ifconfig -a netstat -nr or equivalents (e.g., ip addr show and ip route show) if you don't have those commands. Oh, BTW: how does ssh file transfer work??? You use the scp command to transfer files over
