Re: [Staffslug] Debian Ports
On 1 November 2011 11:08, walt <walt(a)helvatron.co.uk> wrote:
Hi all,
Hope you can help me.
I've got quite a long way with Linux over the past few months but I've run
into a problem I just don't understand. I've googled it to death but I
still don't know enough to resolve the problem.
It's Debian Linux and it runs Apache, MySql, PHP and SAMBA at the moment.
Everthing works fine. Even the SAMBA shares function as they should and I
can access all the shared folders from any windows pc.
However, I also need odbc (3306), smtp (25) and pop3 (110) connections
from windows machines to work. According to the network tools/port scan
the required ports are open. Here is the interesting thing; if I run a
portscan as 'localhost' or 127.0.0.1 then ALL the ports are reported as
open. If, however, I enter the ipV4 address of this machine and run the
scan all the ports I need, apart from 80, are missing. Port 80 appears on
both local and lan ip lists.
In desperation I re-installed debian Linux from scratch but I got the same
results. I then uninstalled iptables but that made no difference either.
There must be a configuration file somewhere that needs changing, I just
don't know which one. I have already checked host.allowed and hosts.denied,
they have no active entries.
Hope one of you can point me in the right direction.
Very many thanks, Walter
Good morning Walter.
Though I am not certain, there could be two things causing this.
The first is that the application you are trying to access is only
"listening" on the internal ports. I find this is common with mysql,
which by default only listens on localhost:3306 or whatever the port
is.
There are configuration files for these servers which allow you to
change the listening settings. E.G
http://www.howtogeek.com/howto/mysql/switch-mysql-to-listen-on-tcp/
In this article, you can see that mysql only listens on the "bind
address" as stored in the config file. This is done for security as
most webapps run locally.
I imagine there are very similar situations with the other services,
in which case googling "listen address for <service name>" usually
returns a result.
The last possibility is that if you are trying to access the server
from behind a router, the firewall may be blocking the requests. I
didn't get the impression you were accessing the box over a WAN
however.
--
Regards, Kris Douglas.
www.krisd.eu