MDaemon + Outlook problems
Geoff Lock
- a Netgear router/modem which connects to the ISP Exetel. It is a Netgear
DG-814
- a Dlink router DI-624 whose WAN port is connect to one of the ports on the
hub of the Netgear
- a Windows XP computer running MDaemon (a mail server) connected a port on
the DLink
- a notebook which picks up email locally and remotely from MDaemon.
I want to replace the Netgear/DLink combo with a DLink DSL-502-GenII and a
switch.
I have looked at the firewall rules in the old DLink DI-624 and I believe I
have replicated all the rules in the new DLink. Essentially, I have opened
port 110 (for POP3), port 25 (for SMTP), port 143 (for IMAP), port 3000 (for
WorldClient - an MDaemon application) and port 1000 (for Webadmin - an
MDaemon application). Also I have forwarded anything for the above ports to
the MDaemon machine.
There were a heap of other stuff which I ignored like virtual FTP, Virtual
DNS, Telnet, games, HTTPS and the exposing of one machine (totally unrelated
to anything going by the IP address) to the Internet. I did try including
them in the new DLink as well but no cigar.
I have looked at the ports which MDaemon uses and the only ports which seem
relevant are ports 110 (POP3), 25 (SMTP), 143 (IMAP), 3000 (WorldClient) and
1000 (Webamdim). There were other ports which MDaemon could use, eg for SSL
connections but these were not present anywhere in the old DLink anyway so I
ignored them.
I cannot determine what settings are in the Netgear as it appears to be
running as a modem (is this possible??)
When I connect the new DLinkrouter/modem and the switch, I can access the
Internet. This proves that I have the username and password right :) BUT
Outlook (on the notebook) cannot get to the mailserver, MDaemon.
What am I doing wrong?
I would appreciate any feedback.
Thank you.
terryc
You do not need to include any firewall rules off the d-link in the
single replacement adsl modem/router.
> I have looked at the firewall rules in the old DLink DI-624 and I
> believe I have replicated all the rules in the new DLink. Essentially, I
> have opened port 110 (for POP3), port 25 (for SMTP), port 143 (for
> IMAP), port 3000 (for WorldClient - an MDaemon application) and port
> 1000 (for Webadmin - an MDaemon application). Also I have forwarded
> anything for the above ports to the MDaemon machine.
port 25; he runs his own mail server, check.
port 110; he collects mail from his lan when away?
port 143; he needs this for mail when away?
port 1000; he administers his network when away?
port 3000; yes well
>
> There were a heap of other stuff which I ignored like virtual FTP,
> Virtual DNS, Telnet, games, HTTPS and the exposing of one machine
> (totally unrelated to anything going by the IP address) to the Internet.
> I did try including them in the new DLink as well but no cigar.
Is he cruising for a bruising with all these open ports?
What game does he need to have ports open?
Personally, apart from 25 & 80, I do not see any need for any open ports.
25 is redirected to your mail server and 80 to your public webserver.
If he does travel and needs to colect emails, etc, the rule of thmb was
to put any services onto a random port, if possible. Certainly it is
security by obscurity with these modem/router boxes, but t all adds up.
> BUT Outlook (on the notebook) cannot get to the mailserver, MDaemon.
Mailserver s internal?
does the win client use dhcp?
where is dhcp comming from?
do you need o set up a new network(change nic properties) in the win box?
--
Great advances in Debian Linux; post a bug report and get spam in three
days.
Geoff Lock
"terryc" <newsseven...@woa.com.au> wrote in message
news:4a933b2a$0$3520$c30e...@pit-reader.telstra.net...
> On Tue, 25 Aug 2009 03:33:32 +1000, Geoff Lock wrote:
>
>
> You do not need to include any firewall rules off the d-link in the
> single replacement adsl modem/router.
Hm, I tort that replicating some of the rules would be necessary but I
accept what you say.
>
>> I have looked at the firewall rules in the old DLink DI-624 and I
>> believe I have replicated all the rules in the new DLink. Essentially, I
>> have opened port 110 (for POP3), port 25 (for SMTP), port 143 (for
>> IMAP), port 3000 (for WorldClient - an MDaemon application) and port
>> 1000 (for Webadmin - an MDaemon application). Also I have forwarded
>> anything for the above ports to the MDaemon machine.
>
>
> port 25; he runs his own mail server, check.
> port 110; he collects mail from his lan when away?
> port 143; he needs this for mail when away?
> port 1000; he administers his network when away?
> port 3000; yes well
Yes, he does pick up mail when he is away and hence ports 110 and 143.
He also sends mail via the MDaemon SMTP (hence port 25) instead of using the
SMTP of whatever ISP he is connected to. It is easier this way as Bazza is
not that cluey about techie things - yet.
The Webadmin port appears to be an MDaemon thing which I included - I am not
very familiar with MDaemon as you may have guessed by now. I look on it
merely as just another application which require inbound and outbound
Internet access.
>> There were a heap of other stuff which I ignored like virtual FTP,
>> Virtual DNS, Telnet, games, HTTPS and the exposing of one machine
>> (totally unrelated to anything going by the IP address) to the Internet.
>> I did try including them in the new DLink as well but no cigar.
>
> Is he cruising for a bruising with all these open ports?
Yes, his "other mate" who was "helping" him had it setup that way but I have
not included them in the new DLink.
> What game does he need to have ports open?
Bazza is a boring old man and does not play any online games. :)
> Personally, apart from 25 & 80, I do not see any need for any open ports.
> 25 is redirected to your mail server and 80 to your public webserver.
No webserver here but I agree with you that ports 25, 110, 143, 1000 and
3000 are the only ones of interest here and should be redirectedto he mail
server.
> If he does travel and needs to colect emails, etc, the rule of thmb was
> to put any services onto a random port, if possible. Certainly it is
> security by obscurity with these modem/router boxes, but t all adds up.
Random ports may obscure but I figured portscanning will pick up those open
ports anyway so I left the ports at the default.
>> BUT Outlook (on the notebook) cannot get to the mailserver, MDaemon.
>
> Mailserver s internal?
Yes.
> does the win client use dhcp?
> where is dhcp comming from?
DHCP is handled by the old DLink router (no idea why anyone would use DHCP
in a small network) but the mail server has a static internal IP
(192.168.0.125).
> do you need o set up a new network(change nic properties) in the win box?
I am not very sure how a new network would help here.
Geoff Lock
"Geoff Lock" <glock@fake_address.com.au> wrote in message
news:4a92ced1$1...@dnews.tpgi.com.au...
>I have a friend who has a small network which consist of the following :-
This problem is now solved using an el cheapo router/modem running in
bridged mode. I don't know why bridging did not work with the new DLink or
another new replacement, a Netgear.
Thank you.