If you have control of your DSL router (or can get some) you *should* be
able to configure it so that your server is presented on the DLS's WAN IP -
which should be static. DSL Wan IP's must be static routable IP's for
practical reasons. (Yes there are exceptions, but those are rare.)

That is, (ascii art below)

                     |                    |                      [Mail
Server ]
DSL Provider Network +-----{FIX.ED.WAN.IP}|[DSL Router in
NAT]---[192.168.0.10]
                     |                    |

You *should* be able to give your mail server a fixed private IP on your
local network... in the diagram, 192.168.0.10. Other workstations might also
have fixed IPs, but all on the same private network. I recommend keeping it
simple this way, but you _can_ also use DHCP in some cases - but your mail
server's IP must be fixed.

Then, you can configure your DSL router to translate the appropriate ports
(SMTP, POP3, IMAP, WEB etc...) to point at your mail server internally. The
router essentially "pretends" to be your mail server and translates the
packets for those ports to your internal mail server IP and back again on
the way out. This is a common practice in NAT situations and a good security
technique as well (when done properly).

Then, your DNS MX records (wherever they are) will need to show that your
mail server is on the FIX.ED.WAN.IP of the DSL router.

That said, in the long run you will spend much more money (in your sweat)
getting and keeping this working with your DSL provider than you would to
simply convince them to give you a static block of IP's for your network...
most will do this for only a few bucks if you have a server to run inside.
The trouble comes in any time you try to work outside of the DSL provider's
basic paradigm... they just don't get it, and they _WILL_ screw it up
sometime as a result.

We extend a lot of circuits through DSL providers for customers who don't
want to spend the money on a "real" connection... in the end analysis it
always ends up costing them more to do it this way - either in down-time, or
support fees, or both.

Hope this helps,
_M

| -----Original Message-----
| From: [EMAIL PROTECTED]
| [mailto:[EMAIL PROTECTED]]On Behalf Of Bernard
| Sent: Wednesday, February 27, 2002 8:04 PM
| To: [EMAIL PROTECTED]
| Subject: RE: [IMail Forum] anyone
|
|
| are you saying here (please realize I am new to this and trying
| to bring to
| my boss an idea to save us some money) that I could have say a
| dsl modem to
| a dsl router then to a mail server where inside of the router would be say
| 192.168.0.1 and it would work??
| ((((please say yes *lol*)))
|
| -----Original Message-----
| From: [EMAIL PROTECTED]
| [mailto:[EMAIL PROTECTED]]On Behalf Of Sanford
| Whiteman
| Sent: Wednesday, February 27, 2002 12:38 PM
| To: Bernard
| Subject: Re: [IMail Forum] anyone
|
|
| Everyone  is pointing you to dynamic DNS providers. That is good. Just
| be  aware  that  if  your  Imail  server itself has the dynamic IP (as
| opposed to an upstream router/firewall), this won't work because Imail
| won't rebind to the new IP in most cases.
|
| Sandy
|
|
| Please visit http://www.ipswitch.com/support/mailing-lists.html
| to be removed from this list.
|
| An Archive of this list is available at:
| http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
|
|
| Please visit http://www.ipswitch.com/support/mailing-lists.html
| to be removed from this list.
|
| An Archive of this list is available at:
| http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
|
|


Please visit http://www.ipswitch.com/support/mailing-lists.html 
to be removed from this list.

An Archive of this list is available at:
http://www.mail-archive.com/imail_forum%40list.ipswitch.com/

Reply via email to