[afnog] mail server

[Hyeroba Peter]

Sorry about the very vague initial post,

If I run telnet 192.168.200.1 80 it actually connects
If I access my webmail from the 192.168.0.1 interface, I can do so properly.

The 192.168.200.1 and 192.168.0.1 are the internal and external interfaces
respectively in relation to my firewall.

So if I tell someone outside my network to access my webmail, they do so
perfectly well. But if I try to do so on my LAN, I cannot. 


Hyeroba W. Peter 
Computer Frontiers International limited;
Tel: +256 31 230 1800 or +254 41 456 4200; Fax: +256 41 434 0456;
Cell-phone: +256 78 247 9192;
Website: www.cfi.co.ug 


-----Original Message-----
From: Stephane Bortzmeyer [mailto:bortzmeyer at nic.fr] 
Sent: Tuesday, December 16, 2008 11:12 AM
To: Hyeroba Peter
Cc: afnog at afnog.org
Subject: Re: mail server

On Tue, Dec 16, 2008 at 10:01:36AM +0300,
 Hyeroba Peter <phyeroba at cfi.co.ug> wrote 
 a message of 21 lines which said:

> I have a mail server on that also doubles as a firewall, its an suse
> enterprise server, the problem is I can access the openwebmail off
> the internet but cannot access it over the local network.

As always, "cannot" is not a proper error message.

1) What command did you type?
2) What result did you get?

Example: "I type telnet mywebmail.example 80 and I get "Connection
foobared at 192.0.2.1"

Remember that graphical behemoths like Firefox (and, worse, IE) are
very poor debugging tools.

Typical tools to debug system and network administration problems:

- telnet (you can give a port number after the host name to test
  various services)

- ping (to check IP routing)

- the log of the server (if the connection was refused by the server,
  if the firewall is Linux Netfilter, dmesg - if the target is LOG -
  or 'iptables -v -L CHAINNAME' may help)

...